Le 02/08/13 11:39, Eugen Dedu a écrit :
Ok, I see.  Right after a suspend/resume, pcscd goes to 100% CPU.  So this is 
related to suspend/resume.

The output generated after the suspend/resume is:

12796601 hotplug_libudev.c:587:HPEstablishUSBNotifications() Device removed
00008392 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 
0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001
00019374 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 
0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001
[...]
00000802 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 
0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001
00000529 hotplug_libudev.c:587:HPEstablishUSBNotifications() Device removed
00004667 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 
0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001
[..]
00009838 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 
0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001
00009786 hotplug_libudev.c:587:HPEstablishUSBNotifications() Device removed
00002195 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 
0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001
[...]
00001705 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 
0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001
00000460 hotplug_libudev.c:587:HPEstablishUSBNotifications() Device removed
00015193 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 
0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001
[similar lines]


I setup a laptop (old MacBook Pro) using Debian stable (plus pcsc-lite from 
unstable) and I can't reproduce the problem.
Suspend/resume works great on this machine and pcscd is still working correctly 
after the resume.

I then upgraded the system to Debian testing and pcscd is still working 
correctly.

So I can't reproduce your bug for now.

Bye

--
 Dr. Ludovic Rousseau


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to