Launchpad has imported 13 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=199035.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2018-03-06T21:09:45+00:00 mathieutournier wrote:
Created attachment 274593
dmesg
Hi,
I'm currently running ubuntu 18.04 with a 4.15 kernel and i can observe very high cpu usage to the systemd-udevd deamon.
removing the rule :
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"
Solved the high CPU usage eventhough my bluetooth card is not available
anymore (as not in hci mode)
It seems that the command hid2hci creates a bind/unbind loop in udev
that is looping trying to set the device in hci mode. (that what udevadm
monitor seems to show, looping from bind to unbind for the device)
I suspect a0085f2510e8976614ad8f766b209448b385492f introduced a
regression (i have not tried to revert it yet).
Please not that there also seem to be a bug in hid2hci.c from bluez l148 :
if (err == 0) {
err = -1;
errno = EALREADY;
}
Correcting this and recompile bluez desn't solve the issue as cpu usage remains very high.
Using a 4.13 kernel result in a normal CPU usage, this seems a
regression in 4.14.
Other people seems to have the same issue, here is a bug report related to this :
https://dev.solus-project.com/T5224
Thanks a lot for your support,
Mathieu Tournier
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/0
------------------------------------------------------------------------
On 2018-05-04T05:57:10+00:00 boro wrote:
I have the very same problem using the same distro (Ubuntu 18.04,
64-bit) on Dell Latitude E5400 laptop. Disabling BT from BIOS or
removing the aforementioned rule solves the problem but leaves BT
unusable.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/1
------------------------------------------------------------------------
On 2018-05-09T23:02:06+00:00 lucent wrote:
Bus 001 Device 009: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 004: ID 0a5c:0000 Broadcom Corp.
Linux zontar 4.16.0-1-amd64 #1 SMP Debian 4.16.5-1 (2018-04-29) x86_64
GNU/Linux
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
...repeating...
15632 root 20 0 233136 186656 2664 R 94.1% 4.7% 62:14.67 systemd-udevd
16222 root 20 0 88252 2432 1888 R 35.3% 0.1% 25:21.87 systemd-udevd
Looks like same problem affects this Dell Precision M6500 laptop.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/2
------------------------------------------------------------------------
On 2018-05-20T07:57:41+00:00 f.dittmer wrote:
I observed the high cpu usage after upgrading from udev-233 to udev-236/udev-238 on Gentoo Linux. Downgrading back to udev-233 lets me use newer kernels (currently running 4.15.18) without any problems.
Using DELL Latitude E6400 from 2009, with same Broadcom Bluetooth module as mentioned above.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/3
------------------------------------------------------------------------
On 2018-06-13T16:50:40+00:00 rickfharris wrote:
As per https://patchwork.kernel.org/patch/10384111/ editing
97-hid2hci.rules as follows works around the new uevents added to the
kernel in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65
-ACTION=="remove", GOTO="hid2hci_end"
+ACTION!="add", GOTO="hid2hci_end"
Bluetooth now works with kernels above and below 4.14.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/4
------------------------------------------------------------------------
On 2018-06-14T00:32:13+00:00 rickfharris wrote:
Scratch that last comment, on further testing found I was booted into
incorrect kernel :/
Editing of 97-hid2hci.rules is not a solution.
Only surefire way of getting bluetooth back and working with kernels
>=4.14, was to revert the bogus kernel commit that added the bind/unbind
uevents.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/5
------------------------------------------------------------------------
On 2018-06-14T00:33:52+00:00 rickfharris wrote:
Created attachment 276537
revert-bind_unbind-uevents.patch
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/6
------------------------------------------------------------------------
On 2018-08-23T15:22:32+00:00 sobik.szymon wrote:
I use ubuntu 18.04 with 4.15 kernel
I have hit the same problem, but with synaptics touchpad.
I have bisected 4.13-4.14 and the problem was in commit
1455cf8dbfd06aa7651dcfccbadb7a093944ca65 (as in the attached patch)
I am unable to use USB bus because udev is bogged down with these
bind/unbind events
```
UDEV [496.168312] bind /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb)
KERNEL[496.175932] bind /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb)
KERNEL[496.176947] unbind /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb)
UDEV [496.177602] unbind /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb)
KERNEL[496.185259] bind /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb)
KERNEL[496.185479] unbind /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb)
UDEV [496.186342] bind /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb)
KERNEL[496.196813] bind /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb)
KERNEL[496.197103] unbind /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb)
UDEV [496.197501] unbind /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb)
KERNEL[496.207283] bind /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb)
```
```
> cat /sys/bus/usb/devices/2-1.4/2-1.4.2/id*
8162
413c
```
```
> lsusb -d 413c:8162
Bus 002 Device 006: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
```
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/11
------------------------------------------------------------------------
On 2018-09-13T05:50:19+00:00 ysg wrote:
I also observed in my Dell laptop similar to Szymon that it relates to
Touchpad.
My workarounds-
Soon after booting, stopping and starting systed-udev eliminates all bind and unbind problems and response drastically improves. I used the following commands in sequence-
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
My understanding-
Before all hardware is discovered properly, bind/unbind start executing when no procedures are available and does not get reinitialized. After stopping and starting, it gets all the procedures in place. Probably, it is booting sequence problem.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/13
------------------------------------------------------------------------
On 2018-10-18T17:53:33+00:00 brunofcosouza wrote:
(In reply to Y S Gupta from comment #8)
Same here. I used the commands from Szymon to find out what was going on and got the Synaptics Touchpad, too.
The workaround by Y S Gupta works like a charm. Put it in a startup
script and everything is ok. THANK YOU!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/14
------------------------------------------------------------------------
On 2018-12-22T17:54:47+00:00 mathieutournier wrote:
Command from Y S Gupta fixed to high cpu load for me.
As this is just a workaround. I suppose this bug should remain open.
Thanks for this, i can now reuse my bluetooth card.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/15
------------------------------------------------------------------------
On 2019-01-08T18:42:34+00:00 jgwphd wrote:
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!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/16
------------------------------------------------------------------------
On 2019-01-08T19:38:50+00:00 jgwphd wrote:
BTW, add to my previous comment an additional symptom: sometimes my
system will "appear to hang" entirely during boot (but it will power
down normally by briefly touching the power off button when it "looks
like" it is stuck).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/17
** Changed in: linux
Status: Unknown => Confirmed
** Changed in: linux
Importance: Unknown => High
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1788018
Title:
udevd keeps binding and unbinding some usb device und uses all cpu
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Incomplete
Bug description:
It first appeared when I upgraded ubuntu studio to 18.04
udevd started to use all available cpu.
now I'm running ubuntu desktop from a usb key and it's still the same
udevadm monitor returns:
KERNEL[2512.539491] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
UDEV [2512.540201] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.566574] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.566866] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
UDEV [2512.567499] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.594050] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.594310] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
UDEV [2512.596510] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.620736] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[2512.624606] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
UDEV [2512.634706] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
...
WORKAROUND: Remove file:
/lib/udev/rules.d/97-hid2hci.rules
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: udev 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
CustomUdevRuleFiles: 70-snap.core.rules
Date: Mon Aug 20 18:54:48 2018
ExecutablePath: /lib/systemd/systemd-udevd
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Vostro 3300
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/10/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 07JC8T
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 3300
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1788018/+subscriptions
Комментариев нет:
Отправить комментарий