From: Timothy Pearson <tpearson@raptorengineering.com>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: Ritesh Harjani <ritesh.list@gmail.com>
Subject: [BUG] PCIe passthrough of MCS9990 fails
Date: Fri, 18 Sep 2026 13:32:51 -0500 (CDT) [thread overview]
Message-ID: <133526175.85096.1789756371777.JavaMail.zimbra@raptorengineeringinc.com> (raw)
When passing through all eight PCIe functions of a MCS9990 PCIe USB multifunction 1.0/2.0 controller on a PowerNV POWER9 host using qemu, the guest fails to launch:
qemu-system-ppc64: -device vfio-pci,host=0031:01:00.1,bus=bridge-1,addr=00.1: vfio 0031:01:00.1: Failed to set up TRIGGER eventfd signaling for interrupt INTX-0: VFIO_DEVICE_SET_IRQS failure: Device or resource busy
If I instead pass through only one function, or only pass through odd functions (the EHCI controller set), I get the following errors in the guest:
[ 0.886625] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.18
[ 0.886710] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.886791] usb usb1: Product: EHCI Host Controller
[ 0.886845] usb usb1: Manufacturer: Linux 6.18.38 ehci_hcd
[ 0.886902] usb usb1: SerialNumber: 0000:01:00.0
[ 1.142469] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 6.530490] usb 1-1: device descriptor read/64, error -110
[ 22.147501] usb 1-1: device descriptor read/64, error -110
[ 22.371536] usb 1-1: new high-speed USB device number 3 using ehci-pci
[ 27.526896] usb 1-1: device descriptor read/64, error -110
[ 43.141934] usb 1-1: device descriptor read/64, error -110
[ 43.245985] usb usb1-port1: attempt power cycle
[ 43.638173] usb 1-1: new high-speed USB device number 4 using ehci-pci
[ 54.491254] usb 1-1: device not accepting address 4, error -110
[ 54.611274] usb 1-1: new high-speed USB device number 5 using ehci-pci
If I reboot the guest, SLOF fails as follows:
Scanning USB
EHCI: Initializing
usb-ehci: reset failed
usb-ehci: control transfer timed out_
usb-ehci: unable to setup device on port 0
Note that this card works perfectly on the host kernel.
next reply other threads:[~2026-09-18 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 18:32 Timothy Pearson [this message]
2026-09-18 18:49 ` [BUG] PCIe passthrough of MCS9990 fails Timothy Pearson
2026-09-21 9:26 ` Narayana Murty N
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=133526175.85096.1789756371777.JavaMail.zimbra@raptorengineeringinc.com \
--to=tpearson@raptorengineering.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ritesh.list@gmail.com \
/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