Bug ID: 220127
           Summary: USB devices sometimes(!) not seen at boot time
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: usb

This is on CURRENT (r314251, amd64) on an Acer C720 Chromebook. I have two USB
devices (small sticks designed to hold a GnuPG CCID cards, see
)which both show the following problem:

steps to reproduce
1. power-off the system
2. insert the USB device (the stick) into any USB port of the machine
3. power-on and let the system boot

Sometimes (statistically in two of three boots) the USB device is not seen by
the kernel, i.e. it takes 2-3 reboots to get it seen.

When the device was seen during boot, one can withdraw it and re-attach it
again. It is always seen again and works fine with the pcscd, the card daemon
from ports.

When the device was NOT seen during boot, it does not help to re-attach. It is
never seen by the kernel. Only re-boot helps.

When the device is seen, it shows the following lines during boot:


ugen0.2: <HID Global OMNIKEY 6121 Smart Card Reader> at usbus0, cfg=0 md=HOST
spd=FULL (12Mbps) pwr=ON (100mA)

ugen0.2: <Identiv uTrust 3512 SAM slot Token> at usbus0

The latter shows, when it was seen on boot, the following usbconfig output:

# usbconfig dump_device_desc

ugen0.2: <Identiv uTrust 3512 SAM slot Token> at usbus0, cfg=0 md=HOST spd=FULL
(12Mbps) pwr=ON (76mA)

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0008 
  idVendor = 0x04e6 
  idProduct = 0x5816 
  bcdDevice = 0x0202 
  iManufacturer = 0x0001  <Identiv>
  iProduct = 0x0002  <uTrust 3512 SAM slot Token>
  iSerialNumber = 0x0005  <55511514602745>
  bNumConfigurations = 0x0001 

There is another issue, maybe related to this one here which should be closed
in favor of this new one or resolved later, when this one here is solved.

You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________ mailing list
To unsubscribe, send any mail to ""

Reply via email to