Le 24/11/2013 20:37, Ludovic Rousseau a écrit :
>> I would like to inform you that I do not have this bug anymore. It
>> seems that it got fixed about 2 months ago.
>
> Good to know.
> I have not changed anything in pcsc-lite to fix this. So it has been
> fixed in another package like libudev or
Le 24/11/2013 19:54, Eugen Dedu a écrit :
I would like to inform you that I do not have this bug anymore. It seems that
it got fixed about 2 months ago.
Good to know.
I have not changed anything in pcsc-lite to fix this. So it has been fixed in
another package like libudev or the Linux kerne
I would like to inform you that I do not have this bug anymore. It
seems that it got fixed about 2 months ago.
--
Eugen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Le 26/09/2013 18:36, Ludovic Rousseau a écrit :
>>> You do:
>>> 1. Switch off wireless (using the hardware button)
>>> 2. Suspend
>>> 3. Resume
>>> 4. Switch on wireless
>>>
>>> Does pcscd uses 100% CPU at this step?
>>>
>>> Then you do:
>>> 5. switch off radio
>>> you get 4 "Device remov
Le 25/09/13 19:53, Stéphane Glondu a écrit :
Le 25/09/2013 17:54, Ludovic Rousseau a écrit :
You do:
1. Switch off wireless (using the hardware button)
2. Suspend
3. Resume
4. Switch on wireless
Does pcscd uses 100% CPU at this step?
Then you do:
5. switch off radio
you get 4 "Device
Le 25/09/2013 17:54, Ludovic Rousseau a écrit :
> You do:
> 1. Switch off wireless (using the hardware button)
> 2. Suspend
> 3. Resume
> 4. Switch on wireless
>
> Does pcscd uses 100% CPU at this step?
>
> Then you do:
> 5. switch off radio
> you get 4 "Device removed" messages from pcscd a
Le 25/09/13 17:00, Stéphane Glondu a écrit :
Le 24/09/2013 17:49, Ludovic Rousseau a écrit :
After resume, I get:
[...]
Then after a while, I get:
[...]
Actually, the "after a while" part corresponds to me switching off
radio and doesn't seem to happen by itself. And only 4 "Device removed
Le 24/09/2013 17:49, Ludovic Rousseau a écrit :
>> After resume, I get:
>>> [...]
>> Then after a while, I get:
>>> [...]
Actually, the "after a while" part corresponds to me switching off
radio and doesn't seem to happen by itself. And only 4 "Device removed"
events occur (no loop in output). I
Le 24/09/13 12:43, Stéphane Glondu a écrit :
I am experiencing the same bug.
My computer is a Dell Latitude E6220. I can reliably reproduce the bug
with the following steps:
1. Switch off wireless (using the hardware button)
2. Suspend
3. Resume
4. Switch on wireless
Great. At least w
I am experiencing the same bug.
My computer is a Dell Latitude E6220. I can reliably reproduce the bug
with the following steps:
1. Switch off wireless (using the hardware button)
2. Suspend
3. Resume
4. Switch on wireless
Le 02/08/2013 10:56, Ludovic Rousseau a écrit :
> Can you:
> 1. run p
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
8392 hotplug_libude
severity 718473 normal
summary 718473 pcscd: 100% CPU usage in hotplug_libudev.c after suspend/resume
thank
Le 02/08/13 12:03, Eugen Dedu a écrit :
On 02/08/13 11:58, Ludovic Rousseau wrote:
Thanks. It may be a libudev bug. Or a wrong way pcscd uses it.
I do not have a laptop to test suspend/r
On 02/08/13 11:58, Ludovic Rousseau wrote:
Thanks. It may be a libudev bug. Or a wrong way pcscd uses it.
I do not have a laptop to test suspend/resume. So it may be a bit
complex to debug.
You can install systemd so that pcscd is started only when needed. So if
you do not use pcscd at the suspe
Le 02/08/13 11:39, Eugen Dedu a écrit :
On 02/08/13 11:20, Ludovic Rousseau wrote:
Le 02/08/13 11:03, Eugen Dedu a écrit :
On 02/08/13 10:56, Ludovic Rousseau wrote:
Can you:
1. run pcscd inside gdb
I have a problem here:
(gdb) run
Starting program: /usr/sbin/pcscd
warning: Could not load
On 02/08/13 11:20, Ludovic Rousseau wrote:
Le 02/08/13 11:03, Eugen Dedu a écrit :
On 02/08/13 10:56, Ludovic Rousseau wrote:
Can you:
1. run pcscd inside gdb
I have a problem here:
(gdb) run
Starting program: /usr/sbin/pcscd
warning: Could not load shared library symbols for linux-vdso.so.
On 02/08/13 11:20, Ludovic Rousseau wrote:
Le 02/08/13 11:03, Eugen Dedu a écrit :
On 02/08/13 10:56, Ludovic Rousseau wrote:
Note also the following output generated a few days ago:
I see a seg fault at exit but no infinite loop in the log. That is not
the same bug.
Can you reproduce the 100
Le 02/08/13 11:03, Eugen Dedu a écrit :
On 02/08/13 10:56, Ludovic Rousseau wrote:
Can you:
1. run pcscd inside gdb
I have a problem here:
(gdb) run
Starting program: /usr/sbin/pcscd
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "s
On 02/08/13 10:56, Ludovic Rousseau wrote:
Le 01/08/13 07:39, Eugen Dedu a écrit :
Subject: pcscd: 100% CPU usage
Package: pcscd
Version: 1.8.8-3
Severity: grave
Dear Maintainer,
Hello,
Since a few weeks, pcscd has been using 100% CPU, as shown by 'top':
PID USER PR NIVIRTR
Le 01/08/13 07:39, Eugen Dedu a écrit :
Subject: pcscd: 100% CPU usage
Package: pcscd
Version: 1.8.8-3
Severity: grave
Dear Maintainer,
Hello,
Since a few weeks, pcscd has been using 100% CPU, as shown by 'top':
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2
Subject: pcscd: 100% CPU usage
Package: pcscd
Version: 1.8.8-3
Severity: grave
Dear Maintainer,
Since a few weeks, pcscd has been using 100% CPU, as shown by 'top':
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2132 root 20 0 312348 5972984 S 99.7 0
20 matches
Mail list logo
