lsusb hangs

I just confirmed that this external USB device functions properly in Windows 10.

So this is either a problem with my motherboard's USB (unlikely since the rest of my USB devices work) or some USB driver in Ubuntu

I just tried upgrading to linux-image-generic-lts-wily (4.2.0-23-generic) and the same problem exists there.

lsusb hangs and the device does not work

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1534856

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Confirmed that this bug also affects linux-image-4.4.0-040400-generic

This device did work on trusty on some older 3.X kernel so this must be an upstream regression.

Sam Shepperd, while booted into a Ubuntu kernel (not mainline/third party) please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1534856

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Attached apport log

Sam Shepperd, please don't manually attach apport logs, as it doesn't allow automatic parsing of the data. Instead, could you please run the command as previously requested?

Running apport for this kernel issue is close to useless as it only provides unrelated userland package versions.

Maybe you should worry less about having a perfect apport log and more about a lack of programming background that prevents you from contributing anything useful other than changing categories in launchpad.

Sam Shepperd, I'm not sure how being rude and attacking folks who have knowledge about the linux kernel is going to motivate anyone to want to help you, let alone fix your problem.

Despite this, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

Problem exists on 4.4 and 4.5-rc1, verified from Ubuntu Mainline builds

Sam Shepperd, to confirm the kernel regression point, could you please test successively older kernels until the issue is not reproducible following https://wiki.ubuntu.com/Kernel/KernelBisection ?

This seems to be a regression specifically with the C-Media USB Audio chipset. At least C-Media CM6632 and CM6631A are affected:
http://article.gmane.org/gmane.linux.usb.general/136685

Unfortunately I have not been able to find an older Ubuntu kernel where this works yet. But I can at least confirm the following kernels all contain the problem:

3.5.0-17.28
3.7.0-0
3.9.0-generic
3.10.0-generic
3.12.0-2-generic
3.12.0-4-generic
3.13.0-24-generic
3.13.0-30-generic
3.13.0-40-generic
3.13.0-51-generic
3.13.0-76-generic
4.2.0-25-generic
4.4
4.5-rc1
4.5-rc2

I will continue testing older kernels.

I believe that I have the same problem, however it is my mouse that (I think) causes it.
At least my mouse loses power (not mouses fault as tested by plugging into other computers/usb power outlets).
Anything I can do to help?

olza, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]