qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] xhci migration breakage


From: Gerd Hoffmann
Subject: Re: [Qemu-devel] xhci migration breakage
Date: Fri, 31 Mar 2017 07:45:33 +0200

  Hi,

> dest:
> (qemu) red_dispatcher_loadvm_commands: 
> usb-storage msd post_load 0x7f45f510ee50 sig=0 tag=0
> 
> I added these as debug on the 'usb-storage' vmsd element; but
> the signature/tag being 0 I assume they're not the culprit.

Yep, no inflight transfer, so highly unlikely (also note that ehci works
fine according to bugzilla).

> #6  0x00007febabacae27 in xhci_kick_epctx (epctx=<optimized out>, 
> xfer=<optimized out>, xhci=<optimized out>)
>     at /root/1436616/qemu/hw/usb/hcd-xhci.c:2103 <- right at the end of 
> xhci_submit
> #7  0x00007febabacae27 in xhci_kick_epctx (epctx=<optimized out>, 
> xfer=<optimized out>, xhci=<optimized out>)
>     at /root/1436616/qemu/hw/usb/hcd-xhci.c:2112 right at end of 
> xhci_fire_transfer
> #8  0x00007febabacae27 in xhci_kick_epctx (epctx=0x7febaec395a0, streamid=0)
>     at /root/1436616/qemu/hw/usb/hcd-xhci.c:2240

Recursive xhci_kick_epctx calls, not good.

Does the attached patch (not tested yet) make any difference?

cheers,
  Gerd

Attachment: 0001-xhci-set-kick_active-for-retried-xfers-too.patch
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]