Bug 39805

Summary:	4.6R install panics with umass0 device connected
Product:	Base System	Reporter:	H. Eckert <ripley>
Component:	kern	Assignee:	freebsd-usb (Nobody) <usb>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.6-RELEASE
Hardware:	Any
OS:	Any

Description H. Eckert 2002-06-24 22:00:05 UTC

With lots of delay after the ATAPI CD drives, the umass0 driver reports
umass0: Invalid CSW: tag 0 should be 13.
Sysinstall shows "Probing devices, please wait" and the kernel panics with

panic: integer divide fault

Fix: 

Physically disconnect the drive or disable USB in BIOS.  Probably
inserting a CF or similar card into the drive could work too,
but unfortunatly I don't have any for the time being.
How-To-Repeat: 
Insert 4.6 CD in my machine and boot it.

Comment 1 H. Eckert 2002-07-04 11:16:57 UTC

Further investigation indicates the umass0 driver is allergic to the device.
I can look up the virtual scsi bus with camcontrol but any access to
the device (like "fdisk da0" with medium inserted) results in a panic.

It seems there are two issues at hand:
1.) The device is not accessed properly (presumably it should just be
like any other generic mass storage USB drive)
2.) The driver's reaction on error conditions is faulty.

Comment 2 Kris Kennaway freebsd_committer

2003-07-14 11:31:57 UTC

State Changed
From-To: open->feedback

Does this problem persist in recent releases?  If so, 
please obtain a debugging traceback as explained in 
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html

Comment 3 Kris Kennaway freebsd_committer

2003-07-18 01:50:13 UTC

Responsible Changed
From-To: freebsd-bugs->joe

Assign to USB maintainer

Comment 4 joe freebsd_committer

2004-11-10 10:57:03 UTC

Responsible Changed
From-To: joe->freebsd-usb

Hand this over to the usb mailling list.

Comment 5 iedowse freebsd_committer

2005-03-23 01:53:43 UTC

State Changed
From-To: feedback->closed


Feedback timed out.