marco-c
commented
8 years ago Can you comment more on the reproducibility? Is this happening every boot? When you plug in a USB device? After some apt updates?
As far as I can tell, it is intermittent. It's unrelated to USB devices (I reproduced it once without any USB device plugged-in, another time with a USB mouse). The regression started after I updated to 16.10, so it's really hard to tell if a specific package is at fault.
Share the output of # lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
Bus 003 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 003 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
Bus 003 Device 007: ID 0765:5010 X-Rite, Inc.
Bus 003 Device 006: ID 5986:026a Acer, Inc
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubShare output of # dmesg
I've currently uninstalled fwupd as a workaround. Do you want me to send you the dmesg output after I reinstall it and while I run into the problem, or does any output work?
Make a copy of all files in /var/lib/app-info/yaml/
A current stack trace to figure out where fwupd is spinning while using 100% CPU
Will do after I run into the problem again.
superm1
Burusutazu
hughsie
robert-ancell
waelbentaleb
@marco-c:
Will need some details to debug this further.
# lsusb# dmesg