046d:082d Logitech c920 usb webcam not working when plugged into USB 3.0 port

[truthy]

My logitech c920 usb webcam doesn't work when connected to my usb 3.0 host controller (Etron EJ168a). When i connect my usb 3.0 stick to the same port it's recognized and also works - just not the webcam. disabling usb 3.0 legacy mode (xhci) in my bios doesn't change anything, it's still used instead of ehci.

Upstream URL http://www.spinics.net/lists/linux-usb/msg107696.html .

dmesg | grep usb
usb 3-1: Not enough bandwidth for altsetting 3
3:3:3: usb_set_interface failed (-22)

dmesg | grep xhci
xhci_hcd 0000:06:00.0: ERROR: unexpected command completion code 0x11.

WORKAROUND: When connected to a usb 2.0 port it works perfectly.

---
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: truthy 1586 F.... pulseaudio
 /dev/snd/controlC2: truthy 1586 F.... pulseaudio
 /dev/snd/pcmC2D0p: truthy 1586 F...m pulseaudio
 /dev/snd/controlC0: truthy 1586 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=646b5559-d036-471d-9f6e-29068cf6172b
InstallationDate: Installed on 2012-11-29 (531 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: wl nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=5adf789b-4753-49d0-bae6-91dae8cc3701 ro splash
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127.2
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-05-09 (5 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/29/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.30
dmi.board.name: Z68 Pro3 Gen3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd06/29/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Pro3Gen3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1319443/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[truthy (martin-rudhart)]

yeah well, that's the problem. I don't think the problem is about a specific source package as xhci is no longer a module but integrated into the kernel ... so I guess it fits the project linux-kernel-headers. that may also mean that the bug should have been reported here: https://bugzilla.kernel.org/, right?

[Brad Figg (brad-figg)]

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

apport-collect 1319443

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.

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[truthy (martin-rudhart)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.15-rc5-utopic/

[truthy (martin-rudhart)]

had to change to nouveau for the kernel to install and my wireless card didn't work (bwcml), but still no change. not working in mainline kernel Linux 3.15.0-031500rc5-generic.

dmesg | grep usb shows multiple instances of
usb 2-1.2: cannot submit urb 0, error -28: not enough bandwidth

dmesg | grep xhci
shows nothing

[truthy (martin-rudhart)]

I've already contacted the appropriate mailing-list (Linux USB) with reference to this bugreport and received a response. If there'r any more logfiles I should upload, please let me know.

[penalvch (penalvch)]

truthy, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc6-utopic/ and advise to the results?

If reproducible, you would want to respond to upstream's request as per http://www.spinics.net/lists/linux-usb/msg107698.html .

[truthy (martin-rudhart)]

penalvch, thx for your reply. tested with 3.15.0-031500rc6-generic amd64. problem persists.

Response:
http://www.spinics.net/lists/linux-usb/msg108362.html
http://marc.info/?l=linux-usb&m=140110305107599&w=2

[penalvch (penalvch)]

truthy, you would want to test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc7-utopic/ and if reproducible provide the information upstream requested. Quoting:
>"And it would be most helpful if you at least posted "lsusb -v" for your camera."

[truthy (martin-rudhart)]

as I found neither 'xhci' nor 'usb' in the changelog I doubt it would work, but I'm gonna test it later today.

I already provided the information upstream requested in my reply to the mailing list (see spinics/marc links above) with an external link as it's too long to be put into the mail itself: http://pastebin.com/CFCqqfDG
it's also uploaded here since 2014-05-15: https://launchpadlibrarian.net/175640585/logitch.c920.lsusb.verbose.txt

I think my email-reply to the mailing list was messed up/wrong somehow as it's not the 3rd thread it should be. at least not at spinics, at marc.info it is. as I was subscribed to the mailing list at the time and received it myself, I at least know that sort of worked.

... did you receive the email I sent to your gmail address today, or was it blocked? sry in advance if that's not proper procedure.

[truthy (martin-rudhart)]

no change with v3.15-rc7-utopic.

[truthy (martin-rudhart)]

I've been asked to enable xhci dynamic debugging (xhci_hcd) with the latest mainline kernel to provide better information about the problem. Can you please tell how to do that - which console command I'd have to input or which files I'd have to alter - I can't seem to get it - googled around a bit.

And after enabling it - they would need the output of grepping xhci and/or usb from kern.log right?

[penalvch (penalvch)]

truthy, the next time you post to an upstream mailing list, one would want to follow https://wiki.ubuntu.com/Bugs/Upstream/kernel , not send some abbreviated post that would not be helpful to anyone in getting your bug solved.

Despite this, you would want to respond to the requester to provide click-for-click instructions on how they would enable and capture the debugging verbatim..

[truthy (martin-rudhart)]

Thank you for responding. Once again I'm sorry for bothering you again/reopening the Bugreport. As it's the 1st time I ever reported any bug - especially a kernel/upstream-bug - I hope you/they will be lenient and forgive my breach of etiquette, format and whatever else I broke ... I submitted a at least partly (logs in message-body) conform Bugreport at the Linux-USB-Mailing list in addition to my respose now. (in the spirit of 'better late than never')
If there'r any changes or if it will be fixed in a future upstream kernel I'll update the Bugreport at Launchpad accordingly.

[True-night (hlpimfalling)]

Just FYI I have the same issue, and unfortunately no USB 2.0 port. Lowering the resolution does work, but I would like to use 720p at least.