From nobody  Fri Nov 20 21:54:28 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA12777;
          Fri, 20 Nov 1998 21:54:28 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199811210554.VAA12777@hub.freebsd.org>
Date: Fri, 20 Nov 1998 21:54:28 -0800 (PST)
From: jim@web-ex.com
To: freebsd-gnats-submit@freebsd.org
Subject: Buslogic BT948 in 2 boxes upgraded from SNAP to release, hangs on bt0 timeouts
X-Send-Pr-Version: www-1.0

>Number:         8778
>Category:       kern
>Synopsis:       [scsi] Buslogic BT948 in 2 boxes upgraded from SNAP to release, hangs on bt0 timeouts
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gibbs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Nov 20 22:00:00 PST 1998
>Closed-Date:    Sun Jul 31 12:02:32 GMT 2005
>Last-Modified:  Sun Jul 31 12:02:32 GMT 2005
>Originator:     Jim Cassata
>Release:        3.0 release
>Organization:
Web Express
>Environment:
FreeBSD jim.web-ex.com 3.0-RELEASE FreeBSD 3.0-RELEASE #25: 
Sun Nov  8 13:25:01 EST 1998     
root@jim.web-ex.com:/usr/src/sys/compile/JIM  i386 
>Description:
get kernel messages on two different machines, both dual cpu 
(one dual pentium 200 and one dual ppro 200) during which machines 
hang for 30 to 60 seconds, then resume.  both Tyan motherboards
with Buslogic BT948 scsi controllers. This never happened while 
running various snap versions, only after upgrading to 3.0 release.
both snaps and release have smp enabled.
Console messages are as 
follows from dmesg:  
(da0:bt0:0:6:0): CCB 0xf5692a80 - timed out
(da0:bt0:0:6:0): CCB 0xf5692a80 - timed out
bt0: No longer in timeout
(da0:bt0:0:6:0): CCB 0xf5694c00 - timed out
(da0:bt0:0:6:0): CCB 0xf5694c00 - timed out
bt0: No longer in timeout
(da0:bt0:0:6:0): CCB 0xf5692a00 - timed out
(da0:bt0:0:6:0): CCB 0xf5692a00 - timed out
bt0: No longer in timeout   
>How-To-Repeat:
happens on its own
>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: gibbs 
State-Changed-When: Fri Nov 20 22:47:06 PST 1998 
State-Changed-Why:  
Please provide a detailed description of your SCSI subsystem including 
the firmware revision of your BusLogic adapter and the make and model 
of the drive timing out. 

You also mention that previous snap shot releases did not show this error. 
Did these releases contain CAM? 

When do the hangs occur?  During periods of heavy I/O activity?  At boot? 

There have been a few bug fixes to the BusLogic driver since 3.0R.  You 
may want to try a recent 3.0-SNAP to see if it addresses your problem. 

Lastly, ensure that your adapter is running the latest firmware revision 
available from the Mylex web site. 


Responsible-Changed-From-To: freebsd-bugs->gibbs 
Responsible-Changed-By: gibbs 
Responsible-Changed-When: Fri Nov 20 22:47:06 PST 1998 
Responsible-Changed-Why:  
My driver 
State-Changed-From-To: feedback->closed 
State-Changed-By: matteo 
State-Changed-When: Sun Jul 31 12:02:15 GMT 2005 
State-Changed-Why:  
feedback timeout 

http://www.freebsd.org/cgi/query-pr.cgi?pr=8778 
>Unformatted:
