From: Tom Rini <trini@kernel•crashing.org>
To: Christian <evilninja@gmx•net>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: PREP sym53c8xx sym53c8xx brokeness due to 2.6.9-rc1-bk1 introduced residual data patch ...
Date: Wed, 6 Apr 2005 11:50:49 -0700 [thread overview]
Message-ID: <20050406185049.GF3396@smtp.west.cox.net> (raw)
In-Reply-To: <42533FA1.1070001@gmx.net>
On Wed, Apr 06, 2005 at 03:47:13AM +0200, Christian wrote:
> Tom Rini wrote:
> > Can either of you verify that say 2.6.11.6 w/ "noresidual" on the
> > command-line works? Thanks.
>
> i booted vanilla 2.6.11.6 with noresidual (and "nopresidual" too, as Sven
> sugggested), but the scsi errors did not went away :(
>
> on a side note, and perhaps totally unrelated: i always have
> PROC_PREPRESIDUAL=y in my .config, but i never had /proc/residual as
> promised from the help text.
Odd. I thought that only happened if you had no residual data at all
(which can happen on Powerstacks, esp if netbooting the kernel). But in
that case the new code shouldn't be hit at all. Leigh?
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-04-06 18:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 23:23 PREP sym53c8xx sym53c8xx brokeness due to 2.6.9-rc1-bk1 introduced residual data patch Sven Luther
2005-03-31 14:28 ` Tom Rini
2005-03-31 18:45 ` Sven Luther
2005-04-05 0:03 ` Christian
2005-04-05 5:39 ` Sven Luther
2005-04-05 14:38 ` Tom Rini
2005-04-05 15:23 ` Sven Luther
2005-04-05 15:47 ` Tom Rini
2005-04-06 1:47 ` Christian
2005-04-06 1:58 ` Christian
2005-04-06 18:50 ` Tom Rini [this message]
2005-04-08 11:36 ` Leigh Brown
2005-04-08 14:54 ` Tom Rini
2005-04-08 15:51 ` Christian
2005-04-08 15:57 ` Tom Rini
2005-04-09 11:33 ` [PATCH 2.6.11+] ppc32: Make the Powerstack II Pro4000 boot again Leigh Brown
2005-04-13 5:18 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050406185049.GF3396@smtp.west.cox.net \
--to=trini@kernel$(echo .)crashing.org \
--cc=evilninja@gmx$(echo .)net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox