Date: Tue, 1 Apr 1997 06:18:26 -0500 (EST) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!yoda.fdt.net!frankd, ponds!lakes.water.net!rivers Cc: ponds!freefall.cdrom.com!freebsd-hackers Subject: Re: aha2940 problems on 2.1.7.1. Message-ID: <199704011118.GAA01239@lakes.water.net>
next in thread | raw e-mail | index | archive | help
Frank Seltzer writes: > On Mon, 31 Mar 1997, Thomas David Rivers wrote: > > > > > Just to let everyone know what I've tried, in an attempt to diagnose > > the aha2940 problems in 2.1.7.1. > > > > I increased (to 20 minutes) all of the timeout parms in the scsi_scsi_cmd() > > calls in st.c; thinking that perhaps the write at the end of the time > > was timing out too soon; causing my problems. [Recall, my problem is that > > I can write to a Wangtek 5150ES (QIC-150) and fill the tape up; which locks > > down my 2.1.7.1 system completely - this is a 2.1.6.1 system with a 2.1.7.1 > > kernel.] > > > > However, this didn't help the problem, when the write that fills the tape > > up completes I get (on the console): > > > > sd0(ahc0:0:0): SCB 0x2 - timed out in command phase, SCSISIGI == 0x84 > > SEQADDR == 0x42 > > st0(ahc0:2:0): abort message in message buffer > > I once got this same message while doing a dump to a DAT tape. I am > running 2.2 compiled from source. > > FreeBSD 2.2-RELEASE #0: Sun Mar 23 15:52:15 EST 1997 > root@Kryten.nina.org:/usr/src/sys/compile/Kryten > > ahc0 <Adaptec 2940 SCSI host adapter> rev 0 int a irq 11 on pci0:12 > ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs > (ahc0:0:0): "MICROP 4421-07 0329SJ 0329" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 2047MB (4193360 512 byte sectors) > sd0(ahc0:0:0): with 4049 cyls, 7 heads, and an average 147 sectors/track > (ahc0:3:0): "HP HP35480A T503" type 1 removable SCSI 2 > st0(ahc0:3:0): Sequential-Access density code 0x13, variable blocks, > write-enabled > > It turned out that dump was corrupted somehow. I grabbed the binary from > another machine across the network that had 2.2 installed by ftp and it > cured the problem. > > I don't know if this is your problem but it worked for me. Nope - I'm using tar. I would be surprised if your problem simply wasn't time dependent; and the version of dump you were running wasn't actually the cause. Were you running 2.2 or 2.2.1 when you saw this? - Thanks - - Dave Rivers -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704011118.GAA01239>