From: Tugrul Galatali <tugrul@galatali.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 Adaptec aic7899 Ultra160 SCSI grief
Date: 24 Jul 2003 21:02:20 -0400 [thread overview]
Message-ID: <1059094940.386.7.camel@duality.galatali.com> (raw)
In-Reply-To: <1369182704.1059067061@aslan.btc.adaptec.com>
On Thu, 2003-07-24 at 13:17, Justin T. Gibbs wrote:
[snip snip]
> came back with a tag identifier of 0x20. This looks like a drive
> firmware bug, but a bug in the aic7xxx driver cannot be completely
> ruled out without a SCSI bus trace of the failure.
[snip snip]
SCSI bus trace = logging? I started poking around online for how that
works, and I found repeatable case of what I hope is the same error (one
tar from the bad scsi disk piping into another tar onto a good scsi
disk). One problem I ran into is that scsi_logging=X as a kernel
parameter doesn't seem to work in 2.6.0-test1, so I put in a S00 init
script to do the:
echo "scsi log all" > /proc/scsi/scsi
The resulting /var/log/messages is ~18M, compressed down to 300k.
http://acm.cs.nyu.edu/~tugrul/scsi/messages.bz2
Is this what you need?
I did a quick test of the above case on a 2.4.21 kernel and it didn't
seem to trigger anything evil.
If it turns out to be a firmware problem, is the firmware upgradeable
or do I have to buy a new drive, in which case is there a blacklist?
Tugrul Galatali
next prev parent reply other threads:[~2003-07-25 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 11:17 2.6.0-test1 Adaptec aic7899 Ultra160 SCSI grief Tugrul Galatali
2003-07-24 17:17 ` Justin T. Gibbs
2003-07-25 1:02 ` Tugrul Galatali [this message]
2003-07-25 13:43 Cress, Andrew R
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=1059094940.386.7.camel@duality.galatali.com \
--to=tugrul@galatali.com \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).