[2107] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Re: eata_abort (timeout) sanity lost

daemon@ATHENA.MIT.EDU (Ed Orcutt)
Thu Jul 3 22:49:39 1997

Reply-to: edo@eosys.com
To: mike@i-Connect.Net (Michael Neuffer)
cc: linux-scsi@vger.rutgers.edu
In-reply-to: edo's message of Wed, 02 Jul 1997 14:37:41 -1000.
Date: 	Thu, 03 Jul 1997 16:46:43 -1000
From: Ed Orcutt <edo@eosys.com>

My apologies for wasting time and bandwidth. There is mud on my face :-(

Did I make sure the cable was properly terminated? Yes.
Was I sure? YES!
Check it again! I've checked it a dozen times and ... oops :-{

[Long story explaining my stupidity deleted.]

End result ... pilot error. Pardon the waste of time and bandwidth.

-later, edo (No really, I *did* check! ... sigh)

>> Here's what Ed Orcutt said:
 > 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:

 [Snip 8< 8< 8< ...]


home help back first fref pref prev next nref lref last post