From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218876] New: PCIE device crash when trying to pass through USB Device to virtual machine
Date: Wed, 22 May 2024 19:31:45 +0000 [thread overview]
Message-ID: <bug-218876-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218876
Bug ID: 218876
Summary: PCIE device crash when trying to pass through USB
Device to virtual machine
Product: Virtualization
Version: unspecified
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: dan@danalderman.co.uk
Regression: No
Hi.
I'm running a Debian Bookworm host with Xanmod 6.9.1 kernel
This motherboard:
https://www.supermicro.com/en/products/motherboard/a2sdi-16c-tp8f
With this USB controller in the 4x PCIe slot.
https://www.startech.com/en-gb/cards-adapters/pexusb3s2ei
The USB card is based on the Renesas uPD720201 USB 3.0 Host Controller and
reports the latest firmware.
I have a Debian Bookworm VM running on this host, which I intend to pass the
entire PCIe card through to (Gnome+Plexamp->USB-SPDIF). If I configure the VM
to do this the VM fails to start and I get the following errors from the
kernel. The card then becomes seemingly unrecoverable without a warm reboot at
least.
I have tried many kernel and BIOS options regarding PCIe but nothing has helped
so far. I'll attach a boot log. This is the error when I start the VM:
May 19 09:24:46 kryten kernel: VFIO - User Level meta-driver version: 0.3
May 19 09:24:46 kryten kernel: xhci_hcd 0000:02:00.0: remove, state 1
May 19 09:24:46 kryten kernel: usb usb4: USB disconnect, device number 1
May 19 09:24:46 kryten kernel: xhci_hcd 0000:02:00.0: USB bus 4 deregistered
May 19 09:24:46 kryten kernel: xhci_hcd 0000:02:00.0: remove, state 1
May 19 09:24:46 kryten kernel: usb usb3: USB disconnect, device number 1
May 19 09:24:46 kryten kernel: usb 3-4: USB disconnect, device number 2
May 19 09:24:46 kryten kernel: xhci_hcd 0000:02:00.0: USB bus 3 deregistered
May 19 09:24:47 kryten kernel: usb 1-1.2: USB disconnect, device number 4
May 19 09:24:53 kryten kernel: pcieport 0000:00:09.0: broken device, retraining
non-functional downstream link at 2.5GT/s
May 19 09:24:54 kryten kernel: pcieport 0000:00:09.0: retraining failed
May 19 09:24:55 kryten kernel: pcieport 0000:00:09.0: broken device, retraining
non-functional downstream link at 2.5GT/s
May 19 09:24:56 kryten kernel: pcieport 0000:00:09.0: retraining failed
May 19 09:24:56 kryten kernel: vfio-pci 0000:02:00.0: not ready 1023ms after
bus reset; waiting
May 19 09:24:57 kryten kernel: vfio-pci 0000:02:00.0: not ready 2047ms after
bus reset; waiting
May 19 09:24:59 kryten kernel: vfio-pci 0000:02:00.0: not ready 4095ms after
bus reset; waiting
May 19 09:25:04 kryten kernel: vfio-pci 0000:02:00.0: not ready 8191ms after
bus reset; waiting
May 19 09:25:12 kryten kernel: vfio-pci 0000:02:00.0: not ready 16383ms after
bus reset; waiting
May 19 09:25:29 kryten kernel: vfio-pci 0000:02:00.0: not ready 32767ms after
bus reset; waiting
May 19 09:26:05 kryten kernel: pcieport 0000:00:09.0: broken device, retraining
non-functional downstream link at 2.5GT/s
May 19 09:26:06 kryten kernel: pcieport 0000:00:09.0: retraining failed
May 19 09:26:08 kryten kernel: pcieport 0000:00:09.0: broken device, retraining
non-functional downstream link at 2.5GT/s
May 19 09:26:09 kryten kernel: pcieport 0000:00:09.0: retraining failed
May 19 09:26:09 kryten kernel: vfio-pci 0000:02:00.0: not ready 1023ms after
bus reset; waiting
May 19 09:26:10 kryten kernel: vfio-pci 0000:02:00.0: not ready 2047ms after
bus reset; waiting
May 19 09:26:12 kryten kernel: vfio-pci 0000:02:00.0: not ready 4095ms after
bus reset; waiting
May 19 09:26:16 kryten kernel: vfio-pci 0000:02:00.0: not ready 8191ms after
bus reset; waiting
May 19 09:26:25 kryten kernel: vfio-pci 0000:02:00.0: not ready 16383ms after
bus reset; waiting
May 19 09:26:43 kryten kernel: vfio-pci 0000:02:00.0: not ready 32767ms after
bus reset; waiting
May 19 09:27:18 kryten kernel: vfio-pci 0000:02:00.0: Unable to change power
state from D0 to D3hot, device inaccessible
May 19 09:27:19 kryten kernel: vfio-pci 0000:02:00.0: Unable to change power
state from D3cold to D0, device inaccessible
May 19 09:27:19 kryten kernel: vfio-pci 0000:02:00.0: Unable to change power
state from D3cold to D0, device inaccessible
May 19 09:27:19 kryten kernel: vfio-pci 0000:02:00.0: Unable to change power
state from D3cold to D0, device inaccessible
May 19 09:27:19 kryten kernel: vfio-pci 0000:02:00.0: Unable to change power
state from D3cold to D0, device inaccessible
May 19 09:27:19 kryten kernel: vfio-pci 0000:02:00.0: Unable to change power
state from D3cold to D0, device inaccessible
May 19 09:27:19 kryten kernel: xhci_hcd 0000:02:00.0: Invalid ROM..
May 19 09:27:19 kryten kernel: xhci_hcd 0000:02:00.0: Unable to change power
state from D3cold to D0, device inaccessible
May 19 09:27:19 kryten kernel: xhci_hcd 0000:02:00.0: xHCI Host Controller
May 19 09:27:19 kryten kernel: xhci_hcd 0000:02:00.0: new USB bus registered,
assigned bus number 3
May 19 09:27:19 kryten kernel: xhci_hcd 0000:02:00.0: Host halt failed, -19
May 19 09:27:19 kryten kernel: xhci_hcd 0000:02:00.0: can't setup: -19
May 19 09:27:19 kryten kernel: xhci_hcd 0000:02:00.0: USB bus 3 deregistered
May 19 09:27:19 kryten kernel: xhci_hcd 0000:02:00.0: init 0000:02:00.0 fail,
-19
Thanks for your time and help.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-05-22 19:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 19:31 bugzilla-daemon [this message]
2024-05-22 19:32 ` [Bug 218876] PCIE device crash when trying to pass through USB Device to virtual machine bugzilla-daemon
2024-05-22 19:34 ` [Bug 218876] PCIE device crash when trying to pass through USB PCIe Card " bugzilla-daemon
2024-05-22 20:38 ` bugzilla-daemon
2024-05-23 14:35 ` bugzilla-daemon
2024-05-23 15:28 ` bugzilla-daemon
2024-05-23 15:28 ` bugzilla-daemon
2024-05-24 11:19 ` bugzilla-daemon
2024-05-25 13:49 ` bugzilla-daemon
2024-05-25 14:16 ` bugzilla-daemon
2024-05-25 14:20 ` bugzilla-daemon
2024-05-28 21:16 ` bugzilla-daemon
2024-05-29 10:42 ` bugzilla-daemon
2024-05-29 11:35 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-218876-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).