From: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> Since commit 1455cf8dbfd0 ("driver core: emit uevents when device is bound to a driver") the kernel started emitting "bound" and "unbound" uevents which confuse the hid2hci udev rules. The symptoms on an affected machine (Dell E5400 in my case) include bluetooth devices not appearing and udev hogging the cpu as it's busy processing a constant stream of these "bound"+"unbound" uevents. Change the udev rules only kick in for an "add" event. This seems to cure my machine at least. Cc: Dmitry Torokhov <dmitry.torokhov at gmail.com> Cc: Greg Kroah-Hartman <gregkh at linuxfoundation.org> Cc: Marcel Holtmann <marcel at holtmann.org> Cc: Kay Sievers <kay.sievers at vrfy.org> Cc: systemd-devel at lists.freedesktop.org Cc: linux-kernel at vger.kernel.org Cc: linux-bluetooth at vger.kernel.org Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com> --- tools/hid2hci.rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/hid2hci.rules b/tools/hid2hci.rules index db6bb03d2ef3..daa381d77387 100644 --- a/tools/hid2hci.rules +++ b/tools/hid2hci.rules @@ -1,6 +1,6 @@ # do not edit this file, it will be overwritten on update -ACTION=="remove", GOTO="hid2hci_end" +ACTION!="add", GOTO="hid2hci_end" SUBSYSTEM!="usb*", GOTO="hid2hci_end" # Variety of Dell Bluetooth devices - match on a mouse device that is -- 2.16.1