From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 77871] New: USB device passthrough to Virtual GUEST system from Linux
Date: Sat, 14 Jun 2014 07:24:59 +0000 [thread overview]
Message-ID: <bug-77871-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=77871
Bug ID: 77871
Summary: USB device passthrough to Virtual GUEST system from
Linux
Product: Virtualization
Version: unspecified
Kernel Version: 3.14.6 or 3.14.7
Hardware: All
OS: Linux
Tree: Fedora
Status: NEW
Severity: high
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: ertanerbek@gmail.com
Regression: No
Created attachment 139701
--> https://bugzilla.kernel.org/attachment.cgi?id=139701&action=edit
Full log file.
After kernel 3.14.6 and 3.14.7 upgrade at Fedora when I try passthrough any USB
device to Virtual GUEST then kerel create log some time after rsyslog demon top
collect log due rate limit. I try that problem with Qemu KVM and Virtualbox.
Also I add full log file to this ticket.
I get that log from Fedora 20 when I use Virtualbox but also KVM have same
problem.
---------------------------------######-------------------------
Jun 13 10:44:58 homless kernel: WARNING: CPU: 0 PID: 15753 at
drivers/usb/core/urb.c:476 usb_submit_urb+0x28d/0x5c0()
Jun 13 10:44:58 homless kernel: usb 3-2.2: BOGUS urb flags, 1 --> 0
Jun 13 10:44:58 homless kernel: Modules linked in: ax88179_178a usbnet
rt2800usb rt2x00usb rt2800lib rt2x00lib crc_ccitt rtl8187 eeprom_93cx6 nls_utf8
udf crc_itu_t usb_storage fuse ccm nf_conntrack_tftp nf_conntrack_netbios_ns
nf_conntrack_broadcast ip6t_rpfilter bnep bluetooth 6lowpan_iphc ip6t_REJECT
xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables
ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle
ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle
vboxpci(OF) vboxnetadp(OF) iptable_security vboxnetflt(OF) iptable_raw
vboxdrv(OF) bbswitch(OF) iTCO_wdt rtsx_pci_sdmmc iTCO_vendor_support
rtsx_pci_ms mmc_core memstick arc4 uvcvideo videobuf2_vmalloc videobuf2_memops
Jun 13 10:44:58 homless kernel: videobuf2_core videodev media
snd_hda_codec_hdmi snd_hda_codec_via snd_hda_codec_generic x86_pkg_temp_thermal
snd_hda_intel coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel
ath9k ghash_clmulni_intel ath9k_common snd_hda_codec snd_hwdep ath9k_hw snd_seq
snd_seq_device ath snd_pcm mac80211 microcode joydev serio_raw cfg80211 r8169
rtsx_pci mii snd_timer lpc_ich snd mfd_core rfkill i2c_i801 soundcore mei_me
shpchp mei tpm_infineon tpm_tis tpm acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd
binfmt_misc sunrpc mxm_wmi i915 i2c_algo_bit drm_kms_helper drm i2c_core video
wmi [last unloaded: nvidia]
Jun 13 10:44:58 homless kernel: CPU: 0 PID: 15753 Comm: EMT-1 Tainted: PF
W O 3.14.7-200.fc20.x86_64 #1
Jun 13 10:44:58 homless kernel: Hardware name: CLEVO CO.
W110ER /W110ER , BIOS 1.02.11
PM v3 07/01/20
Jun 13 10:44:58 homless kernel: 0000000000000000 00000000bf4461af
ffff8802a0239ca8 ffffffff816f04b2
Jun 13 10:44:58 homless kernel: ffff8802a0239cf0 ffff8802a0239ce0
ffffffff8108a1cd ffff8802e99e79c0
Jun 13 10:44:58 homless kernel: ffff88036a43e800 0000000000000002
0000000000000001 0000000000000020
Jun 13 10:44:58 homless kernel: Call Trace:
Jun 13 10:44:58 homless kernel: [<ffffffff816f04b2>] dump_stack+0x45/0x56
Jun 13 10:44:58 homless kernel: [<ffffffff8108a1cd>]
warn_slowpath_common+0x7d/0xa0
Jun 13 10:44:58 homless kernel: [<ffffffff8108a24c>]
warn_slowpath_fmt+0x5c/0x80
Jun 13 10:44:58 homless kernel: [<ffffffff814e4d4d>] usb_submit_urb+0x28d/0x5c0
Jun 13 10:44:58 homless kernel: [<ffffffff814f0e0d>]
proc_do_submiturb+0xc6d/0xcc0
Jun 13 10:44:58 homless kernel: [<ffffffff811cc265>] ? __kmalloc+0x55/0x240
Jun 13 10:44:58 homless kernel: [<ffffffffa10ace8d>] ?
rtR0MemAllocEx+0x19d/0x280 [vboxdrv]
Jun 13 10:44:58 homless kernel: [<ffffffff814f130f>]
usbdev_do_ioctl+0x4af/0x1080
Jun 13 10:44:58 homless kernel: [<ffffffffa10acfca>] ? rtR0MemFree+0x5a/0x70
[vboxdrv]
Jun 13 10:44:58 homless kernel: [<ffffffff814f1f0e>] usbdev_ioctl+0xe/0x20
Jun 13 10:44:58 homless kernel: [<ffffffff811fd0f0>] do_vfs_ioctl+0x2e0/0x4a0
Jun 13 10:44:58 homless kernel: [<ffffffff811fd331>] SyS_ioctl+0x81/0xa0
Jun 13 10:44:58 homless kernel: [<ffffffff81121eb6>] ?
__audit_syscall_exit+0x1f6/0x2a0
Jun 13 10:44:58 homless kernel: [<ffffffff81700869>]
system_call_fastpath+0x16/0x1b
Jun 13 10:44:58 homless kernel: ---[ end trace 0fe71e2b17d4081e ]---
Jun 13 10:44:58 homless kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for slot
4 ep 2 with no TDs queued?
Jun 13 10:44:58 homless kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for slot
4 ep 2 with no TDs queued?
Jun 13 10:44:58 homless kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for slot
4 ep 2 with no TDs queued?
Jun 13 10:44:58 homless kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for slot
4 ep 2 with no TDs queued?
Jun 13 10:44:58 homless kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for slot
4 ep 2 with no TDs queued?
Jun 13 10:44:58 homless kernel: ------------[ cut here ]------------
---------------------------------######-------------------------
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2014-06-14 7:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-77871-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.