From owner-freebsd-hackers Sat Jan 18 09:50:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA21826 for hackers-outgoing; Sat, 18 Jan 1997 09:50:41 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA21809 for ; Sat, 18 Jan 1997 09:50:38 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA02810; Sat, 18 Jan 1997 12:50:06 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sat, 18 Jan 1997 12:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id IAA12087 for ; Sat, 18 Jan 1997 08:51:11 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id IAA02954 for freebsd-hackers@freefall.cdrom.com; Sat, 18 Jan 1997 08:54:48 -0500 (EST) Date: Sat, 18 Jan 1997 08:54:48 -0500 (EST) From: Thomas David Rivers Message-Id: <199701181354.IAA02954@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Re: 2.1.6.1 - SCSI problems (infinite bus reset) w/Aha2940UW (&2.2) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > As Thomas David Rivers wrote: > > > Then, after mounting some disk space, I did the following > > > > tar cvf . /dev/rst0 > > > > after than runs for awhile; I hit cntrl-C to stop the 'tar' and > > *whamo* - everything begins the reset phase. > > I'm somewhat suspecting your tape drive, nevertheless. Do you have > the chance to test it with another controller (like an AHA-1540)? We > all know that the ahc driver has some rough edges right now (that's > why 2.2 isn't out yet). > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > Hmmm... Well, it worked before the Sept. 96 changes in 2.1.5-STABLE. It's possible that the day I built that kernel my tape-drive "went south"; but it seems to be a big coincidence. Prior to the 2940uw it was plugged into a 1542B. It worked fine then; but that was in 2.1.5-RELEASE. The last time it was configured like that was July, 1996. It seems to be a timing problem - is there some timeout for commands that I can adjust? I can boot 2.1.5-RELEASE (boot and fixit trick again) and make sure it still works there; then we'd know it was a software change - how's that? - Dave Rivers -