On 08/02/06, Georg Lohrer <[EMAIL PROTECTED]> wrote: > Hi folks, Hello,
> I'm running a Linux-kernel 2.6.13 Debian system with libusb-0.1.11 support. > For > getting access to my ReinerSCT pinpad reader I am using the ctapi provided by > the manufacturer and pcsc-lite-1.2.9-beta10. > If I startup pcscd: > > > pcscd --foreground --debug > > I get the familiar output showing: > > pcscdaemon.c:264:main() pcsc-lite 1.2.9-beta10 deamon ready > hotplug_lubusb.c:406:HPAddHotPluggable() Adding USB device:003:002 > readerfactory.c:1110:RFInitializeReader() Attempting to startup of REINER SCT > CyberJack pp_a (9309306538) 00 00. > readerfactory.c:952:RFBindFunctions) Loading IFD Handler 2.0 > IFDHCreateChannel: Lun0, Channel 2097152 > IFDHPresence: Lun 0 > > the output of IFDHPresence is a debug-output from REINER-SCT ctapi. > > If I now want to stop pcscd pressing Strg-C to use the "AraKiri"-behaviour, I > got: > > IFDHGetCapabilities: Lun 0, Tag 4014, Length -1210531548 This length is very suspect. The log line comes from the manufacturer driver. I don't know the application you are using by it looks like the application is calling SCardGetAttrib() with a strange length parameter. That may be the cause of the problem if the memory is then corrupted by the manufacturer driver. > What's ongoing there? Why will the system freeze? > As far as I can see in EHDestroyEventHandler() the EHStatusHandlerThread > should > be cancelled by setting dwLockId to 0xFFFF. The pthread_detach() > (SYS_ThreadDetach()) will be called successfully, but calling the > pthread_exit() (SYS_ThreadExit()) will result in holding the whole system. A user application should _never_ block the kernel. Can you also try with a newer kernel? Bye, -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
