From: Hubert Tonneau <hubert.tonneau@fullpliant.org>
To: mpt_linux_developer@lsil.com, linux-kernel@vger.kernel.org,
sjralston1@netscape.net
Subject: Linux 2.6 MPT fusion bug
Date: Fri, 23 Apr 2004 17:23:52 GMT [thread overview]
Message-ID: <045ULNS12@server5.heliogroup.fr> (raw)
I reported a fiew days ago Linux 2.6 not booting with no error message
on a Dell PowerEdge 2600.
I've just tracked the problem down to a faulty SCSI cable raising a bug in MTP
fusion driver for Linux kernel 2.6, up to Linux 2.6.6-rc2
Basically, one of the SCSI cable is wrong, probably a broken wire, so the BIOS
sais that it's a narrow cable, and switches down to 40 MB/s instead of 320 MB/s
With a 2.4 kernel, the Linux driver will report a fiew such error message:
<4>SCSI Error: (1:5:0) Status=02h (CHECK CONDITION)
<4> Key=6h (UNIT ATTENTION); FRU=02h
<4> ASC/ASCQ=29h/02h "SCSI BUS RESET OCCURRED"
<4> CDB: 28 00 00 00 18 3F 00 00 08 00
and recover gracefully, and the machine works perfectly, just a little bit
slower since the disks are connected at 40 MB/s.
With 2.6, the kernel with just hang immediately with absolutely no error message.
If I change the faulty cable, both Linux 2.4 and 2.6 will run perfectly.
reply other threads:[~2004-04-23 17:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=045ULNS12@server5.heliogroup.fr \
--to=hubert.tonneau@fullpliant.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpt_linux_developer@lsil.com \
--cc=sjralston1@netscape.net \
/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