From: Shanker Balan <shanu@exocore.com>
To: Linux SCSI <linux-scsi@vger.kernel.org>
Subject: Re: aic7xxx: SCSI Bus Reset
Date: Thu, 26 Dec 2002 11:04:23 +0530 [thread overview]
Message-ID: <20021226053423.GA727@exocore.com> (raw)
In-Reply-To: <2149895408.1040745297@aslan.scsiguy.com>
Hello:
Justin T. Gibbs wrote,
> Can you provide the firmware revisions of these drives. Anything less
> than B440 is suspect. The behavior your report looks like the drives
> stop returning queued I/O. I have seen this before on at least B120,
> although it was when running at U320/packetized and not U160. My
> guess is that the bug in these early firmware revs is protocol
> agnostic.
Ok, here is a snip from dmesg:
SCSI subsystem driver Revision: 1.00
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
<Adaptec 29160 Ultra160 SCSI adapter>
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
blk: queue c256e218, I/O limit 4095Mb (mask 0xffffffff)
Vendor: QUANTUM Model: ATLAS10K3_18_SCA Rev: 020W
Type: Direct-Access ANSI SCSI revision: 03
blk: queue dfd8be18, I/O limit 4095Mb (mask 0xffffffff)
Vendor: QUANTUM Model: ATLAS10K3_73_SCA Rev: 020W
Type: Direct-Access ANSI SCSI revision: 03
blk: queue dfd8ba18, I/O limit 4095Mb (mask 0xffffffff)
Vendor: QUANTUM Model: ATLAS10K3_73_SCA Rev: 020W
Type: Direct-Access ANSI SCSI revision: 03
blk: queue dfd8b618, I/O limit 4095Mb (mask 0xffffffff)
scsi0:A:0:0: Tagged Queuing enabled. Depth 253
scsi0:A:1:0: Tagged Queuing enabled. Depth 253
scsi0:A:2:0: Tagged Queuing enabled. Depth 253
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
SCSI device sda: 35916548 512-byte hdwr sectors (18389 MB)
Partition check:
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 >
(scsi0:A:1): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
SCSI device sdb: 143666192 512-byte hdwr sectors (73557 MB)
sdb: sdb1 sdb2 sdb3
(scsi0:A:2): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
SCSI device sdc: 143666192 512-byte hdwr sectors (73557 MB)
sdc: sdc1 sdc2 sdc3
-- Shanu
http://shankerbalan.com/
--
It's a good thing we don't get all the government we pay for.
next prev parent reply other threads:[~2002-12-26 5:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 11:21 aic7xxx: SCSI Bus Reset Shanker Balan
2002-12-24 11:34 ` Mikael Abrahamsson
2002-12-24 12:09 ` Shanker Balan
2002-12-24 15:54 ` Justin T. Gibbs
2002-12-24 19:15 ` Mikael Abrahamsson
2002-12-25 9:46 ` Mikael Abrahamsson
2002-12-26 5:34 ` Shanker Balan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-24 18:35 Justin T. Gibbs
2002-12-26 7:29 ` Shanker Balan
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=20021226053423.GA727@exocore.com \
--to=shanu@exocore.com \
--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