http://bugzilla.opensuse.org/show_bug.cgi?id=967490 http://bugzilla.opensuse.org/show_bug.cgi?id=967490#c2 --- Comment #2 from Thomas Mitterfellner --- The light turns on shortly when I power up the laptop but then turns off again. It turns on again shortly after choosing to boot openSUSE. It still happens with kernel 4.1.18-8.gb9ac3b9-default. When I use the camera in skype, e.g. when I go to the video configuration, the light is on, but as soon as I close that options dialog, the light turns off. It seems that skype set the camera to a sane state again. One strange thing is that 2-3 times already the /dev/video0 device just disappeared. Unfortunately, I could not yet find out how to trigger this (I just remember using v4l2-ctl to display some info about the camera in one case. I do not know how to get /dev/video0 back in such a case - do you? I'll attach the dmesg output and the hwinfo output, just in case. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967490 http://bugzilla.opensuse.org/show_bug.cgi?id=967490#c4 --- Comment #4 from Thomas Mitterfellner --- Created attachment 667544 --> http://bugzilla.opensuse.org/attachment.cgi?id=667544&action=edit dmesg output right after booting -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967490 http://bugzilla.opensuse.org/show_bug.cgi?id=967490#c6 --- Comment #6 from Thomas Mitterfellner --- I noticed two things in the hwinfo output, not sure whether this is relevant/problematic: the camera is listed under "Unclassified device" and the device file is /dev/input/event10 - shouldn't this be video0 or /dev/video0? 44: USB 00.0: 0000 Unclassified device [Created at usb.122] Unique ID: R_O4.tUMftoC_b10 Parent ID: pBe4.2DFUsyrieMD SysFS ID: /devices/pci0000:00/0000:00:14.0/usb2/2-6/2-6:1.0 SysFS BusID: 2-6:1.0 Hardware Class: unknown Model: "IMC Networks Lenovo EasyCamera" Hotplug: USB Vendor: usb 0x13d3 "IMC Networks" Device: usb 0x5744 "Lenovo EasyCamera" Revision: "7.31" Driver: "uvcvideo" Driver Modules: "uvcvideo" Device File: /dev/input/event10 Device Files: /dev/input/event10, /dev/input/by-id/usb-13d3_Lenovo_EasyCamera-event-if00, /dev/input/by-path/pci-0000:00:14.0-usb-0:6:1.0-event Device Number: char 13:74 Speed: 480 Mbps Module Alias: "usb:v13D3p5744d0731dcEFdsc02dp01ic0Eisc01ip00in00" Driver Info #0: Driver Status: uvcvideo is active Driver Activation Cmd: "modprobe uvcvideo" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #42 (Hub) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967490 http://bugzilla.opensuse.org/show_bug.cgi?id=967490#c8 --- Comment #8 from Takashi Iwai --- (In reply to Thomas Mitterfellner from comment #5)

I forgot to ask: how do I determine whether the runtime PM is enabled on this usb device?

Check /sys/bus/usb/devices/$DEVICE/power/* files. Fill the right one corresponding to your webcam. In doubt, you can confirm the product name or such information in /sys/bus/usb/devices/$DEVICE directory, too. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967490 http://bugzilla.opensuse.org/show_bug.cgi?id=967490#c10 --- Comment #10 from Thomas Mitterfellner --- Created attachment 667852 --> http://bugzilla.opensuse.org/attachment.cgi?id=667852&action=edit Output of lsusb -v -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967490 http://bugzilla.opensuse.org/show_bug.cgi?id=967490#c12 Oliver Neukum changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(thomas@mitterfell | |ner.at) --- Comment #12 from Oliver Neukum --- (In reply to Thomas Mitterfellner from comment #9)

root@linux:~> for i in /sys/bus/usb/devices/1-6:1.0/power/* ; do echo -n "$i: " ; cat $i ; done /sys/bus/usb/devices/1-6:1.0/power/async: enabled /sys/bus/usb/devices/1-6:1.0/power/runtime_active_kids: 0 /sys/bus/usb/devices/1-6:1.0/power/runtime_enabled: enabled /sys/bus/usb/devices/1-6:1.0/power/runtime_status: suspended /sys/bus/usb/devices/1-6:1.0/power/runtime_usage: 0

Interesting thing is: when I do lsusb -v, the light goes out!

When you do lsusb as root, the device usage count is upped to allow retrival of the descriptors and lowered again. If you land at zero, a runtime suspension is triggered on video devices. Unfortunately there are at least two obvious potential causes 1) a fatal error returned from suspend() 2) the wrong kind of primitive is used in the uvc driver First we need to confirm this theory. Could you do cat /sys/bus/usb/devices/$DEVICE/power/level echo on > /sys/bus/usb/devices/$DEVICE/power/level echo auto > /sys/bus/usb/devices/$DEVICE/power/level Your light should go out after 2 seconds. What is the result of the cat? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967490 http://bugzilla.opensuse.org/show_bug.cgi?id=967490#c14 --- Comment #14 from Oliver Neukum --- (In reply to Thomas Mitterfellner from comment #13)

Unfortunately, it will take a little while until I can test this on the machine itself, BUT: I'm pretty sure /sys/bus/usb/devices/$DEVICE/power/level does not exist as you can see from the output of

for i in /sys/bus/usb/devices/1-6:1.0/power/* ; do echo -n "$i: " ; cat $i ; done

I posted above, i.e. the only files residing there are:

async, runtime_active_kids, runtime_enabled, runtime_status, and runtime_usage.

You are looking into the wrong directory. Possibly you are looking at the device, not at the interface.

That said, I could of course try the two echo commands. OTOH, I just read here https://www.kernel.org/doc/Documentation/usb/power-management.txt that power/level is deprecated since kernel 2.6.35, so I should probably try this with power/control?

It doesn't matter which file you use. Please test. -- You are receiving this mail because: You are on the CC list for the bug.