Hmm, I'm getting the feeling that this may be related to bug 625852, which is also happening since F-12. I have 2 theories now:
1) Something changed in userspace and is probing the usb device in a way it does
not like. I believe this is what is happening in your case. You write that
simply opening /dev/bus/usb/001/002 is enough to re-enable the led.
Can you try turning the led off by running a webcam using app and then do:
udevadm trigger --action=add
And see if this turns the led on again?
2) USB autosuspend is somehow causing this issue. Can you try booting
with usbcore.autosuspend=-1 added your kernel cmdline and see if that helps?
Hi,
Hmm, I'm getting the feeling that this may be related to bug 625852, which is also happening since F-12. I have 2 theories now:
1) Something changed in userspace and is probing the usb device in a way it does usb/001/ 002 is enough to re-enable the led.
not like. I believe this is what is happening in your case. You write that
simply opening /dev/bus/
Can you try turning the led off by running a webcam using app and then do:
udevadm trigger --action=add
And see if this turns the led on again?
2) USB autosuspend is somehow causing this issue. Can you try booting autosuspend= -1 added your kernel cmdline and see if that helps?
with usbcore.
Thanks,
Hans