Bug 130208 - Boot process severely hampered by umass0 error
Summary: Boot process severely hampered by umass0 error
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: 7.1-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-usb (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-05 22:00 UTC by Russell Sutherland
Modified: 2018-01-03 05:16 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Russell Sutherland 2009-01-05 22:00:11 UTC
The boot process waits for several minutes due to a umass error:

umass0: <vendor 0x55aa 8-in-2, class 0/0, rev 1.10/1.01, addr 2> on uhub0
umass0: Get Max Lun not supported (IOERROR)
Waiting 5 seconds for SCSI devices to settle
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
umass0: BBB reset failed, IOERROR
umass0: BBB bulk-in clear stall failed, IOERROR
umass0: BBB bulk-out clear stall failed, IOERROR
run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
umass0: BBB reset failed, IOERROR
umass0: BBB bulk-in clear stall failed, IOERROR
umass0: BBB bulk-out clear stall failed, IOERROR
run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
umass0: BBB reset failed, IOERROR
umass0: BBB bulk-in clear stall failed, IOERROR
umass0: BBB bulk-out clear stall failed, IOERROR
run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config
umass0: BBB reset failed, IOERROR
umass0: BBB bulk-in clear stall failed, IOERROR
umass0: BBB bulk-out clear stall failed, IOERROR
run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config
umass0: BBB reset failed, IOERROR
umass0: BBB bulk-in clear stall failed, IOERROR
umass0: BBB bulk-out clear stall failed, IOERROR

sa0 at ahc0 bus 0 target 6 lun 0
sa0: <CERTANCE ULTRIUM 2 1914> Removable Sequential Access SCSI-3 device 
sa0: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ad0s1a

This problem did not seem to exist with FreeBSD 7.0

Fix: 

No idea.
How-To-Repeat: Reboot
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:31 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped