Created attachment 935510 [details] grepped dmesg output On nearly every boot, I get the following error messages popping up: [ 2.491690] usb 2-7: new full-speed USB device number 6 using xhci_hcd [ 4.758611] usb 2-7: unable to read config index 0 descriptor/start: -71 [ 4.758621] usb 2-7: can't read configurations, error -71 (... up to:) [ 60.974914] usb 2-7: new full-speed USB device number 43 using xhci_hcd [ 63.090612] usb 2-7: unable to read config index 0 descriptor/start: -71 [ 63.090617] usb 2-7: can't read configurations, error -71 then, it finally seems to work: [ 63.240793] usb 2-7: new full-speed USB device number 44 using xhci_hcd [ 63.253022] usb 2-7: New USB device found, idVendor=04f3, idProduct=016f [ 63.253025] usb 2-7: New USB device strings: Mfr=4, Product=14, SerialNumber=0 [ 63.253026] usb 2-7: Product: Touchscreen [ 63.253028] usb 2-7: Manufacturer: ELAN [ 63.253247] usb 2-7: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes [ 63.260815] input: ELAN Touchscreen as /devices/pci0000:00/0000:00:14.0/usb2/2-7/2-7:1.0/0003:04F3:016F.0007/input/input20 These repeat a few times, incrementing the "discovered device number" by 1, always take about 1-2 seconds, and so the boot is delayed unnecessarily by about 40 seconds. The device connected to the problem seems to be an ELAN touchscreen on usb port 2-7 (?). Version-Release number of selected component (if applicable): kernel-3.16.2-300.fc21.x86_64 How reproducible: Cold boot or reboot. Steps to Reproduce: 1. Boot fedora 2. Watch for error messages 3. See the boot being delayed because the device is not ready Actual results: Boot takes ~40 seconds longer than it needs to on a core i7 and SSD. Expected results: Additional info: output of "dmesg | grep usb | grep 2-7" attached.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs. Fedora 21 has now been rebased to 3.18.3-201.fc21. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.