Subnostr

Looks like it could be something the kernel is doing, either in sys-usb, or the qube that the device is being attached to.

I saw issue 3628 that was kernel bugs/incompatibilities related to USBIP.

That issue isn't what I'm facing, but I am seeing some weird stuff in the syslogs...

nostr:nevent1qqstne97kt56fprsslxana9w93l5xf6ylyy95ph26net0rwyg7r56ugpzemhxue69uhkummnw3ezumn0dahx2uewvdhk6q3q6v82nr4xt62nlydtj0mtxr49r6enc5r0sl2f7cq2zwdw7q92j5gsxpqqqqqqzx22phn

Dr. Hax 1y ago

dmesg in qube show: unlink->seqnum and urb->status -104

In journalctl in sys-usb: unlinked by a call to usb_unlink_urb()

I see selinux is enabled in sys-usb, which adds another possible layer that might be messing around with things...

nostr:nevent1qqszsxeeeevvhr2wgxfxt5lvyg2lnyy9c3kw3sz0487tpyzc5khzq5spp4mhxue69uhkummn9ekx7mqzyrfsa2vw5e0f20u34wfldvcw550tx0zsd7raf8mqpgfe4mcq4223zqcyqqqqqqgc0luas

Reply to this note

Please Login to reply.

Discussion

Dr. Hax 1y ago

This problem just keeps getting weirder. I'm now thinking of it as a "computer problem" because I'm seeing this weird behavior in Tails and with a PCIe USB controller.

https://forum.qubes-os.org/t/usbip-protocol-errors/24236/4

So maybe Qubes 4.2 was fine all along...

nostr:nevent1qqsd32r0zvpxfnls7k7msntamcvu90eerepm5tjzdcsgwha4lpuv63cpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqzyrfsa2vw5e0f20u34wfldvcw550tx0zsd7raf8mqpgfe4mcq4223zqcyqqqqqqgvvuqmd