From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: kraxel@redhat.com, sai.pavan.boddu@xilinx.com,
marcandre.lureau@redhat.com
Cc: qemu-devel@nongnu.org
Subject: nec-usb-xhci migration breakage
Date: Wed, 11 Nov 2020 17:16:22 +0000 [thread overview]
Message-ID: <20201111171622.GI3232@work-vm> (raw)
Hi,
Somewhere between 5.1.0 and 5.2.0-rc1 there's a migration breakage
on the nec-usb-xhci device:
[dgilbert@dgilbert-t580 try]$ ./x86_64-softmmu/qemu-system-x86_64 -M pc-q35-5.1 -device nec-usb-xhci -nographic -incoming tcp::4444
qemu-system-x86_64: get_pci_config_device: Bad config data: i=0x72 read: 88 device: 80 cmask: ff wmask: 71 w1cmask:0
qemu-system-x86_64: Failed to load PCIDevice:config
qemu-system-x86_64: Failed to load xhci:parent_obj
qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:03.0/xhci'
qemu-system-x86_64: load of migration failed: Invalid argument
lspci is showing the MSI count ifferent, but I'm not sure if that's the
only problem or not:
5.1.0 showing:
[root@localhost ~]# lspci -v -s 00:03.0 -v
00:03.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) (prog-if 30 [XHCI])
Subsystem: Red Hat, Inc. QEMU Virtual Machine
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 23
Region 0: Memory at febd4000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [90] MSI-X: Enable+ Count=16 Masked-
Vector table: BAR=0 offset=00003000
PBA: BAR=0 offset=00003800
Capabilities: [a0] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
AtomicOpsCtl: ReqEn-
Capabilities: [70] MSI: Enable- Count=1/16 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Kernel driver in use: xhci_hcd
5.2.0rc1 showing
[root@localhost ~]# lspci -v -s 00:03.0 -v
00:03.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) (prog-if 30 [XHCI])
Subsystem: Red Hat, Inc. QEMU Virtual Machine
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 23
Region 0: Memory at febd4000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [90] MSI-X: Enable+ Count=1 Masked-
Vector table: BAR=0 offset=00003000
PBA: BAR=0 offset=00003800
Capabilities: [a0] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
AtomicOpsCtl: ReqEn-
Capabilities: [70] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Kernel driver in use: xhci_hcd
I see there's quite a few differences in the output of info qtree for
the device.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next reply other threads:[~2020-11-11 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 17:16 Dr. David Alan Gilbert [this message]
2020-11-16 5:18 ` nec-usb-xhci migration breakage Sai Pavan Boddu
2020-11-16 7:03 ` kraxel
2020-11-16 7:27 ` Sai Pavan Boddu
2020-11-16 7:55 ` Sai Pavan Boddu
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=20201111171622.GI3232@work-vm \
--to=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sai.pavan.boddu@xilinx.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;
as well as URLs for NNTP newsgroup(s).