This isn't a bug. That error is spawned by the hardware and defined in the USB specs. The kernel only catches it and report it to user land as specs say it should happen.
This isn't a bug. That error is spawned by the hardware and defined in the USB specs. The kernel only catches it and report it to user land as specs say it should happen.