From nobody@FreeBSD.ORG Tue Nov 23 19:35:51 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 0B2CA1512A; Tue, 23 Nov 1999 19:35:50 -0800 (PST)
Message-Id: <19991124033550.0B2CA1512A@hub.freebsd.org>
Date: Tue, 23 Nov 1999 19:35:50 -0800 (PST)
From: feisal@uwi.tt
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: T400s hangs on any access
X-Send-Pr-Version: www-1.0

>Number:         15069
>Category:       kern
>Synopsis:       T400s hangs on any access
>Confidential:   no
>Severity:       critical
>Priority:       low
>Responsible:    gibbs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 23 19:40:01 PST 1999
>Closed-Date:    Mon Oct 1 18:55:22 PDT 2001
>Last-Modified:  Mon Oct 01 18:56:12 PDT 2001
>Originator:     Feisal Mohammed
>Release:        3.3-RELEASE
>Organization:
University of the West Indies
>Environment:
FreeBSD 3.3-RELEASE
Advansys PCI ASB3940UA SCSI card
HP T4000s (v 1.10) Travan drive
Plextor 12Plex CDrom
Pentium 120MHz
64MB Ram
2 IDE disks

>Description:
The HP T4000s drive is seen correctly on bootup but any command
such as "mt status", hangs the SCSI bus. 
>How-To-Repeat:
mt status or any other mt command
>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->mjacob 
Responsible-Changed-By: billf 
Responsible-Changed-When: Tue Nov 23 19:43:16 PST 1999 
Responsible-Changed-Why:  
over to tape driver maintainer. 
State-Changed-From-To: open->feedback 
State-Changed-By: mjacob 
State-Changed-When: Tue Nov 23 19:53:05 PST 1999 
State-Changed-Why:  
Need more information than this. Like, kernel messages, configuration, etc. 
I'll be out of town for a week. In the interim, try and build a kernel 
with CAMDEBUG defined and turn on debugging for the drive prior to trying 
to issue status (e.g. 'camcontrol -Ic 0:5:0' if it's at target 5 on scsibus0). 
State-Changed-From-To: feedback->open 
State-Changed-By: mjacob 
State-Changed-When: Fri Dec 3 12:15:01 PST 1999 
State-Changed-Why:  
Got information back. First problem I see is: 

Nov 24 08:55:09 feisalpc /kernel: (sa0:adv0:0:4:0): LOAD UNLOAD. CDB: 1b 0 0 0 
1 0  
Nov 24 08:56:08 feisalpc /kernel: (sa0:adv0:0:4:0): Timed out 

The Load/Unload period is probably a tad short. The user is requested too 
replace all 60000 occurrences in calls to scsi_load_unload in scsi_sa.c 
with (1 * 60 * 60 * 1000). Either that or comment out the load/unload and 
then recontact if this helps. A one minute timeout *may* be too short. It 
is also possible that this is such a broken drive that the f/w crashes 
with a load/unload command- in which case we'll have to invent a new 
quirk. 
Responsible-Changed-From-To: mjacob->gibbs 
Responsible-Changed-By: mjacob 
Responsible-Changed-When: Mon Dec 13 11:13:06 PST 1999 
Responsible-Changed-Why:  
It appears this is an Advansys HBA specific problem. 

From: Dag-Erling Smorgrav <des@ofug.org>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: kern/15069
Date: 13 Mar 2001 05:09:23 +0100

 Can you tell us if you're still having this problem with newer FreeBSD
 versions and / or newer firmware revisions?
 
 DES
 -- 
 Dag-Erling Smorgrav - des@ofug.org
State-Changed-From-To: feedback->closed 
State-Changed-By: mjacob 
State-Changed-When: Mon Oct 1 18:55:22 PDT 2001 
State-Changed-Why:  
This has been in feedback state for 6 months. Closed.  

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15069 
>Unformatted:
