Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upattaching usb device fails, usbip-host errors in sys-usb #3628
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 25, 2018
Member
Verify if you have the same kernel version in sys-usb and target VM. I think there were some major changes in USBIP (used by qvm-usb) between 4.9 and 4.14.
|
Verify if you have the same kernel version in sys-usb and target VM. I think there were some major changes in USBIP (used by qvm-usb) between 4.9 and 4.14. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
maltesl
Feb 25, 2018
I just tried this again after making sure uname -a reports both vms as running 4.14.18-1.pvops.qubes.x86_64, and the behavior is still the same. This is also the version running in dom0. I don't have any pre-4.14 kernel installed anymore (is there an easy way to install older kernels then the three oldest that are retained?), so I can't check at the moment whether the update from 4.9 to 4.14 was the one that broke things.
maltesl
commented
Feb 25, 2018
|
I just tried this again after making sure |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 25, 2018
Member
As for installing older kernels:
- Increase
installonly_limitin/etc/dnf/dnf.conf - Downgrade kernel-qubes-vm package: https://www.qubes-os.org/doc/software-update-dom0/#how-to-update-software-in-dom0
There are also some updates to USBIP in 4.15 kernel but doesn't look related to CMD_SUBMIT: isoc invalid num packets 6 error (at least not directly). So, I'd start with downgrading sys-usb kernel to 4.9.x
|
As for installing older kernels:
There are also some updates to USBIP in 4.15 kernel but doesn't look related to |
andrewdavidwong
added
bug
C: core
labels
Feb 25, 2018
andrewdavidwong
added this to the Release 4.0 milestone
Feb 25, 2018
andrewdavidwong
modified the milestones:
Release 4.0,
Release 4.0 updates
Mar 31, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
aksiazek
Apr 2, 2018
I hit the same issue with my wireless headphones and can confirm that a downgrade to 4.9 for sys-usb solved the issue for now
aksiazek
commented
Apr 2, 2018
|
I hit the same issue with my wireless headphones and can confirm that a downgrade to 4.9 for sys-usb solved the issue for now |
maltesl commentedFeb 25, 2018
Qubes OS version:
Qubes release 4.0 (R4.0)
R4.0rc4
last updated this morning (2018-02-25) from testing
Affected component(s):
qubes-usb-proxy (?)
Steps to reproduce the behavior:
Try to attach a usb device (in my case a usb soundcard/wireless headphones):
qvm-usb attach vm sys-usb:2-6Expected behavior:
The device gets attached, gets recognized by pulseaudio etc. and can be used in the target vm.
Actual behavior:
Device gets shown as attached in the widget, but not by qvm-usb.
qvm-usb shows no error message.
There is an error message in sys-usb (output of
journalctl -f):the full output is:
The messages in the target vm are:
General notes:
This worked perfectly out of the box since my first install of RC1 in September. An update a couple of weeks/months ago seems to have introduced this problem (unfortunately I don't remember anymore when it appeared precisely).
Not all usb devices seem to have this problem, this one is the only one I tried that has it.
The problem appears to be the same for both debian and fedora templates. I tried both the current kernel (4.14.18-1) as well as 4.14.13-2. Unfortunately this is is the oldest of the three kernels currently installed, so I don't know how to test older ones should the kernel be where the problem is.
Sometimes it seems possible (by repeatedly executing the
qvm-usb attachcommand until it hangs, then killing it and immediately executing another one - or something like that) to reach a state in whichqvm-usbdoes list the device as attached and it is also listed in the target vm bylsusb, but leads to pulseaudio crashing / hanging, so I am not sure whether in that case the usb device is actually usable. This does not happen often, but happened twice yesterday while I was trying to debug this.