https://bugzilla.kernel.org/show_bug.cgi?id=52471 Summary: usb device removed from sysfs before input children devices Product: Drivers Version: 2.5 Kernel Version: 3.7 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: USB AssignedTo: greg@xxxxxxxxx ReportedBy: karllinuxtest.relton@xxxxxxxxxxxx CC: linux-bluetooth@xxxxxxxxxxxxxxx Regression: Yes Created an attachment (id=90741) --> (https://bugzilla.kernel.org/attachment.cgi?id=90741) udevadm monitor log On coming out of suspend my usb bluetooth adaptor is being reset by the system. In linux 3.7 the usb devices are being removed from the sysfs tree first, and then the various 'child' devices (like my bluetooth mouse & keyboard related devices) afterwards. This is causing the udev events for the input devices to have 'orphaned' sysfs paths in the udev events. This in term means the Xorg evdev driver does not recognise the events, and so doesn't see the removal of in the put devices. This has been picked by some downstream distributions, e.g. see this thread by Google Chrome developers: http://code.google.com/p/chromium-os/issues/detail?id=33813 Back on linux 3.2 this was not the case. The usb adaptor was reset, but device removal was orderly: first the input devices (will full paths in the udev events), then the usb devices walking up the tree. The attachment is a fragment captured by udevadm monitor when running 3.7. See how the usb devices are moved first, and then the input/bluetooth related stuff with path-heads removed (paths are now /hci0/... instead of /devices/...) -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
