[Bug 199035] BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel

[bugzilla-daemon@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=199035

John (jgwphd@yahoo.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jgwphd@yahoo.com

--- Comment #11 from John (jgwphd@yahoo.com) ---
When I boot up every day without exception, my machine starts up with one of
the CPU cores running at 100%. I see lots of posts on other forums (Unbuntu 
etc) going back over a year or more blaming touchpads or nvidia or WiFi. Some
even say they can't use their thumb drive if it isn't plugged in when they
boot. The problem also mimics a defective thumb drive where you plug it in and
Ubuntu doesn't see it (because systemd-udevd doesn't have the cycles to process
the newly plugged in USB device). Losing one core makes my machine slower but
not too noticeably so. I do see much longer boot times and sometime it will
hang entirely during boot. I assume a single core or dual core machine will be
drastically slowed down or even unusable. When I search I find other non-ubuntu
os's complaining about similar problems.

I have 18.10 running on my Dell studio XPS with an AMD® Phenom(tm) ii x4 945
processor × 4 and AMD® Juniper graphics. It's a quad-core 64 bit machine. I
have wireless mouse and keyboard for Logitech. I have a pretty vanilla set-up.
I DO NOT have a touchpad or nvidia or WiFi!

I can verify that the problem can be managed by stopping and starting
systemd-udevd. I used the following commands, suggested in this bug report, in
sequence in the terminal which corrects the problem until I boot again. 

sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket
systemd-udevd-control.socket

sudo systemctl start systemd-udevd systemd-udevd-kernel.socket
systemd-udevd-control.socket

Also the problem will "sometimes" re-appear by plugging in a thumb drive! 

This is a serious kernel problem and can manifest its presence in a number of
ways depending on your hardware configuration. 

This is a very very very annoying problem will someone PLEASE fix it soon!
...did I mention that this is a serious problem impacting many people!

-- 
You are receiving this mail because:
You are the assignee for the bug.