Date: Sat, 7 Nov 1998 15:29:06 -0330 From: "Andrea Neville" <andrea@publib.nf.ca> To: "AIC7xxx Developers List" <aic7xxx@FreeBSD.ORG> Subject: Re: abort using AHA2940UW with x86 Linux RedHat 5.2 (kernel-2.0.36-pre) Message-ID: <001f01be0a80$b403eb80$010200c0@orca>
next in thread | raw e-mail | index | archive | help
>We have several Linux boxen here with the same hardware configuration, but
>on the one where we first decided to install RedHat 5.2, we get the ff.
>errors:
>
>scsi : aborting command due to timeout : pid 48641, scsi0, channel 0, id 0,
lun 0 Write (10) 00 00 7a 69 a6 00 00 04 00
>scsi : aborting command due to timeout : pid 48642, scsi0, channel 0, id 0,
lun 0 Write (10) 00 00 7a 69 ac 00 00 02 00
>scsi : aborting command due to timeout : pid 48643, scsi0, channel 0, id 0,
lun 0 Write (10) 00 00 7a 6b ba 00 00 f4 00
>SCSI host 0 abort (pid 48641) timed out - resetting
>SCSI bus is being reset for host 0 channel 0.
>
>
>It seems to happen when there is a lot of harddisk activity. The box just
>freezes cold for a couple of seconds and then resumes operation. What's
>the problem? What is the recommended solution? (recompile the kernel with
>newer drivers, use kernel-2.0.35, etc?)
I have an almost identical problem. There is no problem until there is
moderate to heavy disk usage. Then I get multiple SCSI timeout errors, the
whole thing freezes up for a little while and sometimes doesn't unfreeze. I
have included my particulars below.
Since it works sorta I am not sure of where to start looking. one thing I am
not sure of is this automatic termination warning?
Thanks
Andrea Neville
Relevant parts of dmesg
----
>>> kernel: show kernel version <<<
Linux version 2.0.33 (root@buildmeister.caldera.com) (gcc version 2.7.2.3)
#1 W8
Starting kswapd v 1.4.2.2
>>> kernel: mounting root filesystem <<<
VFS: Mounted root (ext2 filesystem).
aic7xxx: <Adaptec AIC-7880 Ultra SCSI host adapter> at PCI 7
aic7xxx: Warning - detected auto-termination. Please verify driver
detected settings and use manual termination if necessary.
aic7xxx: BIOS enabled, IO Port 0xfc00, IO Mem 0xfedff000, IRQ 9, Revision C
aic7xxx: Wide Channel, SCSI ID 7, 16/16 SCBs, QFull 16, QMask 0x1f
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 4.1.1/3.2.1
scsi : 1 host.
scsi0: Scanning channel A for devices.
Vendor: WDIGTL Model: ENTERPRISE Rev: 1.91
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: WDIGTL Model: ENTERPRISE Rev: 1.91
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 2, lun 0
Vendor: HP Model: T4000s Rev: 1.10
Type: Sequential-Access ANSI SCSI revision: 02
Detected scsi tape st0 at scsi0, channel 0, id 4, lun 0
SCSI device sda: hdwr sector= 512 bytes. Sectors= 8515173 [4157 MB] [4.2 GB]
sda: sda1 sda2 sda3
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8515173 [4157 MB] [4.2 GB]
sdb: sdb1 sdb2
Typical Error messages
scsi : aborting command due to timeout : pid 134357, scsi0, channel 0, id 0,
lun 0 Write (6) 04 c3 27 f4 00
scsi : aborting command due to timeout : pid 134361, scsi0, channel 0, id 2,
lun 0 Write (6) 0e 40 67 02 00
scsi : aborting command due to timeout : pid 134360, scsi0, channel 0, id 0,
lun 0 Write (6) 04 c4 1b f4 00
scsi : aborting command due to timeout : pid 134362, scsi0, channel 0, id 2,
lun 0 Write (6) 0e 80 67 02 00
SCSI host 0 abort (pid 134357) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
SCSI host 0 abort (pid 134362) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
SCSI host 0 abort (pid 134361) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
SCSI host 0 abort (pid 134361) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
SCSI host 0 channel 0 reset (pid 134361) timed out - trying harder
SCSI bus is being reset for host 0 channel 0.
SCSI host 0 reset (pid 134361) timed out - trying to shake it loose
SCSI bus is being reset for host 0 channel 0.
SCSI host 0 reset (pid 134361) timed out again -
probably an unrecoverable SCSI bus or device hang
-----
This one is when trying to copy from one physical hard drive to the other.
Anything involving both drives usually results in a crash. if only one drive
is involved with the particular disk activity it freezes up and *eventually*
returns control.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001f01be0a80$b403eb80$010200c0>