[Kernel-packages] [Bug 1767603] Re: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel

2018-05-05 Thread Philip Taylor
ignore comment 3, i retested it, with kernel Linux deepthought 4.17.0-041700rc3-generic #201804300800 SMP Mon Apr 30 08:03:00 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux and the bug clearly still exists. My apologies. 317 root 20 0 172284 130324 3280 R 81.2 3.3 6:30.80 systemd-udevd

[Kernel-packages] [Bug 1767603] Re: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel

2018-05-05 Thread Philip Taylor
** Attachment added: "Screenshot at 2018-05-05 11-17-38.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603/+attachment/5134287/+files/Screenshot%20at%202018-05-05%2011-17-38.png ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Conf

[Kernel-packages] [Bug 1767603] Re: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel

2018-05-05 Thread Philip Taylor
It seems the kernel version Linux deepthought 4.17.0-041700rc3-generic #201804300800 SMP Mon Apr 30 08:03:00 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux solves the issue, normal cpu usage with bluetooth turned on and device connected, as identified in the below screenshots. ** Attachment added: "Sc

[Kernel-packages] [Bug 1767603] Re: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel

2018-04-29 Thread Philip Taylor
I can confirm, using said screenshot, i turned off bluetooth in my bios, and as top shows in the below screenshot the bug seems resolved, so the bug is confirmed. ** Attachment added: "Screenshot at 2018-04-29 08-57-39.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603/+attachme

[Kernel-packages] [Bug 1767603] [NEW] BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel

2018-04-28 Thread Philip Taylor
Public bug reported: I can confirm the following bug in kernel version 4.15 in bionic, https://bugzilla.kernel.org/show_bug.cgi?id=199035 I have thus booted into 4.13, and temporarily worked around the bug. If you need any further information please tell me. ** Affects: linux (Ubuntu) Impo