webcam "device initialization failed" in lucid (needs high-speed USB 2.0 port) but has worked in past on lucid

Bug #622168 reported by Kim Tyler
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.32-24-generic

uname -a = "Linux pio 2.6.32-24-generic #41-Ubuntu SMP Thu Aug 19 01:38:40 UTC 2010 x86_64 GNU/Linux"

system up-to-date as of 22nd August 2010

sb_release -rd =
Description: Ubuntu 10.04.1 LTS
Release: 10.04

Problem show up in dmesg during boot (see /var/log/messages below)

Webcam should initialize correctly during startup, and be usable during normal use

relevant part of /var/log/messages=

Aug 22 17:26:02 pio kernel: [ 28.796272] em28xx: New device @ 12 Mbps (eb1a:2750, interface 0, class 0)
Aug 22 17:26:02 pio kernel: [ 28.796276] em28xx: Device initialization failed.
Aug 22 17:26:02 pio kernel: [ 28.796277] em28xx: Device must be connected to a high-speed USB 2.0 port.
Aug 22 17:26:02 pio kernel: [ 28.796329] usbcore: registered new interface driver em28xx
Aug 22 17:26:02 pio kernel: [ 28.796332] em28xx driver loaded

lsusb -v=

Bus 002 Device 002: ID eb1a:2750 eMPIA Technology, Inc. ECS Elitegroup G220 integrated Webcam
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0xeb1a eMPIA Technology, Inc.
  idProduct 0x2750 ECS Elitegroup G220 integrated Webcam
  bcdDevice 1.00
  iManufacturer 0
  iProduct 0
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 249
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
      (Bus Powered)
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 255
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0001 1x 1 bytes
        bInterval 100
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 1
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 255
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0001 1x 1 bytes
        bInterval 100
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 2
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 255
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0001 1x 1 bytes
        bInterval 100
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0280 1x 640 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 3
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 255
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0001 1x 1 bytes
        bInterval 100
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0300 1x 768 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 4
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 255
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0001 1x 1 bytes
        bInterval 100
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0340 1x 832 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 5
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 255
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0001 1x 1 bytes
        bInterval 100
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0380 1x 896 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 6
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 255
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0001 1x 1 bytes
        bInterval 100
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x03c0 1x 960 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 7
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 255
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0001 1x 1 bytes
        bInterval 100
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x03fc 1x 1020 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
Device Qualifier (for other device speed):
  bLength 10
  bDescriptorType 6
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  bNumConfigurations 1
Device Status: 0x0000
  (Bus Powered)

The webcam used to work under lucid, but now doesn't. I can't find the module for the usb, is this now part of the kernel and not a module? The webcam been attached to a slow speed USB device instead of the high speed device.

lsusb =

Bus 005 Device 002: ID 0db0:a970 Micro Star International Bluetooth dongle
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID eb1a:2750 eMPIA Technology, Inc. ECS Elitegroup G220 integrated Webcam
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

This is especially annoying since it worked in this release of ubuntu lucid with early kernels. (enumeration of usb devices during kernel load of usb devices is different to enumeration of usb devices during module load?)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kit284 1599 F.... pulseaudio
 /dev/snd/controlC1: kit284 1599 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'V8237'/'VIA 8237 with ALC850 at 0x1800, irq 22'
   Mixer name : 'Realtek ALC850 rev 0'
   Components : 'AC97a:414c4790'
   Controls : 49
   Simple ctrls : 30
Card1.Amixer.info:
 Card hw:1 'SAA7134'/'saa7133[0] at 0xd2206800 irq 22'
   Mixer name : 'SAA7134 Mixer'
   Components : ''
   Controls : 6
   Simple ctrls : 3
Card2.Amixer.info:
 Card hw:2 'modem'/'VIA 82XX modem at 0x1c00, irq 22'
   Mixer name : 'Conexant id 23'
   Components : 'AC97m:43585423'
   Controls : 2
   Simple ctrls : 2
Card2.Codecs.codec97.0.mc97.1.1:
 1-1/0: Conexant id 23

 Extended modem ID: codec=1 LIN1
 Modem status : PRA(GPIO) PRB(res) PRC(ADC1) PRD(DAC1) PRE(ADC2) PRF(DAC2) PRG(HADC) PRH(HDAC)
 Line1 rate : 8000Hz
