2012/6/12 Umberto Rustichelli aka Ubi <[email protected]>:
>
> Dear developers,
> I have an issue with pcscd / pcsc-lite which is quite puzzling (for me), it
> may even be related with hardware/USB but I cannot guess why.
>
> For a number of reasons, I'm using a very old version of pcscd (1.5.3),
> modified to handle a large number of readers (I just changed the proper
> #define's here and there).
> I understand that this is quite an extreme situation, so I do not expect
> anybody to have tried it, just I hope that you have any clue for me.
>
> The problem is that this trivial hack worked fine on a couple of server
> models for some time, but miserably fails on a Dell R410.
> I'm puzzled because we use the same operating system (Red Hat RHEL 5.4),
> same kernel (Linux 2.6.18-164.10.1.el5 #1 SMP Wed Dec 30 18:35:37 EST 2009
> i686 i686 i386 GNU/Linux) and the hardware is definitely similar -almost
> identical- to the R610 which never showed the issue (we also placed an R610
> processor on the R410 board to rule out that variable: Xeon E5620 vs Xeon
> E5607, the latter missing HT), also having 4GB RAM each (this to rule out
> any relationship with the quantity of RAM dedicated to the thread structures
> in the kernel).
> The set of recompiled software is the same; the smart card readers are ACS
> ACR38 SmartCard Reader and there is a 2-level cascade of USB hubs (server -
> hub - hubs - smart card readers).
>
> The point is that, on the R410 only, I come to this error (not on the R610):
>
> Jun  5 15:43:15 pes-app-blank-01 pcscd:
> winscard_svc.c:106:CreateContextThread() SYS_ThreadCreate failed: Cannot
> allocate memory
> Jun  5 15:43:15 pes-app-blank-01 pcscd: pcscdaemon.c:151:SVCServiceRunLoop()
> Problem during the context thread creation
>
> (another notice: the error is produced by the function pthread_create,
> almost certainly the glibc produces the ENOMEM error code but it should be
> EAGAIN, this is a known glibc issue).
>
> Also, on the R410 pcscd seems to use a lot more threads to do the same job
> (3-4 times the number of threads of the R610), tht is presumably why it runs
> out of ammo.

It is VERY strange to have more threads on the R410 than on the R610
for the same task with the same software.

Either you do not use the same pcsc-lite on both machines or you do
not use the same libC/thread library.

Bye

PS: it may be a good idea to upgrade pcsc-lite.

-- 
 Dr. Ludovic Rousseau

_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to