From: Berkley Shands <berkley@cs.wustl.edu>
To: gibbs@scsiguy.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, pbadari@us.ibm.com
Subject: x86_64 + 2.6.1-rc3 panics on aic79xx
Date: Thu, 8 Jan 2004 10:27:42 -0600 (CST) [thread overview]
Message-ID: <200401081627.i08GRgZ0000027670@mudpuddle.cs.wustl.edu> (raw)
The default scsi driver for the adaptec 39320 (aic79xx) v 1.3.11
STILL causes panics and BUG halts when a drive decides to have troubles.
I have a 2.6.1-rc3 X86_64 kernel, with
ftp://ftp.x86-64.org/pub/linux/v2.6/x86_64-2.6.1rc2-1.bz2
applied. On the first scsi error, the kernel bughalts "BRKADRINT".
The 2.0.5 version of the aic79xx driver will not boot with the
x86-64 patch, regardless of the iommu=[off | nomerge | noforce] setting.
If I use a vanilla 2.6.1-rc3 kernel, and apply the 2.0.5 driver,
the system will not boot, stalling with a scsi0: Unexpected SEQINTCODE 26 (bad scb).
If I disable the iommu, (iommu=off), then the kernel will boot, but the
system does not work, as the TG3 Gig-E driver is 32 bit.
When the 2.6.1-rc3 + x86_64 patch ran, the I/O throughput on
raid0 was 50% of the 2.6.0 stock kernel (340-360 MB/Sec vs 670-880 MB/Sec).
The ioctl to change /dev/md0 read ahead parameter is being called.
There were some changes to the read ahead values (at least raid5) in
-rc3. Ouch!
A pure stock 2.6.1-rc3 kernel also bug halts with sg corruption
on the first scsi retry. It seems that the iommu has serious issues
with all three variants of current kernel patches.
berkley
next reply other threads:[~2004-01-08 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 16:27 Berkley Shands [this message]
2004-01-08 17:26 ` James Bottomley
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=200401081627.i08GRgZ0000027670@mudpuddle.cs.wustl.edu \
--to=berkley@cs.wustl.edu \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/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
all inboxes | Powered by JetHome®