Date: Wed, 31 May 2000 19:58:51 -0400 From: John <papalia@udel.edu> To: "Kenneth D. Merry" <ken@kdm.org> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <4.3.1.2.20000531195721.00ad3b50@mail.udel.edu> In-Reply-To: <20000531175139.A86282@panzer.kdm.org> References: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Hi all, > > > > I ran into some really odd (to me, that is) problems. Via Samba I was > > trying to move items from my windows PC to my FreeBSD (4.0-Stable) > > box. During these transfers I will occasionally get the following error > > which (as far as I've figured out) requires a complete power-down to > > correct. Any thoughts? > > > > Thanks, > > John > > > > > > The error is: > > > > May 31 18:46:08 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed out > > while idle, SEQADDR == 0xa > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Queuing a BDR SCB > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Bus Device Reset > Message Sent > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed out in > > Message-out phase, SEQADDR == 0x157 > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): no longer in timeout, > > status = 34b > > May 31 18:46:20 merlin /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs > > aborted > > May 31 18:46:22 merlin /kernel: (da1:ahc0:0:8:0): Invalidating pack > >The drive is going "out to lunch" and not coming back for a full minute. > >We hit it with a bus device reset to wake it up, and then it appears we >sent a bus reset after we got another timeout in the message out phase. > >Perhaps something had a stuck signal on the bus. Is it possible to kick-start or "burp" the bus when that happens, other than resetting the box? > > da1 at ahc0 bus 0 target 8 lun 0 > > da1: <MICROP 3391WS x43h> Fixed Direct Access SCSI-2 device > > da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > > da1: 8681MB (17780058 512 byte sectors: 255H 63S/T 1106C) > >If I had to guess, I'd say it is a firmware problem with the drive, but >it's hard to say for sure. You might also want to check your cabling and >termination. I'll check the cables and terminations just as soon as my backup finishes. I'm not sure if it would be either though since this drive configuration has been running fine for almost 6 months. Thanks again, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.1.2.20000531195721.00ad3b50>