From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Marcel Holtmann" <marcel@holtmann.org>,
"Kay Sievers" <kay.sievers@vrfy.org>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
systemd-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] hid2hci: Fix udev rules for linux-4.14+
Date: Mon, 5 Nov 2018 19:54:16 +0200 [thread overview]
Message-ID: <20181105175416.GO9144@intel.com> (raw)
In-Reply-To: <20180620164240.6535-1-ville.syrjala@linux.intel.com>
On Wed, Jun 20, 2018 at 07:42:40PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.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.
>
> Change the udev rules not do anything except for "add" and
> "change" events. This seems to cure my machine at least.
>
> v2: Don't mess up "change" (Zbyszek)
> Fix up the commit message a bit
Ping. Can someone push this?
>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Marcel Holtmann <marcel@holtmann.org>
> Cc: Kay Sievers <kay.sievers@vrfy.org>
> Cc: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
> Cc: systemd-devel@lists.freedesktop.org
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-bluetooth@vger.kernel.org
> Signed-off-by: Ville Syrjälä <ville.syrjala@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..5c7208af7a02 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|change", GOTO="hid2hci_end"
> SUBSYSTEM!="usb*", GOTO="hid2hci_end"
>
> # Variety of Dell Bluetooth devices - match on a mouse device that is
> --
> 2.16.4
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2018-11-05 17:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 13:06 [PATCH bluez] hid2hci: Fix udev rules for linux-4.14+ Ville Syrjala
2018-05-07 17:44 ` [systemd-devel] " Zbigniew Jędrzejewski-Szmek
2018-06-20 16:46 ` Ville Syrjälä
2018-06-20 16:42 ` [PATCH v2] " Ville Syrjala
2018-11-05 17:54 ` Ville Syrjälä [this message]
2018-12-04 20:41 ` [PATCH v2 BlueZ] " Ville Syrjala
2018-12-05 7:06 ` Greg Kroah-Hartman
2018-12-05 15:40 ` Ville Syrjälä
2018-12-05 19:09 ` Dag B
2018-12-05 19:21 ` Greg Kroah-Hartman
2018-12-05 19:20 ` Greg Kroah-Hartman
2018-12-05 19:40 ` Ville Syrjälä
2018-12-05 19:49 ` Greg Kroah-Hartman
2019-04-23 15:41 ` Ville Syrjälä
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181105175416.GO9144@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=systemd-devel@lists.freedesktop.org \
--cc=zbyszek@in.waw.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.