From owner-freebsd-scsi  Tue Apr  8 11:58:04 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA23870
          for freebsd-scsi-outgoing; Tue, 8 Apr 1997 11:58:04 -0700 (PDT)
Received: from silver.sms.fi (silver.sms.fi [194.111.122.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA23865
          for <scsi@FreeBSD.org>; Tue, 8 Apr 1997 11:57:59 -0700 (PDT)
Received: (from pete@localhost) by silver.sms.fi (8.8.5/8.7.3) id VAA02087; Tue, 8 Apr 1997 21:57:49 +0300 (EEST)
Date: Tue, 8 Apr 1997 21:57:49 +0300 (EEST)
Message-Id: <199704081857.VAA02087@silver.sms.fi>
From: Petri Helenius <pete@sms.fi>
To: "Justin T. Gibbs" <gibbs@plutotech.com>
Cc: scsi@FreeBSD.org
Subject: Re: Latest round around the AIC7xxx 
In-Reply-To: <199704081626.KAA25178@pluto.plutotech.com>
References: <199704080741.KAA00570@silver.sms.fi>
	<199704081626.KAA25178@pluto.plutotech.com>
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