Windows 10 hang at boot with ir receiver plugged into dedicated usb port


Recommended Posts

I have a Windows 10 VM that's working decently after some troubleshooting (needed to enable MSI mode on nvidia graphics/sound, else it could bring entire unraid server down when the VM was powered off/rebooted). I have an issue that I've worked around, but it still bugs me (you know how it is).

 

I bought a Sonnet Allegro Pro USB 3.0 PCIe card with four dedicated controllers (one controller per usb port). One is passed through to the Windows 10 VM. I have a cheap four port hub plugged in so anything I plug into the hub is connected directly to the VM. Needed it this way so I could use a usb amp (when it's turned off it's not visible to the OS, i.e. unplugged). Anyway....

 

The Windows 10 VM hangs at the bios screen (where it shows it passed the memory check) if the IR receiver is plugged in. Doesn't matter if the IR receiver is plugged into the usb hub, or plugged directly into the dedicated usb port. Just hangs there. I can unplug, boot, then plug the receiver in, works fine until I reboot. It doesn't have an issue with the other usb devices (currently a Logitech unifying usb adapter and an SMSL amp).

 

Simple workaround, I have the IR receiver plugged into one of the shared usb ports and assigned it to the Windows 10 VM. Works fine, but it still bugs me, you know?

 

IR receiver info:

TopSeed Technology Corp. eHome Infrared Transceiver (1784:0006)

 

Dedicated usb controller info:

Fresco Logic FL1100 USB 3.0 Host Controller | USB controller (09:00.0)

 

Syslog when booting with the IR receiver plugged into the hub (VM hangs):

Oct 11 19:12:36 Tower kernel: vgaarb: device changed decodes: PCI:0000:04:00.0,olddecodes=io+mem,decodes=io+mem:owns=none
Oct 11 19:12:36 Tower kernel: br0: port 3(vnet1) entered blocking state
Oct 11 19:12:36 Tower kernel: br0: port 3(vnet1) entered disabled state
Oct 11 19:12:36 Tower kernel: device vnet1 entered promiscuous mode
Oct 11 19:12:36 Tower kernel: br0: port 3(vnet1) entered blocking state
Oct 11 19:12:36 Tower kernel: br0: port 3(vnet1) entered forwarding state
Oct 11 19:12:38 Tower kernel: vfio_ecap_init: 0000:04:00.0 hiding ecap 0x19@0x900
Oct 11 19:12:38 Tower kernel: vfio-pci 0000:09:00.0: enabling device (0400 -> 0402)

 

Syslog when booting without  the IR receiver plugged in (VM boots, can plug in once Windows boot screen displays):

Oct 11 19:13:34 Tower kernel: vgaarb: device changed decodes: PCI:0000:04:00.0,olddecodes=io+mem,decodes=io+mem:owns=none
Oct 11 19:13:34 Tower kernel: br0: port 3(vnet1) entered blocking state
Oct 11 19:13:34 Tower kernel: br0: port 3(vnet1) entered disabled state
Oct 11 19:13:34 Tower kernel: device vnet1 entered promiscuous mode
Oct 11 19:13:34 Tower kernel: br0: port 3(vnet1) entered blocking state
Oct 11 19:13:34 Tower kernel: br0: port 3(vnet1) entered forwarding state
Oct 11 19:13:36 Tower kernel: vfio_ecap_init: 0000:04:00.0 hiding ecap 0x19@0x900
Oct 11 19:13:36 Tower kernel: vfio-pci 0000:09:00.0: enabling device (0400 -> 0402)
Oct 11 19:13:47 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound
Oct 11 19:13:47 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound

 

I don't see anything useful. If there's any additional information you'd like, just let me know.

 

Edit: In case it helps, here's a syslog of the Windows 10 VM successfully booting with the current setup (dedicated usb port passed through, plus the IR receiver passed through separately):

Oct 11 19:38:16 Tower kernel: vgaarb: device changed decodes: PCI:0000:04:00.0,olddecodes=io+mem,decodes=io+mem:owns=none
Oct 11 19:38:16 Tower kernel: br0: port 3(vnet1) entered blocking state
Oct 11 19:38:16 Tower kernel: br0: port 3(vnet1) entered disabled state
Oct 11 19:38:16 Tower kernel: device vnet1 entered promiscuous mode
Oct 11 19:38:16 Tower kernel: br0: port 3(vnet1) entered blocking state
Oct 11 19:38:16 Tower kernel: br0: port 3(vnet1) entered forwarding state
Oct 11 19:38:18 Tower kernel: vfio_ecap_init: 0000:04:00.0 hiding ecap 0x19@0x900
Oct 11 19:38:18 Tower kernel: vfio-pci 0000:09:00.0: enabling device (0400 -> 0402)
Oct 11 19:38:20 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:20 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:26 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:27 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:27 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:30 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound
Oct 11 19:38:30 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound
Oct 11 19:38:31 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:31 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:32 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:32 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:35 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:36 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:36 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:37 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:37 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci
Oct 11 19:38:37 Tower kernel: usb 1-1.6: reset full-speed USB device number 4 using ehci-pci

 

Edited by josetann
Post wasn't boring enough.
Link to comment
  • 3 months later...

Hi Josetann,  Did you ever figure this one out beyond your work-around?  I just added a similar multi chip USB card (High Point RocketU 1144C ) to my system and am fighting with the same issue.  I have an IR receiver as well as a couple other USB devices (webcams/vid capture devices) that just hang the VM at the BIOS/boot screen.  Did you try both OVMF and SeaBIOS by chance?  I haven't done a ton of troubleshooting myself yet so thought I'd see if anyone has solved this before pulling any hair out...  First step is trying to find an error message or something, but like your logs mine don't state anything obvious to look at that I can see.

 

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.