[ 8.160759] uvcvideo: Found UVC 1.00 device BisonCam, NB Pro (5986:0203) ...running fsck in the meantime... [ 102.188017] ehci_hcd 0000:00:1d.7: force halt; handhake f803a024 00004000 00000000 -> -110 [ 102.191531] hub 1-0:1.0: cannot reset port 6 (err = -108)
r...@machine:~# lsmod | grep uvc uvcvideo 59016 0 videodev 36672 1 uvcvideo v4l1_compat 14496 2 uvcvideo,videodev On my LG X110-L.A7SAG (which is quite a clone of MSI Wind) running Jaunty with the Kernel Backports ppa of user a7x, this happens since udev 145-1 appeared, and through the kernel 2.6.31-X rc-pre-releases until current 2.6.31-10.34 and udev 147. Earlier (without packages requiring newer udev) the ehci_hcd force halt didn't happen when udev was held on Jaunty's 141-1.2. Symptoms are very similar to the original report. Found it happens always after cold start (power off, USB devices without power, power cable disconnected before). 50/50 when rebooting warm with "init 6". When ehci_hcd force halt doesn't occur after reboot, system is running stable and USB 2.0 devices work normal (external DVB-T stick (dib0700) and external generic USB storage). Changing/Removing USB devices shows no effect, the devices are plugged in before start. I noticed (and this seems to be normal, I'dont know if it's important) boot behaviour on USB is different in cold/warm start. The light of my GSM modem (Huawei E169G on USB 1.1) shows a reset on cold boot and normal operation on warm boot. The 2.0 devices don't indicate, means I cannot see if they are reset or not at cold boot. syslog doesn't tell what happens. echi_hcd force halt during boot always happens *after* devices are detected and DVB-T stick is initialized successfully (with successful firmware load on cold boot). I suspected a coincidence with hal start but upgrade to hal 0.5.13-1ubuntu7 didn't help. I appreciate debug hints. syslog extract attached. -- regression: uvcvideo module makes "cannot reset port" error on usb with bison webcam (5986:0203): USB and suspend fails https://bugs.launchpad.net/bugs/435352 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
