Comment 19 for bug 1794922

Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

So you have EHCI enabled on the virtual machines? Without it, they're not testing similar conditions

Based on an earlier comment I should point out that if you look at those kernel messages and ignore the timestamp (equivalent of `dmesg --notime`), you note they all start with "ehci-pci," which is a reference to the kernel driver for the 2.0 version of USB:
https://github.com/torvalds/linux/blob/master/drivers/usb/host/ehci-pci.c

By default EHCI is not enabled in VirtualBox, even with the extension pack that is required to support it installed. Given that the problem seems to be related to EHCI, this will need to be selected first.

With that in place, if there is no fail, it also may be related to the specific USB device you have. You should plug it in ("add a filter" in VB parlance) to the virtual machine.

If that still fails to fail, you might want to try to boot from the USB but that's a little trickier:
https://askubuntu.com/questions/693719/how-to-boot-from-a-usb-drive-in-virtualbox

I'll note that bug I mentioned before seems to point at this as the fix:
https://lkml.org/lkml/2018/10/14/62

I still suspect the kernel as it seems that the test you did to confirm it's not the kernel you performed on a 64 bit kernel. The symptoms seem to suggest 32 bit, as does that patch.