From: James Bottomley <James.Bottomley@SteelEye.com>
To: bugme-daemon@bugzilla.kernel.org, freelsjd@ornl.gov
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [Bug 8366] aic79xx and aic7xxx driver issues
Date: Tue, 24 Jul 2007 22:14:43 -0400 [thread overview]
Message-ID: <1185329683.3488.46.camel@localhost.localdomain> (raw)
In-Reply-To: <20070725010525.614621080E4@picon.linux-foundation.org>
On Tue, 2007-07-24 at 18:05 -0700, bugme-daemon@bugzilla.kernel.org
wrote:
> --> (http://bugzilla.kernel.org/attachment.cgi?id=12126&action=view)
> failed driver dmesg
>
> This driver fails at time of boot up. there are many scsi errors shown in the
> output. It is the "new" aic7xxx driver.
This is about the most significant line
> (scsi0:A:3:0): parity error detected in Data-in phase. SEQADDR(0x84) SCSIRATE(0x80)
The SCSIRATE indicates wide. I'd bet this is a narrow device; in which case, does
echo 0 > /sys/class/spi_transport/target0:0:3/max_wide
and then triggering a revalidate with
echo 1 > /sys/class/spi_transport/target0:0:3/revalidate
produce anything different?
James
next parent reply other threads:[~2007-07-25 2:14 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 ` James Bottomley [this message]
[not found] ` <1185461780.14419.17.camel@fea.ornl.gov>
2007-07-26 15:05 ` [Bug 8366] aic79xx and aic7xxx driver issues James Bottomley
2007-07-26 20:00 ` Freels, James D.
2007-07-26 20:46 ` James Bottomley
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=1185329683.3488.46.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