[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181205070621.GE16346@kroah.com>
Date: Wed, 5 Dec 2018 08:06:21 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Ville Syrjala <ville.syrjala@...ux.intel.com>
Cc: linux-bluetooth@...r.kernel.org,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Marcel Holtmann <marcel@...tmann.org>,
Kay Sievers <kay.sievers@...y.org>,
Zbigniew Jędrzejewski-Szmek <zbyszek@...waw.pl>,
systemd-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 BlueZ] hid2hci: Fix udev rules for linux-4.14+
On Tue, Dec 04, 2018 at 10:41:17PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@...ux.intel.com>
>
> Since commit 1455cf8dbfd0 ("driver core: emit uevents when
> device is bound to a driver") the kernel started emitting
> "bind" and "unbind" 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
> "bind"+"unbind" uevents.
What is causing a "stream" of bind and unbind events? This only happens
when a device is attached to a driver or removed from a driver, which is
caused by something else happening. This should not be a normal
occurance, unless something odd is happening to your hardware?
thanks,
greg k-h
Powered by blists - more mailing lists