On Thu, 25 Jun 2009 15:15:14 -0400 (EDT) Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Thu, 25 Jun 2009, Andrew Morton wrote: > > > > http://bugzilla.kernel.org/show_bug.cgi?id=13624 > > > > > > Summary: usb: wrong autosuspend initialization > > > > My optical usb mouse (Logitech MX500, 046d:c025) turns its LED off after 2 > > > seconds of idling. That means I have to press a button to wake it up again. > > > > > > This happens only if it's connected at bootup: > > > # cat /sys/bus/usb/devices/2-1/power/level > > > auto > > > > > > then after I replug it: > > > # cat /sys/bus/usb/devices/2-1/power/level > > > on > > > > > > which then results in the desired behaviour (LED stays on). This is new since > > > 2.6.30. I'm using the gentoo patchset, but I'll assume they didn't tamper with > > > usb autosuspend there. > > > > > > > Seems to be a 2.6.29->2.6.30 regression. > > This should be rejected as a duplicate of Bug #13505. > But #13505 was closed as "invalid". That's two people now whose systems have falied when they switched from a 2.6.29 kernel to a 2.6.30 kernel. That is a kernel-caused regression. What is the justification for not fixing this kernel-caused regression within the kernel? -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
