You are not logged in.
On my good old laptop the CPU runs hot since udev keeps failing and retrying to connect some USB device. The systemd-udevd process maxes out my processor at near 100%.
Here are some clues as to what device is problematic
$ udevadm monitor
KERNEL[2233.548315] bind /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
KERNEL[2233.550318] unbind /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
UDEV [2233.554589] bind /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
KERNEL[2233.584200] bind /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
KERNEL[2233.586308] unbind /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
UDEV [2233.587755] unbind /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
...
# lspci -vvs1a.0
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) (prog-if 00 [UHCI])
Subsystem: Dell 82801I (ICH9 Family) USB UHCI Controller
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 20
Region 4: I/O ports at 6f60 [size=32]
Capabilities: [50] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: uhci_hcd
# lsusb -t
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Application Specific Interface, Driver=, 12M
|__ Port 1: Dev 2, If 1, Class=Chip/SmartCard, Driver=, 12M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 12M
|__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=, 12M
|__ Port 3: Dev 5, If 3, Class=Application Specific Interface, Driver=, 12M
|__ Port 3: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 5, If 2, Class=Vendor Specific Class, Driver=, 12M
|__ Port 3: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
/sys/bus/usb/devices/3-1.2:1.0$ ls
authorized bInterfaceNumber bNumEndpoints power uevent
bAlternateSetting bInterfaceProtocol ep_81 subsystem
bInterfaceClass bInterfaceSubClass modalias supports_autosuspend
/sys/bus/usb/devices/3-1.2:1.0$ cat modalias
usb:v413Cp8162d0100dc00dsc00dp00ic03isc01ip02in00
Will I ever be able to tell which device is the cause of udev spamming bind/unbind-messages? How do I understand the seemingly varying ways of enumerating USB-devices?
thx in advance
Offline
I plugged a couple thumb drives into a USB hub:
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 12M
|__ Port 1: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 12M
|__ Port 3: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 12M
When I plugged in the first one, I saw messages from udevadm monitor containing this:
/devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2.1/6-2.1:1.0
When I plugged in the second one, I saw messages containing this:
/devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2.3/6-2.3:1.0
Based on that, I think the bit "X-Y.Z" ie refers to Bus:Port:Port so in your case the problem device (3-1.2) is
|__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=, 12M
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
post the output of lsusb without any parameters, that list should help to identify brand/model of the device at 3-1.2 .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
thanks Lone_Wolf and alphaniner
So then it would be my touchpad according to the output below? This bootup the device is numbered 12. The weird thing is that the devices (10-13) under bus 3 changes numbers every time I toggle the wifi-switch off and on. So, strange that the touchpad is sorted under devices that change enumeration when wifi is toggled.
Btw the touchpad is working fine, but I guess it could still be the thing causing the messages...
$ lsusb -t
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Application Specific Interface, Driver=, 12M
|__ Port 1: Dev 2, If 1, Class=Chip/SmartCard, Driver=, 12M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 10, If 0, Class=Hub, Driver=hub/3p, 12M
|__ Port 1: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 12, If 0, Class=Human Interface Device, Driver=, 12M
|__ Port 3: Dev 13, If 3, Class=Application Specific Interface, Driver=, 12M
|__ Port 3: Dev 13, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 13, If 2, Class=Vendor Specific Class, Driver=, 12M
|__ Port 3: Dev 13, If 0, Class=Wireless, Driver=btusb, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 013: ID 413c:8160 Dell Computer Corp. Wireless 365 Bluetooth
Bus 003 Device 012: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
Bus 003 Device 011: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
Bus 003 Device 010: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
# lsusb -vs3\:12
Bus 003 Device 012: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x413c Dell Computer Corp.
idProduct 0x8162 Integrated Touchpad [Synaptics]
bcdDevice 1.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 113
Report Descriptor: (length is 113)
Item(Global): Usage Page, data= [ 0x01 ] 1
Generic Desktop Controls
Item(Local ): Usage, data= [ 0x02 ] 2
Mouse
Item(Main ): Collection, data= [ 0x01 ] 1
Application
Item(Global): Report ID, data= [ 0x02 ] 2
Item(Local ): Usage, data= [ 0x01 ] 1
Pointer
Item(Main ): Collection, data= [ 0x00 ] 0
Physical
Item(Global): Usage Page, data= [ 0x09 ] 9
Buttons
Item(Local ): Usage Minimum, data= [ 0x01 ] 1
Button 1 (Primary)
Item(Local ): Usage Maximum, data= [ 0x03 ] 3
Button 3 (Tertiary)
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x01 ] 1
Item(Global): Report Size, data= [ 0x01 ] 1
Item(Global): Report Count, data= [ 0x03 ] 3
Item(Main ): Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Report Size, data= [ 0x05 ] 5
Item(Main ): Input, data= [ 0x01 ] 1
Constant Array Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Usage Page, data= [ 0x01 ] 1
Generic Desktop Controls
Item(Local ): Usage, data= [ 0x30 ] 48
Direction-X
Item(Local ): Usage, data= [ 0x31 ] 49
Direction-Y
Item(Global): Logical Minimum, data= [ 0x81 ] 129
Item(Global): Logical Maximum, data= [ 0x7f ] 127
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x02 ] 2
Item(Main ): Input, data= [ 0x06 ] 6
Data Variable Relative No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Main ): End Collection, data=none
Item(Main ): End Collection, data=none
Item(Global): Usage Page, data= [ 0x0c ] 12
Consumer
Item(Local ): Usage, data= [ 0x01 ] 1
Consumer Control
Item(Main ): Collection, data= [ 0x01 ] 1
Application
Item(Global): Report ID, data= [ 0x7f ] 127
Item(Global): Usage Page, data= [ 0x00 0xff ] 65280
(null)
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x03 ] 3
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
Item(Local ): Usage Minimum, data= [ 0x40 0xfc ] 64576
(null)
Item(Local ): Usage Maximum, data= [ 0x42 0xfc ] 64578
(null)
Item(Main ): Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report ID, data= [ 0x7e ] 126
Item(Global): Report Count, data= [ 0x1b ] 27
Item(Local ): Usage Minimum, data= [ 0x44 0xfc ] 64580
(null)
Item(Local ): Usage Maximum, data= [ 0x5e 0xfc ] 64606
(null)
Item(Main ): Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report ID, data= [ 0x7d ] 125
Item(Global): Report Size, data= [ 0x01 ] 1
Item(Global): Report Count, data= [ 0x0a ] 10
Item(Global): Logical Maximum, data= [ 0x01 ] 1
Item(Local ): Usage Minimum, data= [ 0x5f 0xfc ] 64607
(null)
Item(Local ): Usage Maximum, data= [ 0x68 0xfc ] 64616
(null)
Item(Main ): Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report Count, data= [ 0x06 ] 6
Item(Main ): Input, data= [ 0x01 ] 1
Constant Array Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Main ): End Collection, data=none
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 10
** UNRECOGNIZED: 1c ff 42 49 53 54 00 01 03 08 05 00 00 00 00 00 01 09 f4 01 02 0a f4 01 03 0b f4 01
Device Status: 0x0001
Self Powered
Offline
It does look like the touchpad is indeed involved.
All devices on bus 3 appear to be builtin, so you can't put them in other ports.
A few things to try :
- Disable touchpad in firmware (if possible...) to test if this stops the bind / unbind
- boot into multi-user.target to verify whether X / libinput / evdev are involved
- When did the issue start ? was there a systemd or kernel update shortly before that ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
A few things to try :
- Disable touchpad in firmware (if possible...) to test if this stops the bind / unbind
This did disable the touchpad for any use in X, but the binds/unbinds were still there when I checked in the terminal.
Edit: Here are the usb-listings when the touchpad has been disabled in BIOS.
$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 005: ID 413c:8160 Dell Computer Corp. Wireless 365 Bluetooth
Bus 003 Device 004: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
Bus 003 Device 003: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
$ lsusb -t
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Application Specific Interface, Driver=, 12M
|__ Port 1: Dev 2, If 1, Class=Chip/SmartCard, Driver=, 12M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 12M
|__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=, 12M
|__ Port 3: Dev 5, If 3, Class=Application Specific Interface, Driver=, 12M
|__ Port 3: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 5, If 2, Class=Vendor Specific Class, Driver=, 12M
|__ Port 3: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
- boot into multi-user.target to verify whether X / libinput / evdev are involved
systemd.unit=multi-user.target
Same problems also without X or display manager running.
- When did the issue start ? was there a systemd or kernel update shortly before that ?
No idea when it started unfortunately. I haven't used this laptop much lately, but was planning to start using it again.
Anyone have any other ideas abt what to do? I wanna use this comfy old laptop more but this issue needless to say ruins battery-time, besides creating heat and slowing the computer down.
Last edited by renegen (2018-06-07 17:33:43)
Offline
You might want to give powertop a try too, which might help narrow things down.
Edit: Moving thread to "Kernel & Hardware".
Last edited by x33a (2018-06-08 04:53:44)
Offline
The main question is why the device constantly rebinds.
This is either a software issue (cyclic udev rule, stupid power saving tool, ...) or hardware (loose contact, stuck key causing some event)
=> Run some life distro (grml, knoppix, ubuntu, ...)and check whether the problem exists w/ an entirely different software stack.
Offline
Hey and thanks for all the replies so far.
So, what I did was to try the latest Arch-liveUSB. No issues there.
Inspired by some other threads like for example this one I decided to see if the internal bluetooth was related to the issue - and it was. I did a new Arch-install on a separate partition, and I could install the full Bluez-stack without issues until I added bluez-hid2hci (which apparently adds a udev-rule to switch some devices automatically from hid to hci-mode). That's when the spamming of bind/unbind started again.
It seems my internal bluetooth is not handled correctly by the current bluez-stack. I decided to keep bluez-hid2hci and disable the internal bluetooth-device in BIOS. All is working well now, except I cannot use the internal bluetooth (my external USB-bluetooth works).
I also installed Windows 10 on a scrap partition, and no bluetooth-device was found by Windows at all. (This was before I disabled it in BIOS.) Maybe it's simply a lesser known device with no support on any OS?
Anyway, if anyone knows a more proper solution that allows me to get the internal bluetooth working, let me know.
Offline