[2105] in linux-scsi channel archive
eata_abort (timeout) sanity lost
daemon@ATHENA.MIT.EDU (Ed Orcutt)
Wed Jul 2 21:26:39 1997
Reply-to: edo@eosys.com
To: mike@i-Connect.Net (Michael Neuffer)
Cc: linux-scsi@vger.rutgers.edu
Date: Wed, 02 Jul 1997 14:37:41 -1000
From: Ed Orcutt <edo@eosys.com>
Greetings!
I am have a terrible time with the EATA_DMA driver. After nearly two years
of faithful service my DPT PM2024A/9X is no longer happy. Perhaps the move
to a new motherboard, or the new pair of Quantum Fireballs. Below is an
excerpt from the system log just prior to failure (via timeout). I would
love nothing more than to have a silly oversight pointed out to me, but
alas after nearly a week of trial-n-error I'm at a lose for options.
I've moved my DPT PM2024A/9X SCSI adaptor onto a new motherboard that will
server as my router/gateway/website/mailserv. To that end I have beat on
the new twin Quantum Fireballs with a pair of `bonnie's ... sadly each time
I've run bonnie the EATA_DMA driver aborts due to a timeout. I've tried the
Linux 2.0.29 and 2.0.30, EATA_DMA and EATA drivers, with virtually the
same results. Below are the system logs for the 2.0.30 EATA_DMA just prior
to failure.
Here are some of the other system particulars that *may* be of import:
Motherboard: SuperMicro P5STE
CPU: Intel Pentium 133MHz
Partial Boot message:
EATA (Extended Attachment) driver version: 2.59b
developed in co-operation with DPT
(c) 1993-96 Michael Neuffer, mike@i-Connect.Net
Registered HBAs:
HBA no. Boardtype Revis EATA Bus BaseIO IRQ DMA Ch ID Pr QS S/G IS
scsi0 : PM2024A/9X v06D.4 2.0c PCI 0x0510 11 BMST 1 7 N 64 64 N
scsi0 : EATA (Extended Attachment) HBA driver
scsi : 1 host.
Started kswapd v 1.4.2.2
Vendor: QUANTUM Model: FIREBALL ST3.2S Rev: 0F0C
Type: Direct-Access ANSI SCSI revision: 02
Vendor: QUANTUM Model: FIREBALL ST3.2S Rev: 0F0C
Type: Direct-Access ANSI SCSI revision: 02
scsi0: queue depth for target 1 on channel 0 set to 32
scsi0: queue depth for target 2 on channel 0 set to 32
Any help would be *greatly* appreicated! If additional information is
required please let me know!
Here's the system log:
Jul 2 03:03:35 gecko kernel: scsi : aborting command due to timeout : pid 938757, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 4c 64 a8 00 00 60 00
Jul 2 03:03:35 gecko kernel: eata_abort called pid: 938757 target: 1 lun: 0 reason 3
Jul 2 03:03:35 gecko kernel: Returning: SCSI_ABORT_BUSY
Jul 2 03:03:51 gecko kernel: scsi : aborting command due to timeout : pid 938757, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 4c 64 a8 00 00 60 00
Jul 2 03:03:52 gecko kernel: eata_abort called pid: 938757 target: 1 lun: 0 reason 3
Jul 2 03:03:52 gecko kernel: Returning: SCSI_ABORT_BUSY
Jul 2 03:03:52 gecko kernel: SCSI host 0 abort (pid 938757) timed out - resetting
Jul 2 03:03:52 gecko kernel: SCSI bus is being reset for host 0 channel 0.
Jul 2 03:03:52 gecko kernel: eata_reset called pid:938757 target: 1 lun: 0 reason 3
Jul 2 03:03:52 gecko kernel: eata_reset: slot 0 in reset, pid 941746.
.............
Jul 2 03:03:52 gecko kernel: eata_reset: slot 63 in reset, pid 941745.
Jul 2 03:03:52 gecko kernel: eata_reset: board reset done, enabling interrupts.
Jul 2 03:03:52 gecko kernel: eata_dma: int_handler, reseted command pid 938757 returned
Jul 2 03:03:52 gecko kernel: eata_dma: int_handler, reseted command pid 941735 returned
Jul 2 03:03:52 gecko kernel: eata_reset: interrupts disabled again.
Jul 2 03:03:52 gecko kernel: eata_reset: slot 0 locked, DID_RESET, pid 941746 done.
.............
Jul 2 03:03:53 gecko kernel: eata_reset: slot 63 locked, DID_RESET, pid 941745 done.
Jul 2 03:03:53 gecko kernel: eata_dma: int_handler, reseted command pid 941736 returned
Jul 2 03:03:53 gecko kernel: eata_reset: exit, pending.
Jul 2 03:03:53 gecko kernel: eata_dma: int_handler, reseted command pid 941737 returned
.............
Many more "eata_dma: int_handler, reseted command" until machine locks up
-later, edo
