2011/11/21 Eduard Rysavy <[email protected]>: >> Please try to update libusb. See [1]. >> The "latest" version should be in the libusb-stuge branch [2]. > > I installed the updated (from 1.0.8 to Peter Stuge's current snapshot > version), checked that libccid.so is linked to the newly updated library, no > improvement. > But calling pcscd as "chrt -f 10 pcscd" works reliably.
It looks like a scheduling issue. You are the first one to report such a problem. Do you also have the problem if you run pcscd in the foreground using "pcscd -fd" If yes then send me a trace as explained in [1] I propose to: - try with a different Linux kernel - build libusb in debug mode: ./configure --enable-debug-log and see what is happening > Since the two other reader drivers I have (the one provided by Cherry for the > same reader, the other for Reiner-SCT's cyberjack) don't show this behavior, I > wonder if this is really related to the USB code. Do you know if the two other (working) drivers use libusb-1.0 or libusb-0.1 or something else? > Is it possible that spawned subprocesses interfere with each other and have to > be completed in a certain order? Maybe. [1] http://pcsclite.alioth.debian.org/pcsclite.html#support -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