DistroRelease: Ubuntu 10.10
HibernationDevice: RESUME=UUID=8bc3362d-e136-453f-bb6c-284013a5dd11
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100908)
MachineType: CLEVO D900K
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-20-generic root=UUID=b85f5356-f0bf-4800-bc48-8cae73070e26 ro quiet splash
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Regression: Yes
RelatedPackageVersions: linux-firmware 1.38
Reproducible: Yes
Tags: maverick kernel-config regression-update needs-upstream-testing
Uname: Linux 2.6.35-20-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/06/2005
dmi.bios.vendor: Phoenix
dmi.bios.version: 4.06CJ15
dmi.board.name: D900K
dmi.board.vendor: CLEVO
dmi.board.version: VT8341B
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd12/06/2005:svnCLEVO:pnD900K:pvrVT8341B:rvnCLEVO:rnD900K:rvrVT8341B:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: D900K
dmi.product.version: VT8341B
dmi.sys.vendor: CLEVO

---
Architecture: amd64
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
Package: linux (not installed)
ProcEnviron:
 LANG=en_AU.utf8
 SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.36-020636rc3-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lp lpadmin mythtv netdev plugdev sambashare tape vboxusers video

Revision history for this message
Kim Tyler (ktyler) wrote :

I loaded a live CD of lucid, and the webcam works!

grep em28 log :=

Aug 22 11:29:14 ubuntu kernel: [ 30.299722] em28xx: New device @ 480 Mbps (eb1a:2750, interface 0, class 0)
Aug 22 11:29:14 ubuntu kernel: [ 30.300457] em28xx #0: chip ID is em2750
Aug 22 11:29:15 ubuntu kernel: [ 30.902872] em28xx #0: Identified as EM2710/EM2750/EM2751 webcam grabber (card=22)
Aug 22 11:29:15 ubuntu kernel: [ 30.902958] em28xx #0: Config register raw data: 0x00
Aug 22 11:29:15 ubuntu kernel: [ 30.902962] em28xx #0: v4l2 driver version 0.1.2
Aug 22 11:29:16 ubuntu kernel: [ 31.562699] em28xx #0: V4L2 video device registered as /dev/video1
Aug 22 11:29:16 ubuntu kernel: [ 31.562733] usbcore: registered new interface driver em28xx
Aug 22 11:29:16 ubuntu kernel: [ 31.562736] em28xx driver loaded

Revision history for this message
Kim Tyler (ktyler) wrote :

Anything else you need from me to proceed?

Revision history for this message
Kim Tyler (ktyler) wrote :

I'm a bit worried about claims of "long-term-support" when there seems to be little "short-term-support"

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Kim,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 622168

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Kim Tyler (ktyler) wrote : AcpiTables.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Kim Tyler (ktyler) wrote : AlsaDevices.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : AplayDevices.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : ArecordDevices.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : BootDmesg.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : Card0.Codecs.codec97.0.ac97.0.0.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : Card0.Codecs.codec97.0.ac97.0.0.regs.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : Card1.Amixer.values.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : Card2.Amixer.values.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : Card2.Codecs.codec97.0.mc97.1.1.regs.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : IwConfig.txt

apport information

Revision history for this message
Kim Tyler (ktyler) wrote : Lspci.txt

apport information

Kim Tyler (ktyler)
description: updated
Revision history for this message
Kim Tyler (ktyler) wrote :

Hi - can't find the tag needs-upstream testing - I have tested it with mainline linux-headers-2.6.36-020636rc3-generic_2.6.36-020636rc3.201008300905_amd64.deb et al

Same problem - I have sent an apport-collect to the developers.

I note also that the problem seems to be interrupt lost with CD/DVD as well, and other USB devices going nuts, eg bluetooth on USB device. A google search show that others have reported these sorts of problems when the USB drivers went into the kernel instead of being modules, and one tester reported that he compiled kernel with USB as module (the only change) and all worked magically well.

Hopes this helps - I'm almost at point of going back to windows 7 after being on linux for many years. (sigh!)

Revision history for this message
Kim Tyler (ktyler) wrote :
Download full text (5.6 KiB)

After adding some packages yesterday to maverick (nvidia driver, compiz, etc) and adding any updates, I rebooted again today into maverick, and the webcam works!

Rebooted from cold, and webcam failed again.

I'll have a look at whether cold boot or reboot from different versions of ubuntu cause problems.

For your information...........................

