From owner-freebsd-scsi Tue Apr 8 17:24:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA14978 for freebsd-scsi-outgoing; Tue, 8 Apr 1997 17:24:53 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA14973 for ; Tue, 8 Apr 1997 17:24:50 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id SAA29661; Tue, 8 Apr 1997 18:24:46 -0600 (MDT) Message-Id: <199704090024.SAA29661@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Petri Helenius cc: "Justin T. Gibbs" , scsi@FreeBSD.org Subject: Re: Latest round around the AIC7xxx In-reply-to: Your message of "Tue, 08 Apr 1997 21:57:49 +0300." <199704081857.VAA02087@silver.sms.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Apr 1997 18:23:03 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Justin T. Gibbs writes: > > Okay, I have a fix for that panic, but I'm still looking for reasons > > leading to the original timeout. > > > > >panic: Couldn't find busy SCB > > >That might be easier to figure out when the system does not panic when >the error occurs. > >Is the fix committed to 2.2-STABLE? I could cvsup my tree and build a >new kernel and test it. > >Pete No. It won't be fixed until I get back in town late tomorrow. I don't think that fixing the panic will give any indication of why the timeout is occurring though. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================