Created attachment 1062320 [details] dmesg output exhibiting the problem Description of problem: After upgrading to kernel version 4.1.4-200.fc22.x86_64, an external USB 3.0 hard drive is not detected. The same hard drive works with the previous kernel version, 4.1.3-201.fc22.x86_64. Version-Release number of selected component (if applicable): 4.1.4-200.fc22.x86_64 How reproducible: Problem persists after powering down and restarting the machine, and with every port in the system. Additional info: Please see end of attached dmesg.log.problem for relevant output. Compare with the corresponding output in dmesg.log.noproblem (search for "LaCie") with the older kernel version.
Created attachment 1062321 [details] dmesg log with older kernel version, showing no problem
(Broken functionality, first=4.1.4)
Somehow that got submitted unintentionally. It looks like in the broken case, the drive is detected twice for some reason 9as two different USB devices) but it never gets to the point of reading the partition table. It might be useful to have lsusb -v output for both cases if possible.
It is detected twice because I plugged it into a different USB port when it didn't work the first time, to rule out hardware issues. I'm attaching a new dmesg log that only has one detection. I'm also attaching the output of lsusb, even though the drive doesn't show up there.
Created attachment 1062833 [details] dmesg output exhibiting the problem
Created attachment 1062834 [details] output of lsusb (doesn't include device)
Created attachment 1063207 [details] output of lsusb (including device, with older kernel)
I think I can confirm this bug I have F22 x86_64 installed on HD in a USB3 box, as rescue tool. After update from kernel 4.1.3-201 to 4.14-200 it can not boot anymore. Grub menu comes up, select the newest kernel, after a long while(without USB activity) it drops out to the dracut menu reporting that it can not access storage. Happens on 2 different type HW, a Intel I7 based laptop and AMD Phenom II based desktop. Selecting the previous kernel or the rescue kernel it boot normal. Just for info, boot it in a VirtualBox 5 (USB 3) guest box, works fine. Knud
Kernel 4.1.5-200.fc22.x86_64 has the problem also
Kernel 4.1.6-200 still has the bug.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug is still present in Fedora 30 with kernel 5.2.9-300.