From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 199035] BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel
Date: Sat, 13 Apr 2019 17:34:37 +0000 [thread overview]
Message-ID: <bug-199035-62941-aGKfcDykFi@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199035-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199035
--- Comment #15 from gustavo.willer@hotmail.com ---
I fix the problem with this approach:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/comments/70
from "Florian Dittmer (fd81)"
"
Following the instructions mentioned by one user in the comments helped me to
solve the cpu load issue with udev-239 and kernel 4.18.17, while Bluetooth
still works.
Run the following command:
/lib/systemd/systemd-udevd -D
This should print garbage in endless loop containing ".../97-hid2hci.rules:"
If so, edit /lib/udev/rules.d/97-hid2hci.rules
and add
ACTION=="add",
in front of line mentioned by above command.
In my case, I had to change the following lines in 97-hid2hci.rules from:
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01",
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
to:
ACTION=="add", ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01",
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
And this fixed the issue (after reboot).
"
from
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-04-13 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199035-62941@https.bugzilla.kernel.org/>
2018-10-18 17:53 ` [Bug 199035] BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel bugzilla-daemon
2018-12-22 17:54 ` bugzilla-daemon
2019-01-08 18:42 ` bugzilla-daemon
2019-01-08 19:38 ` bugzilla-daemon
2019-04-13 14:02 ` bugzilla-daemon
2019-04-13 17:23 ` bugzilla-daemon
2019-04-13 17:34 ` bugzilla-daemon [this message]
2019-04-13 18:30 ` bugzilla-daemon
2019-04-13 23:27 ` bugzilla-daemon
2019-04-14 14:22 ` bugzilla-daemon
2022-04-13 15:14 ` bugzilla-daemon
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=bug-199035-62941-aGKfcDykFi@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).