Howdy, After the usual message (on one of my machines) about "could not find the root block device [...]" which is normal on that machine due to the USB delay, the prompt appears offering to try again, name a different device or open a shell, just as with the old (3.7) kernel, but now (3.8.13), the machine is hanging, i.e., nothing goes at that point (the prompt) except a hard reset. The USB stick LED never goes on, as it used to on 3.7 after a couple of seconds. Tried kernel parameters "slowusb scandelay=<n>", but to no effect. Works fine with kernel 3.7.10 (i just wait until the LED goes on, then hit Return). 3.8.13 works fine in other installations (one native hd install, one VirtualBox, all 32-bit as the USB installation that fails), so it looks like it has something to do with me booting from USB (USB 2.0 by the way). I did not change any option in the kernel config that has anything to do with USB or hardware drivers in this regard. Maybe someone else can confirm this problem? Cheers. Reproducible: Always Steps to Reproduce: 1. Boot from USB on certain machines (...) 2. Wait for root device not found error msg + prompt 3. Try anything (machine is hanging).
Are you building this kernel with genkernel all? I suspect this is caused by bug #458606, basically starting in kernel 3.8 the EHCI driver (responsible for usb-2.0) was split out and the default genkernel config doesn't enable the CONFIG_EHCI_PCI option needed for most usb-2.0 users.
(In reply to Ben Kohler from comment #1) > Are you building this kernel with genkernel all? Yes, i am. Interesting point, i'm gonna check this out over the weekend. Thanks.
Update: CONFIG_EHCI_PCI does not exist. You mean CONFIG_USB_EHCI_PCI? Tried to enable CONFIG_USB_EHCI_PCI, but to no effect. Still the same deadlock. The CONFIG_USB_EHCI_PCI item was also disabled in the old 3.7 kernel which worked fine. So no luck there..
CONFIG_USB_EHCI_PCI was newly split out starting in kernel 3.8, so you wouldn't have had it (or needed it) enabled on 3.7. Can you try with the newly stabilized genkernel-3.4.45.1, which has this and a couple of other config issues fixed?
Please re-open if this issue still exists with genkernel-3.4.45.1
