From: Christian <evilninja@gmx.net>
To: linuxppc-dev@ozlabs.org
Cc: Tom Rini <trini@kernel.crashing.org>
Subject: Re: PREP sym53c8xx sym53c8xx brokeness due to 2.6.9-rc1-bk1 introduced residual data patch ...
Date: Wed, 06 Apr 2005 03:58:05 +0200 [thread overview]
Message-ID: <4253422D.5050606@gmx.net> (raw)
In-Reply-To: <42533FA1.1070001@gmx.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian wrote:
> i booted vanilla 2.6.11.6 with noresidual (and "nopresidual" too, as Sven
> sugggested), but the scsi errors did not went away :(
um, no, worse that that: the scsi error kicks in for sym0:0:0:
sym0:0:0: DEVICE RESET operation started.
(...then it would continue until sym0:15:0, see [1])
then the machine locked up completely, not even SYSRQ works any more.
that happened when booting with "noresidual" and even with PREP_RESIDUAL=n
(in the .config).
thanks,
Christian.
[1] http://nerdbynature.de/bits/hal/2.6.11-rc5/dmesg
- --
BOFH excuse #48:
bad ether in the cables
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCU0ItC/PVm5+NVoYRAnVMAJ9L1eQLopn6ckMUkC+lNVnwsoKUCACfa2Tj
zqXc3jjKeiXpdYuih+wlZqs=
=GRwp
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-04-06 1:58 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 [this message]
2005-04-06 18:50 ` Tom Rini
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=4253422D.5050606@gmx.net \
--to=evilninja@gmx.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=trini@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).