from /var/log/messages and /var/log/messages.1 (see near bottom where it worked)

grep em28 /var/log/messages.1 /var/log/messages
/var/log/messages.1:Sep 9 12:16:55 pio kernel: [ 9.641939] em28xx: New device @ 12 Mbps (eb1a:2750, interface 0, class 0)
/var/log/messages.1:Sep 9 12:16:55 pio kernel: [ 9.641944] em28xx: Device initialization failed.
/var/log/messages.1:Sep 9 12:16:55 pio kernel: [ 9.641946] em28xx: Device must be connected to a high-speed USB 2.0 port.
/var/log/messages.1:Sep 9 12:16:55 pio kernel: [ 9.642474] usbcore: registered new interface driver em28xx
/var/log/messages.1:Sep 9 12:16:55 pio kernel: [ 9.642477] em28xx driver loaded
/var/log/messages.1:Sep 9 12:23:57 pio kernel: [ 14.921127] em28xx: New device @ 12 Mbps (eb1a:2750, interface 0, class 0)
/var/log/messages.1:Sep 9 12:23:57 pio kernel: [ 14.921130] em28xx: Device initialization failed.
/var/log/messages.1:Sep 9 12:23:57 pio kernel: [ 14.921132] em28xx: Device must be connected to a high-speed USB 2.0 port.
/var/log/messages.1:Sep 9 12:23:57 pio kernel: [ 14.921390] usbcore: registered new interface driver em28xx
/var/log/messages.1:Sep 9 12:23:57 pio kernel: [ 14.921392] em28xx driver loaded
/var/log/messages.1:Sep 9 12:27:32 pio kernel: [ 15.731575] em28xx: New device @ 12 Mbps (eb1a:2750, interface 0, class 0)
/var/log/messages.1:Sep 9 12:27:32 pio kernel: [ 15.731578] em28xx: Device initialization failed.
/var/log/messages.1:Sep 9 12:27:32 pio kernel: [ 15.731579] em28xx: Device must be connected to a high-speed USB 2.0 port.
/var/log/messages.1:Sep 9 12:27:32 pio kernel: [ 15.732084] usbcore: registered new interface driver em28xx
/var/log/messages.1:Sep 9 12:27:32 pio kernel: [ 15.732088] em28xx driver loaded
/var/log/messages.1:Sep 9 12:32:52 pio kernel: [ 14.787093] em28xx: New device @ 12 Mbps (eb1a:2750, interface 0, class 0)
/var/log/messages.1:Sep 9 12:32:52 pio kernel: [ 14.787096] em28xx: Device initialization failed.
/var/log/messages.1:Sep 9 12:32:52 pio kernel: [ 14.787097] em28xx: Device must be connected to a high-speed USB 2.0 port.
/var/log/messages.1:Sep 9 12:32:52 pio kernel: [ 14.787389] usbcore: registered new interface driver em28xx
/var/log/messages.1:Sep 9 12:32:52 pio kernel: [ 14.787392] em28xx driver loaded
/var/log/messages.1:Sep 9 11:18:58 pio kernel: [ 15.606967] em28xx: New device @ 12 Mbps (eb1a:2750, interface 0, class 0)
/var/log/messages.1:Sep 9 11:18:58 pio kernel: [ 15.606969] em28xx: Device initialization failed.
/var/log/messages.1:Sep 9 11:18:58 pio kernel: [ 15.606971] em28xx: Device must be connected to a high-speed USB 2.0 port.
/var/log/messages.1:Sep 9 11:18:58 pio kernel: [ 15.607129] usbcore: registered new interface driver em28xx
/var/log/messages.1:Sep 9 11:18:58 pio kernel: [ 15.6...

Read more...

Revision history for this message
Kim Tyler (ktyler) wrote :

hmmm..... it seems there is no consistent answer, except that the webcam etc works depending on the startup time - it is looking like a timing problem. Perhaps the webcam etc is initialized too soon, before it is ready?

Revision history for this message
Kim Tyler (ktyler) wrote :

I toggled the /etc/default/irqbalance "ENABLED=..." in both lucid (1=>0) and maverick(0=>1), and the webcam is now working in both, although the picture is shot thorough with green horizontal lines and breaking up badly.

This is the first time that the webcam has worked in lucid, apart from the live CD. I'm not sure if it will continue to work, but I'll keep checking

Revision history for this message
Kim Tyler (ktyler) wrote :

There seems to be no consistent way of making the webcam work repeatedly across reboots. Sometimes it connects at 480Mbps, and works correctly at all resolutions, sometimes at 12Mbps and only works correctly at low resolutions, (higher resolutions get a lot of green lines splattered across video, and is unstable), sometimes connects at 12Mbps with no associated /dev/videox entry, (I also have tv card for the other /dev/videox entry), and sometimes fails altogether during boot.

If it doesn't work, it is unlikely to work unless I add/delete packages (eg update-manager updates) or I fiddle with /etc/default/irqbalance parameters. Once it is working, it is unlikely to remain working across reboots, either shutdown/startup or reboot.

Given that it worked perfectly in karmic, it would hint at something in boot procedure.

Maverick is more likely to produce working webcam, but it has worked properly under lucid. (not as likely though)

Revision history for this message
Kim Tyler (ktyler) wrote :
Download full text (4.1 KiB)

After being up for a while with the webcam working, a lost interrupt has caused the webcam to re-initialize and fail.

from /var/log/messages :-
Sep 15 09:25:56 pio kernel: [ 203.107480] xc2028 1-0061: Loading firmware for type=(0), id 0000000100000007.
Sep 15 09:25:57 pio kernel: [ 203.520033] xc2028 1-0061: Loading SCODE for type=MONO SCODE HAS_IF_5320 (60008000), id 0000000f00000007.
Sep 15 09:28:00 pio kernel: [ 326.840054] xc2028 1-0061: Loading firmware for type=BASE F8MHZ (3), id 0000000000000000.
Sep 15 09:28:20 pio kernel: [ 347.070039] xc2028 1-0061: Loading firmware for type=D2633 DTV7 (90), id 0000000000000000.
Sep 15 09:28:21 pio kernel: [ 347.470025] xc2028 1-0061: Loading SCODE for type=SCODE HAS_IF_5260 (60000000), id 0000000000000000.
Sep 15 09:36:26 pio kernel: [ 833.040095] ata2: lost interrupt (Status 0x51)
Sep 15 09:36:31 pio kernel: [ 838.040099] ata2.01: qc timeout (cmd 0xa0)
Sep 15 09:36:31 pio kernel: [ 838.040128] sr 1:0:1:0: CDB: Test Unit Ready: 00 00 00 00 00 00
Sep 15 09:36:31 pio kernel: [ 838.040192] ata2: soft resetting link
Sep 15 09:36:32 pio kernel: [ 838.280459] ata2.00: configured for UDMA/33
Sep 15 09:36:32 pio kernel: [ 838.320451] ata2.01: configured for UDMA/33
Sep 15 09:36:37 pio kernel: [ 843.320052] ata2.00: qc timeout (cmd 0xa0)
Sep 15 09:36:37 pio kernel: [ 843.320065] ata2.00: TEST_UNIT_READY failed (err_mask=0x5)
Sep 15 09:36:37 pio kernel: [ 843.320100] ata2: soft resetting link
Sep 15 09:36:37 pio kernel: [ 843.560375] ata2.00: configured for UDMA/33
Sep 15 09:36:37 pio kernel: [ 843.600440] ata2.01: configured for UDMA/33
Sep 15 09:36:42 pio kernel: [ 848.600052] ata2.00: qc timeout (cmd 0xa0)
Sep 15 09:36:42 pio kernel: [ 848.600065] ata2.00: TEST_UNIT_READY failed (err_mask=0x5)
Sep 15 09:36:42 pio kernel: [ 848.600074] ata2.00: limiting speed to UDMA/33:PIO3
Sep 15 09:36:42 pio kernel: [ 848.600107] ata2: soft resetting link
Sep 15 09:36:42 pio kernel: [ 848.840358] ata2.00: configured for UDMA/33
Sep 15 09:36:42 pio kernel: [ 848.880471] ata2.01: configured for UDMA/33
Sep 15 09:36:47 pio kernel: [ 853.880066] ata2.00: qc timeout (cmd 0xa0)
Sep 15 09:36:47 pio kernel: [ 853.880079] ata2.00: TEST_UNIT_READY failed (err_mask=0x5)
Sep 15 09:36:47 pio kernel: [ 853.880085] ata2.00: disabled
Sep 15 09:36:47 pio kernel: [ 853.880107] ata2.01: TEST_UNIT_READY failed (err_mask=0x40)
Sep 15 09:36:47 pio kernel: [ 853.880135] ata2: soft resetting link
Sep 15 09:36:47 pio kernel: [ 854.100461] ata2.01: configured for UDMA/33
Sep 15 09:36:52 pio kernel: [ 859.100057] ata2.01: qc timeout (cmd 0xa0)
Sep 15 09:36:52 pio kernel: [ 859.100070] ata2.01: TEST_UNIT_READY failed (err_mask=0x5)
Sep 15 09:36:52 pio kernel: [ 859.100079] ata2.01: limiting speed to UDMA/33:PIO3
Sep 15 09:36:52 pio kernel: [ 859.100112] ata2: soft resetting link
Sep 15 09:36:53 pio kernel: [ 859.320458] ata2.01: configured for UDMA/33
Sep 15 09:36:58 pio kernel: [ 864.320051] ata2.01: qc timeout (cmd 0xa0)
Sep 15 09:36:58 pio kernel: [ 864.320064] ata2.01: TEST_UNIT_READY failed (err_mask=0x5)
Sep 15 09:36:58 pio kernel: [ 864.320070] ata2.01: disabled
Sep 15 09:36:58 pio kernel: [ 864.320128]...

Read more...

Revision history for this message
Kim Tyler (ktyler) wrote :

I have recompiled a new kernel grom the git tree - 2.6.32-25, with the only configuration change being the drivers ehci_hcd and uhci_hcd being module instead of in the kernel.

By rmmod ehci_hcd followed by modprobe ehci_hcd, the webcam sometimes springs into life. (and sometimes not)

By removing the module, the webcam attaches to slow speed USB and fails (logic in em28xx). modprobing em28xx causes the webcam to attach again to the slow speed USB again (and fail) or attach to the high speed USB and therefore work correctly. At least by using modules, I can avoid having to reboot to alter the state of the drivers.

If you would like the dmesg and/or /var/log/messages, please let me know. (the logs look very similar to successful and unsuccessful logs attached above)

good luck

Revision history for this message
Kim Tyler (ktyler) wrote :
Download full text (41.4 KiB)

Have tried using rmmod / modprobe as above when webcam fails, but am now occasional stack trace, when using command line "rmmod uhci_hcd ; sleep 5 ; rmmod ehci_hcd ; sleep 5 ; modprobe ehci_hcd ; sleep 5 ; modprobe uhci_hcd"

Trace =>

Sep 23 12:13:58 pio kernel: [ 8217.406590] ------------[ cut here ]------------
Sep 23 12:13:58 pio kernel: [ 8217.406597] WARNING: at /home/kit284/devel/kernel/lucid-git/source/drivers/usb/core/driver.c:1343 usb_autopm_do_device+0x11e/0x130()
Sep 23 12:13:58 pio kernel: [ 8217.406603] Hardware name: D900K
Sep 23 12:13:58 pio kernel: [ 8217.406605] Modules linked in: uhci_hcd(+) ehci_hcd iptable_filter ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables cryptd aes_x86_64 aes_generic rfcomm binfmt_misc sco bridge stp bnep l2cap snd_atiixp_modem mt352 saa7134_dvb videobuf_dvb dvb_core saa7134_alsa snd_intel8x0m nfsd exportfs nfs lockd nfs_acl auth_rpcgss snd_via82xx snd_via82xx_modem gameport snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm tuner_xc2028 snd_seq_dummy snd_mpu401_uart snd_seq_oss snd_seq_midi fbcon tileblit font snd_rawmidi snd_seq_midi_event edac_core snd_seq pcmcia bitblit snd_timer tuner edac_mce_amd softcursor snd_seq_device nvidia(P) k8temp arc4 snd snd_page_alloc saa7134 vga16fb soundcore vgastate yenta_socket btusb bluetooth joydev videobuf_dma_sg rsrc_nonstatic bonding sunrpc rt2500pci rt2x00pci rt2x00lib led_class mac80211 em28xx v4l2_common videodev v4l1_compat pcmcia_core v4l2_compat_ioctl32 ppdev i2c_viapro cfg80211 eeprom_93cx6 ns
Sep 23 12:13:58 pio kernel: c_ircc irda video output ir_common videobuf_vmalloc videobuf_core tveeprom shpchp psmouse serio_raw parport_pc crc_ccitt lp parport usbhid hid ohci1394 sata_via ieee1394 r8169 mii pata_via [last unloaded: uhci_hcd]
Sep 23 12:13:58 pio kernel: [ 8217.406739] Pid: 1355, comm: upowerd Tainted: P W 2.6.32-25-core2 #44
Sep 23 12:13:58 pio kernel: [ 8217.406743] Call Trace:
Sep 23 12:13:58 pio kernel: [ 8217.406750] [<ffffffff81065efb>] warn_slowpath_common+0x7b/0xc0
Sep 23 12:13:58 pio kernel: [ 8217.406757] [<ffffffff81065f54>] warn_slowpath_null+0x14/0x20
Sep 23 12:13:58 pio kernel: [ 8217.406764] [<ffffffff813da57e>] usb_autopm_do_device+0x11e/0x130
Sep 23 12:13:58 pio kernel: [ 8217.406771] [<ffffffff813da5e3>] usb_autosuspend_device+0x13/0x20
Sep 23 12:13:58 pio kernel: [ 8217.406779] [<ffffffff813dfb35>] usbdev_release+0xd5/0x130
Sep 23 12:13:58 pio kernel: [ 8217.406786] [<ffffffff81144995>] __fput+0xf5/0x210
Sep 23 12:13:58 pio kernel: [ 8217.406793] [<ffffffff81144ad5>] fput+0x25/0x30
Sep 23 12:13:58 pio kernel: [ 8217.406799] [<ffffffff81140bcd>] filp_close+0x5d/0x90
Sep 23 12:13:58 pio kernel: [ 8217.406806] [<ffffffff81140cb7>] sys_close+0xb7/0x120
Sep 23 12:13:58 pio kernel: [ 8217.406813] [<ffffffff810121b2>] system_call_fastpath+0x16/0x1b
Sep 23 12:13:58 pio kernel: [ 8217.406818] ---[ end trace abad110792e1f3e1 ]---
Sep 23 12:13:58 pio kernel: [ 8217.415394] uhci_hcd 0000:00:10.2: PCI INT B -> Link[ALKD] -> GSI 21 (level, low) -> IRQ 21
Sep 23 12:13:58 pio kernel: [ 8217.415418] uhci_hcd 0000:00:10.2: UHCI Host Controller
Sep 23 12:13:58 pio kernel...

Revision history for this message
Sina Eetezadi (sina-eetezadi) wrote :

Kim, please keep going on this! It affects me to and I would be sooo happy if it can be resolved somehow.

Revision history for this message
Kim Tyler (ktyler) wrote :

I have removed the nvidia driver (installed and uninstalled via the hardware drivers utility system->administration) and the system is using nouveau drivers.

Webcam back to normal from restart and from cold boot. (so far, touch wood, after 4 restarts)

Also cpu usage is lower with nouveau than with nvidia driver. (go figure!)

I will continue to test and report findings. I am currently still using rebuild kernel with ehci_hcd and uhci_hcd as midules, but will remove nvidia from normal apt tree and try that as well.

I will also try maverick without nvidia (currently installed) and also report for upstream. Can I get compiz with nouveau? (it doesn't look like it)

Revision history for this message
Kim Tyler (ktyler) wrote :

Nvidia is not the problem. Problem eventually re-surfaces after a cold boot, but subsequent warm boots/restarts can fix the problem. I have reinstalled nvidia, and webcam is working OK with nvidia driver. (as above, except after cold boot).

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Kim Tyler (ktyler) wrote :

Hey guys, we're still waiting for a solution out here. Expiring it because nobody there is doing anything about it would seem to be a bit wrong.

The problem still exist with lucid and maverick.

I have tried it with a backport linux-image-2.6.37-020637rc2-generic_2.6.37-020637rc2.201011160905_amd64.deb and others, and the problem still exists with those kernels.

I couldn't reset the tag 'needs-upstream-testing'. (perhaps I need lessons)

Is anyone doing anything with this bug, or do the users not bother. (the option is to either go the windows 7, or to buy another PC, neither of which is appealing to me, and doesn't fit with the ethos that Linux can run on most hardware without problems)

Merry Xmas and happy new year

Revision history for this message
Sina Eetezadi (sina-eetezadi) wrote :

I also have the same issue on Lucid and no solution.

So far I am using Windows 7 in a Virtual Machine which is of course not the preferred way out.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.