kern/95636: 5 minute delay at boot when using VT6205 based USB card reader

Tue Apr 11 21:00:37 UTC 2006

>Number:         95636
>Category:       kern
>Synopsis:       5 minute delay at boot when using VT6205 based USB card reader
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Apr 11 21:00:35 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Edwin Cini
>Release:        FreeBSD 6.0-RELEASE (AMD64)
>Organization:
>Environment:
FreeBSD wuwwu.mshome.net 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Mon Feb  6 21:12:58 CET 2006     root at wuwwu.mshome.net:/usr/obj/usr/src/sys/SMP  amd64
>Description:
When a Mitsumi 7-in-1 internal card reader is installed, the system halts for approximately 5 minutes during boot-up while attempting to detect umass devices.  Following boot-up the card reader is not operational.

The card reader is based on a VIA VT6205 Rev003 chip, and is known to work properly in other operating systems.

A discussion thread, by another person, describing the same problem related to a Mitsumi card reader is to be found on the FreeBSD-CURRENT archives of June 2005 at the following link:
http://lists.freebsd.org/pipermail/freebsd-current/2005-June/050928.html

No solution to this problem was then proposed.

Diagnostic output:
-----------------------------------------------
usbdevs -d -v -a2

Controller /dev/usb0:
Controller /dev/usb1:
Controller /dev/usb2:
Controller /dev/usb3:
addr 2: high speed, power 100 mA, config 1, USB 2.0 Card Reader(0x6205), VIA Technologies Inc.(0x040d), rev 0.03
  umass0

-----------------------------------------------
dmesg (snippet 1 - USB hardware)

ohci0: <AcerLabs M5237 (Aladdin-V) USB controller> mem 0xdffff000-0xdfffffff irq 18 at device 28.0 on pci0
ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xdffff000
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1: <AcerLabs M5237 (Aladdin-V) USB controller> mem 0xdfffe000-0xdfffefff irq 18 at device 28.1 on pci0
ohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xdfffe000
ohci1: [GIANT-LOCKED]
usb1: OHCI version 1.0, legacy support
usb1: SMM does not respond, resetting
usb1: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
ohci2: <AcerLabs M5237 (Aladdin-V) USB controller> mem 0xdfffd000-0xdfffdfff irq 18 at device 28.2 on pci0
ohci2: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xdfffd000
ohci2: [GIANT-LOCKED]
usb2: OHCI version 1.0, legacy support
usb2: SMM does not respond, resetting
usb2: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci2
usb2: USB revision 1.0
uhub2: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 3 ports with 3 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xdfffc000-0xdfffc0ff irq 23 at device 28.3 on pci0
ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xdfffc000
ehci0: [GIANT-LOCKED]
usb3: EHCI version 1.0
usb3: companion controllers, 3 ports each: usb0 usb1 usb2
usb3: <EHCI (generic) USB 2.0 controller> on ehci0
usb3: USB revision 2.0
uhub3: AcerLabs EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub3: 8 ports with 8 removable, self powered
umass0: VIA Technologies Inc. USB 2.0 Card Reader, rev 2.00/0.03, addr 2
umass0:1:0:-1: Attached to scbus1
umass1: vendor 0x04e8 USB DRIVE, rev 2.00/0.50, addr 3
umass1:2:1:-1: Attached to scbus2

-----------------------------------------------
dmesg (snippet 2 - error messages.  5:28 minutes pass between display of first line and last line shown.  Each probe7:... line pair appears after approx 1:08 minutes.)

(probe0:sbp0:0:0:0): error 22
(probe0:sbp0:0:0:0): Unretryable Error
(probe1:sbp0:0:1:0): error 22
(probe1:sbp0:0:1:0): Unretryable Error
(probe2:sbp0:0:2:0): error 22
(probe2:sbp0:0:2:0): Unretryable Error
(probe3:sbp0:0:3:0): error 22
(probe3:sbp0:0:3:0): Unretryable Error
(probe4:sbp0:0:4:0): error 22
(probe4:sbp0:0:4:0): Unretryable Error
(probe5:sbp0:0:5:0): error 22
(probe5:sbp0:0:5:0): Unretryable Error
(probe6:sbp0:0:6:0): error 22
(probe6:sbp0:0:6:0): Unretryable Error
(probe7:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
(probe7:umass-sim0:0:0:0): Retrying Command
(probe7:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
(probe7:umass-sim0:0:0:0): Retrying Command
(probe7:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
(probe7:umass-sim0:0:0:0): Retrying Command
(probe7:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
(probe7:umass-sim0:0:0:0): Retrying Command
(probe7:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
(probe7:umass-sim0:0:0:0): error 5
(probe7:umass-sim0:0:0:0): Retries Exausted

>How-To-Repeat:
Problem occurs every time during system boot.  To repeat, simply reboot with the card reader connected to the internal USB header.
>Fix:
No known fixes to date.
>Release-Note:
>Audit-Trail:
>Unformatted: