Le 24/03/2016 18:56, Ludovic Rousseau a écrit :
Le 15/03/2016 19:14, Ludovic Rousseau a écrit :
Maybe enabling libusb debug would help. I will try to document how to do that
easily.
Philippe, Gustavo, Eric, can you do:
$ sudo LIBUSB_DEBUG=99 pcscd -dfaT | tee log.txt
generate the problem and
Le 15/03/2016 19:14, Ludovic Rousseau a écrit :
Maybe enabling libusb debug would help. I will try to document how to
do that easily.
Philippe, Gustavo, Eric, can you do:
$ sudo LIBUSB_DEBUG=99 pcscd -dfaT | tee log.txt
generate the problem and send me the created log.txt file?
Thanks
--
Dr.
Hello,
For an unknown reason this email is not visible on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812087
Sending it again.
Le 15/03/2016 19:14, Ludovic Rousseau a écrit :
On Mon, 7 Mar 2016 21:14:48 +0100 Philippe Teuwen
wrote:
>
>
> On 03/07/2016 07:34 PM, Ludovic Rousseau wrote
On Mon, 7 Mar 2016 21:14:48 +0100 Philippe Teuwen wrote:
>
>
> 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].r
Package: pcscd
Version: 1.8.15-1
Followup-For: Bug #812087
Hello
I just want to provide more information about the issue, I have an
SmartCard reader (ok, it is usb internally) and a g10 smartcard.
I can reproduce the issue plugging my phone as MTP device.
If I had my phone connected while I star
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
Le 07/03/2016 10:21, Philippe Teuwen a écrit :
I recompiled libusb with debug symbols:
Normal CPU:
Thread 5 (Thread 0x7f0238fcb700 (LWP 24364)):
#0 0x7f02394dfb6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x7f0238fdbafc in poll (__timeout=-1, __nfds=2,
__fds=0x7f0238fcae
I forgot to say, removing TEMP_FAILURE_RETRY() didn't change anything.
I recompiled libusb with debug symbols:
Normal CPU:
Thread 5 (Thread 0x7f0238fcb700 (LWP 24364)):
#0 0x7f02394dfb6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x7f0238fdbafc in poll (__timeout=-1, __nfds=2,
__fds=0x7f0238fcaee0)
at /usr/include/x86_64-linux-gnu/bits/pol
On Sun, 6 Mar 2016 23:10:07 +0100 Philippe Teuwen wrote:
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 trigg
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
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
On Thu, 3 Mar 2016 09:30:36 +0100 Philippe Teuwen wrote:
Hi Ludovic,
Hello Philippe,
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 also suspect a bug in libudev, no
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
Hello,
I got no news from my latest email.
Do you still have the 100% CPU load for pcscd?
Can you help me fix the problem?
Thanks
Le 25/01/2016 17:33, Ludovic Rousseau a écrit :
Hello Alexander and Eric,
Le 25/01/2016 01:13, Alexander Mikhailian a écrit :
Package: pcscd
Version: 1.8.15-1
Fo
Hello Alexander and Eric,
Le 25/01/2016 01:13, Alexander Mikhailian a écrit :
Package: pcscd
Version: 1.8.15-1
Followup-For: Bug #812087
Dear Maintainer,
I have the same problem with pcscd, and I did not even have to insert a
USB mass storage device, when I plug my notebook into the dock stati
Package: pcscd
Version: 1.8.15-1
Followup-For: Bug #812087
Dear Maintainer,
I have the same problem with pcscd, and I did not even have to insert a
USB mass storage device, when I plug my notebook into the dock station,
fans go off like mad and pcscd takes on CPU cycles.
-- System Information:
D
>> You can identify a process using PC/SC using:
>> $ sudo fuser /usr/lib/x86_64-linux-gnu/libpcsclite.so.1
> sudo fuser /usr/lib/x86_64-linux-gnu/libpcsclite.so.1
> [sudo] password for ceva6380:
> /usr/lib/x86_64-linux-gnu/libpcsclite.so.1.0.0: 14662m
> 19 r-x-ceva6380:~->ps ax | grep 14662
> 1
Le 22/01/2016 16:05, eric2.vale...@orange.com a écrit :
On 01/22/2016 03:52 PM, Ludovic Rousseau wrote:
Le 22/01/2016 15:18, eric2.vale...@orange.com a écrit :
On 01/22/2016 03:06 PM, Ludovic Rousseau wrote:
Le 22/01/2016 13:11, eric2.vale...@orange.com a écrit :
On 01/20/2016 03:07 PM, Ludov
On 01/22/2016 03:52 PM, Ludovic
Rousseau wrote:
Le
22/01/2016 15:18, eric2.vale...@orange.com a écrit :
On 01/22/2016 03:06 PM, Ludovic Rousseau
wrote:
Le 22/01/2016 13:11,
eric2.vale...@orange.com a écrit :
Le 22/01/2016 15:18, eric2.vale...@orange.com a écrit :
On 01/22/2016 03:06 PM, Ludovic Rousseau wrote:
Le 22/01/2016 13:11, eric2.vale...@orange.com a écrit :
On 01/20/2016 03:07 PM, Ludovic Rousseau wrote:
It does not look like the problem is the Broadcom reader.
Can you generate a log as
On 01/22/2016 03:06 PM, Ludovic Rousseau wrote:
Le 22/01/2016 13:11, eric2.vale...@orange.com a écrit :
On 01/20/2016 03:07 PM, Ludovic Rousseau wrote:
It does not look like the problem is the Broadcom reader.
Can you generate a log as documented in
https://pcsclite.alioth.debian.org/pcsclit
Le 22/01/2016 13:11, eric2.vale...@orange.com a écrit :
On 01/20/2016 03:07 PM, Ludovic Rousseau wrote:
It does not look like the problem is the Broadcom reader.
Can you generate a log as documented in
https://pcsclite.alioth.debian.org/pcsclite.html#support ?
Start the log and then connect y
On 01/22/2016 01:11 PM, VALETTE Eric
OLNC/OLPS wrote:
On
01/20/2016 03:07 PM, Ludovic Rousseau wrote:
It does not look like the problem is the Broadcom reader.
Can you generate a log as documented in
ht
On 01/20/2016 03:07 PM, Ludovic Rousseau wrote:
Le 20/01/2016 14:02, eric2.vale...@orange.com a écrit :
It does not look like the problem is the Broadcom reader.
Can you generate a log as documented in
https://pcsclite.alioth.debian.org/pcsclite.html#support ?
Start the log and then connect yo
Le 20/01/2016 14:02, eric2.vale...@orange.com a écrit :
Note that in the laptop there is a build in broadcom credit card format crypto
key reader (that you see in the log), but I do not use it although for testing
purpose I have enabled the driver. But the bug is only if I insert a USB key.
On 01/20/2016 01:31 PM, Ludovic Rousseau wrote:
Le 20/01/2016 13:03, Eric Valette a écrit :
Package: pcscd
Version: 1.8.15-1
Severity: critical
Justification: breaks unrelated software
Twice in two days, I noticed my laptop fan was going carsy allthough I
was only doing many mail activity.
Twi
Le 20/01/2016 13:03, Eric Valette a écrit :
Package: pcscd
Version: 1.8.15-1
Severity: critical
Justification: breaks unrelated software
Twice in two days, I noticed my laptop fan was going carsy allthough I
was only doing many mail activity.
Twice I found that pcscd was eating a complete CPU a
Package: pcscd
Version: 1.8.15-1
Severity: critical
Justification: breaks unrelated software
Twice in two days, I noticed my laptop fan was going carsy allthough I
was only doing many mail activity.
Twice I found that pcscd was eating a complete CPU and remembered that
each time I had inserted a
29 matches
Mail list logo
