Bug 15069

Summary: T400s hangs on any access
Product: Base System Reporter: feisal <feisal>
Component: kernAssignee: Justin T. Gibbs <gibbs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 3.3-RELEASE   
Hardware: Any   
OS: Any   

Description feisal 1999-11-24 03:40:01 UTC
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
Comment 1 bill fumerola freebsd_committer freebsd_triage 1999-11-24 03:43:16 UTC
Responsible Changed
From-To: freebsd-bugs->mjacob

over to tape driver maintainer. 
Comment 2 Matt Jacob freebsd_committer freebsd_triage 1999-11-24 03:53:05 UTC
State Changed
From-To: open->feedback

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). 
Comment 3 Matt Jacob freebsd_committer freebsd_triage 1999-12-03 20:15:01 UTC
State Changed
From-To: feedback->open

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. 
Comment 4 Matt Jacob freebsd_committer freebsd_triage 1999-12-13 19:13:06 UTC
Responsible Changed
From-To: mjacob->gibbs

It appears this is an Advansys HBA specific problem. 

Comment 5 des 2001-03-13 04:09:23 UTC
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
Comment 6 Matt Jacob freebsd_committer freebsd_triage 2001-10-02 02:55:22 UTC
State Changed
From-To: feedback->closed

This has been in feedback state for 6 months. Closed.