From owner-freebsd-hackers Tue Jun 4 02:39:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA29146 for hackers-outgoing; Tue, 4 Jun 1996 02:39:42 -0700 (PDT) Received: from fub46.zedat.fu-berlin.de (fub46.fddi1.fu-berlin.de [160.45.1.46]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA29137 for ; Tue, 4 Jun 1996 02:39:35 -0700 (PDT) Received: by fub46.zedat.fu-berlin.de (Smail3.1.29.1) id ; Tue, 4 Jun 1996 11:38:01 +0200 (MES) Message-Id: Date: Tue, 4 Jun 1996 11:38:01 +0200 (MES) From: gusw@zedat.fu-berlin.de (Gunther Schadow) To: davidg@Root.COM Subject: Re: Adaptec 2940 U makes fatal bus resets! Cc: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>void >>ahc_scb_timeout(unit, ahc, scb) >>... > >> timeout(ahc_timeout, (caddr_t)scb, ( TOFACT * 2 * hz)); > >2 seconds was already a lot. The fatal problem is probably in poor handling >of SCSI errors. It seems conceivable that certain types of failures that require a recalibrate, or certain types of SCSI devices (like CDROM drives) that need to spin up first could trigger an unnecessary timeout with it set to only 2 seconds. It should probably be increased to at least 10 seconds, but I'll defer to whatever Justin thinks is needed. I have to correct myself, the Problem is not fixed by the lengthening of the timeout times. The machine just hangs longer, before it comes up with this BUS DEVICE RESET message on my sd(0). This problem is so awfully severe, I hope that I am not the only one who has it, and that there are already some people who know what to do (I don't) working hard on it. I'm so disappointed because I never had to mistrust my BSD kernel so much: 386BSD 0.0new had longer uptimes then I experience today! sigh, Gunther Schadow