From: Nick Papadonis <nick@coelacanth.com>
To: linux-kernel@vger.kernel.org
Cc: gibbs@scsiguy.com
Subject: AIC7XXX + v2.4.18 problems?
Date: Wed, 19 Jun 2002 11:09:13 -0400 [thread overview]
Message-ID: <m3k7ov2tly.fsf@noop.bombay> (raw)
Is anyone else having problems with the AIC7XXX driver using a AHA-29160
controller? I believe my kernel is going into a unrecoverable spin-lock
when there is high SCSI load. I'm assuming this because the keyboard
lights still function and network still replies to pings.
In addition the 'st' driver returns with unrecoverable errors when
trying to tar to tape. This usually occurs after a few hundred
megabytes have been pushed through a device.
My setup is :
- AHA-29160N controller
- Internal 50 PIN / SCSI-2 port in use
- See below for connected drives
I tested the following kernels and they display similar behavior:
- v2.4.9
- v2.4.18
- v2.4.18 with updated 7XXX driver
- v2.4.19-pre10
Any insight is appreciated.
- Nick
DETAILS:
Jun 19 01:25:15 bombay kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
Jun 19 01:25:15 bombay kernel: <Adaptec 29160 Ultra160 SCSI adapter>
Jun 19 01:25:15 bombay kernel: aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
Jun 19 01:25:15 bombay kernel:
Jun 19 01:25:15 bombay kernel: Vendor: IBM Model: DNES-318350 Rev: SAH0
Jun 19 01:25:15 bombay kernel: Type: Direct-Access ANSI SCSI revision: 03
Jun 19 01:25:15 bombay kernel: Vendor: IBM Model: DCAS-34330 Rev: S65A
Jun 19 01:25:15 bombay kernel: Type: Direct-Access ANSI SCSI revision: 02
Jun 19 01:25:15 bombay kernel: Vendor: PLEXTOR Model: CD-R PX-W124TS Rev: 1.07
Jun 19 01:25:15 bombay kernel: Type: CD-ROM ANSI SCSI revision: 02
Jun 19 01:25:15 bombay kernel: scsi0:A:0:0: Tagged Queuing enabled. Depth 253
Jun 19 01:25:15 bombay kernel: scsi0:A:2:0: Tagged Queuing enabled. Depth 253
Jun 19 01:25:15 bombay kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Jun 19 01:25:15 bombay kernel: Attached scsi disk sdb at scsi0, channel 0, id 2, lun 0
Jun 19 01:25:15 bombay kernel: (scsi0:A:0): 20.000MB/s transfers (20.000MHz, offset 31)
Jun 19 01:25:15 bombay kernel: SCSI device sda: 35843670 512-byte hdwr sectors (18352 MB)
Jun 19 01:25:15 bombay kernel: sda: sda1 sda2 sda3
Jun 19 01:25:15 bombay kernel: (scsi0:A:2): 20.000MB/s transfers (20.000MHz, offset 15)
Jun 19 01:25:15 bombay kernel: SCSI device sdb: 8467200 512-byte hdwr sectors (4335 MB)
Jun 19 01:25:15 bombay kernel: sdb: unknown partition table
[root@bombay root]# more /proc/scsi/aic7xxx/0
Adaptec AIC7xxx driver version: 6.2.8
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
Serial EEPROM:
0x439b 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a
0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a
0xb8f4 0x7c5d 0x2807 0x0010 0x0300 0xffff 0xffff 0xffff
0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x16b0
Channel A Target 0 Negotiation Settings
User: 40.000MB/s transfers (40.000MHz DT, offset 255)
Goal: 20.000MB/s transfers (20.000MHz, offset 31)
Curr: 20.000MB/s transfers (20.000MHz, offset 31)
Channel A Target 0 Lun 0 Settings
Commands Queued 245659
Commands Active 0
Command Openings 64
Max Tagged Openings 64
Device Queue Frozen Count 0
Channel A Target 1 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 2 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Goal: 20.000MB/s transfers (20.000MHz, offset 15)
Curr: 20.000MB/s transfers (20.000MHz, offset 15)
Channel A Target 2 Lun 0 Settings
Commands Queued 5
Commands Active 0
Command Openings 253
Max Tagged Openings 253
Device Queue Frozen Count 0
Channel A Target 3 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Goal: 40.000MB/s transfers (40.000MHz, offset 127)
Curr: 3.300MB/s transfers
Channel A Target 3 Lun 0 Settings
Commands Queued 1
Commands Active 0
Command Openings 1
Max Tagged Openings 0
Device Queue Frozen Count 0
Channel A Target 4 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 5 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 6 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 7 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 8 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 9 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 10 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 11 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 12 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 13 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 14 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
Channel A Target 15 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
next reply other threads:[~2002-06-19 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 15:09 Nick Papadonis [this message]
2002-06-19 15:15 ` AIC7XXX + v2.4.18 problems? Nick Papadonis
2002-06-19 15:35 ` Doug Ledford
2002-06-19 21:49 ` J.A. Magallon
2002-06-20 19:16 ` Doug Ledford
2002-06-20 22:31 ` J.A. Magallon
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=m3k7ov2tly.fsf@noop.bombay \
--to=nick@coelacanth.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