© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
(In reply to comment #35)
> Well at least we have a status report. It would be nice if even if nothing
> was happening on a bug because of this backlog that we get a comment from
> someone to this effect every six months or so.
>
> Is there anything we can be doing to help track down this bug?
Yes, actually.
Likely one of the most helpful things you can do is email the upstream linux-usb mailing list and report the issue to them. They are the domain experts and having them directly in contact with the people having the issue eliminates the middle-man.
Things to note in the email would be:
- USB controller/chipset
- What kind of devices present this error (usb id)
- Which kernel(s) exhibit the problem
Given that this bug seems to have been around for a really long time, that last question might be a bit difficult to answer.
If anyone gets responses from upstream, we can help build test kernels and patches if needs be. Just put a URL to the mailing list archive there in this bug.