From: James Bottomley <James.Bottomley@SteelEye.com>
To: freelsjd@ornl.gov
Cc: bugme-daemon@bugzilla.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [Bug 8366] aic79xx and aic7xxx driver issues
Date: Thu, 26 Jul 2007 16:46:44 -0400 [thread overview]
Message-ID: <1185482804.3501.87.camel@localhost.localdomain> (raw)
In-Reply-To: <1185480022.14419.58.camel@fea.ornl.gov>
On Thu, 2007-07-26 at 16:00 -0400, Freels, James D. wrote:
> 9) the output from the commands you asked for are shown below for the
> 2.6.22.1 kernel. They indicate parity errors on the changer at scsi
> id=3. Also, when booting up under 2.6.18.8, the linux media changer
> scsi device works and initializes; when booting up under 2.6.22.1, it
> does not; probably because of the same parity errors ?
>
> target0:0:3: Beginning Domain Validation
> target0:0:3: asynchronous
> target0:0:3: FAST-20 WIDE SCSI 40.0
^^^^
This is the problem.
Something in the transport class is causing WIDE to be set regardless of
the max_width setting ... this looks to be a bug in the aic7xxx
transport class implementation
> MB/s ST (50 ns, offset 32)
> (scsi0:A:3:0): parity error detected in Data-in phase. SEQADDR(0x1a6)
> SCSIRATE(0x95)
Once it goes wide on a narrow device, you get immediate parity errors
half the time, because you're missing the upper 8 bits for the parity
calculation.
I'll see if I can trace this inside the driver ... naturally, I have no
aic7xxx setup where I only have a narrow device.
James
next prev parent reply other threads:[~2007-07-26 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070725010525.614621080E4@picon.linux-foundation.org>
2007-07-25 2:14 ` [Bug 8366] aic79xx and aic7xxx driver issues James Bottomley
[not found] ` <1185461780.14419.17.camel@fea.ornl.gov>
2007-07-26 15:05 ` James Bottomley
2007-07-26 20:00 ` Freels, James D.
2007-07-26 20:46 ` James Bottomley [this message]
2007-07-26 21:13 ` James Bottomley
[not found] ` <1185484597.14419.65.camel@fea.ornl.gov>
2007-07-26 21:29 ` James Bottomley
2007-07-26 21:37 ` Freels, James D.
2007-07-26 21:44 ` James Bottomley
2007-07-26 21:52 ` Freels, James D.
2007-07-26 21:57 ` Freels, James D.
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=1185482804.3501.87.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=freelsjd@ornl.gov \
--cc=linux-scsi@vger.kernel.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