All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 26872] New: qemu stop responding if using kvm with usb passthru
Date: Sun, 16 Jan 2011 20:38:14 GMT	[thread overview]
Message-ID: <bug-26872-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=26872

           Summary: qemu stop responding if using kvm with usb passthru
           Product: Virtualization
           Version: unspecified
    Kernel Version: 2.6.37
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
        AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
        ReportedBy: alien.virus@gmail.com
        Regression: No


qemu stop responding, if using kvm with usb passthru.
if kvm disabled qemu does not hung, but usb device 2022:0008 didn't work. 
in processes:
13304 pts/0    Dl+    0:10  |           \_ /usr/bin/qemu-system-x86_64
--enable-kvm -boot c -vnc :8 -drive
file=/raid5/image.vmdk,cache=none,if=virtio,boot=on -name image1 -uuid
564d125f-0948-a1ff-7ae3-c9acb9a25626 -cdrom /virtio-win-last.iso -fda
/virtio-win-last.vfd -enable-kvm -m 1024 -usb -smp 1 -net
vde,vlan=0,name=vmwin1,sock=/var/run/vde.sock -net
nic,vlan=0,macaddr=00:0c:29:a2:56:26,model=virtio -usbdevice tablet -vga std
-monitor telnet:0.0.0.0:4008,server,nowait -device
usb-host,vendorid=2022,productid=8 -no-kvm-irqchip -no-kvm-pit

in console
husb: open device 2.2
husb: config #1 need -1
husb: 2 interfaces claimed for configuration 1
husb: grabbed usb device 2.2
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 2 interfaces claimed for configuration 1

in messages
Jan 17 01:02:45 gentoo kernel: hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
Jan 17 01:02:45 gentoo kernel: usb 2-9: reset full speed USB device using
ohci_hcd and address 2
Jan 17 01:02:45 gentoo kernel: ohci_hcd 0000:00:02.0: GetStatus
roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
Jan 17 01:02:46 gentoo kernel: usbfs 2-9:1.0: forced unbind
Jan 17 01:02:46 gentoo kernel: usbfs 2-9:1.1: forced unbind
Jan 17 01:02:46 gentoo kernel: hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
Jan 17 01:02:46 gentoo kernel: hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
Jan 17 01:02:46 gentoo kernel: ohci_hcd 0000:00:02.0: GetStatus
roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
Jan 17 01:02:46 gentoo kernel: usb 2-9: reset full speed USB device using
ohci_hcd and address 2
Jan 17 01:02:46 gentoo kernel: ohci_hcd 0000:00:02.0: GetStatus
roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
Jan 17 01:03:06 gentoo kernel: usbfs 2-9:1.0: forced unbind
Jan 17 01:03:06 gentoo kernel: usbfs 2-9:1.1: forced unbind
Jan 17 01:03:06 gentoo kernel: hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
Jan 17 01:03:06 gentoo kernel: ohci_hcd 0000:00:02.0: GetStatus
roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
Jan 17 01:03:06 gentoo kernel: hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
Jan 17 01:03:06 gentoo kernel: usb 2-9: reset full speed USB device using
ohci_hcd and address 2
Jan 17 01:03:06 gentoo kernel: ohci_hcd 0000:00:02.0: GetStatus
roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
Jan 17 01:03:07 gentoo kernel: usbfs 2-9:1.0: forced unbind
Jan 17 01:03:07 gentoo kernel: usbfs 2-9:1.1: forced unbind
Jan 17 01:03:07 gentoo kernel: hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
Jan 17 01:03:07 gentoo kernel: hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
Jan 17 01:03:07 gentoo kernel: ohci_hcd 0000:00:02.0: GetStatus
roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
Jan 17 01:03:07 gentoo kernel: usb 2-9: reset full speed USB device using
ohci_hcd and address 2
Jan 17 01:03:07 gentoo kernel: ohci_hcd 0000:00:02.0: GetStatus
roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
Jan 17 01:03:07 gentoo kernel: ohci_hcd 0000:00:02.0: urb ffff88011f54a200 path
9 ep4in 42160000 cc 4 --> status -32
Jan 17 01:03:26 gentoo kernel: usbfs 2-9:1.0: forced unbind
Jan 17 01:03:26 gentoo kernel: usbfs 2-9:1.1: forced unbind
Jan 17 01:03:26 gentoo kernel: hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
Jan 17 01:03:26 gentoo kernel: ohci_hcd 0000:00:02.0: GetStatus
roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
Jan 17 01:03:26 gentoo kernel: hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
Jan 17 01:03:26 gentoo kernel: usb 2-9: reset full speed USB device using
ohci_hcd and address 2
Jan 17 01:03:26 gentoo kernel: ohci_hcd 0000:00:02.0: GetStatus
roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
Jan 17 01:03:27 gentoo kernel: usbfs 2-9:1.0: forced unbind
Jan 17 01:03:27 gentoo kernel: usbfs 2-9:1.1: forced unbind
Jan 17 01:03:27 gentoo kernel: hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
Jan 17 01:03:27 gentoo kernel: ohci_hcd 0000:00:02.0: GetStatus
roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
Jan 17 01:03:27 gentoo kernel: hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0200
Jan 17 01:03:27 gentoo kernel: usb 2-9: reset full speed USB device using
ohci_hcd and address 2
Jan 17 01:03:27 gentoo kernel: ohci_hcd 0000:00:02.0: GetStatus
roothub.portstatus [8] = 0x00100103 PRSC PPS PES CCS
Jan 17 01:03:32 gentoo kernel: usb 2-9: qemu-system-x86 timed out on ep0out
len=0/0
Jan 17 01:03:37 gentoo kernel: usb 2-9: qemu-system-x86 timed out on ep0out
len=0/0
Jan 17 01:03:42 gentoo kernel: usb 2-9: qemu-system-x86 timed out on ep0out
len=0/0
Jan 17 01:03:47 gentoo kernel: usb 2-9: qemu-system-x86 timed out on ep0out
len=0/0
Jan 17 01:03:52 gentoo kernel: usb 2-9: qemu-system-x86 timed out on ep0out
len=0/0
Jan 17 01:03:57 gentoo kernel: usb 2-9: qemu-system-x86 timed out on ep0out
len=0/0
Jan 17 01:04:02 gentoo kernel: usb 2-9: qemu-system-x86 timed out on ep0out
len=0/0

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2011-01-16 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16 20:38 bugzilla-daemon [this message]
2011-01-21  8:02 ` [Bug 26872] qemu stop responding if using kvm with usb passthru 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-26872-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.