Bug#812087: [pcscd]

2016-03-07 Thread Philippe Teuwen
On 03/07/2016 07:34 PM, Ludovic Rousseau wrote: > printf("fds: %d %d\n", fds[0].revents, fds[1].revents); fds: 0 1 always I also printed udev_dev from udev_monitor_receive_device() it's always null So we get fds[1].revents but don't get anything from udev_monitor_receive_device() so it's loopi

Bug#812087: [pcscd]

2016-03-07 Thread Philippe Teuwen
I forgot to say, removing TEMP_FAILURE_RETRY() didn't change anything.

Bug#812087: [pcscd]

2016-03-07 Thread Philippe Teuwen
bi_mutex_static_unlock(&linux_hotplug_lock); } } usbi_dbg("udev event thread exiting"); I added error msgs in the loop. When 100% CPU, the poll() is non-blocking and the loop becomes a busy loop. On 03/06/2016 11:49 PM, Philippe Teuwen wrote: > #0 0x7f196a6cabdd in recvmsg () at ..

Bug#812087: [pcscd]

2016-03-06 Thread Philippe Teuwen
Here are some backtraces Normal CPU usage: Thread 5 (Thread 0x7f6365c82700 (LWP 30482)): #0 0x7f6366196b6d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f6365c92b3c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x7f6366462284 in start_thread (arg=0x7f6365c8270

Bug#812087: [pcscd]

2016-03-06 Thread Philippe Teuwen
Mmm activating libudev debug didn't bring much I think. I attached one log with LIBUSB_DEBUG=99 and one with recompiled pcscd with udev debug support. For both I just ran pcscd with the yubikey plugged in then plugged a USB hub that triggered the CPU to 100% libccid1.4.22-1 libusb-1.0-0

Bug#812087: [pcscd]

2016-03-03 Thread Philippe Teuwen
Hi Ludovic, I'm getting the same problem with my Debian Testing. I'll try to generate more logs related to libusb as explained in the bug thread but here are some things I noticed: I've a Yubikey Neo-n plugged constantly. When the 100% problem arises, nothing special in pcscd logs, even with -f

Bug#619701: Some more info... or not

2011-03-26 Thread Philippe Teuwen
Hi, I was also previously impacted by bug #616372 which I've locally solved by simply rebuilding version 0.7.44+dfsg-2 from sources (bzr). BTW this also solved #609705 Now it got being upgraded to 0.7.50+dfsg-1 and... segfault too. So... I tried again to rebuild, now version 0.7.50+dfsg-1, from s

Bug#440140: Current version broken ("can't find message"), please take new upstream

2007-08-29 Thread Philippe Teuwen
Package: fetchyahoo Version: 2.10.9 Severity: grave Hello, Since a few days fetchyahoo failed with "can't find message" >From upstream there is now: v2.11.0 08/28/07 * fix "can't find message" error with new Yahoo internals * replace html character entities in msg summaries Please integrate it a