Greetings, USB gurus.
I've got a working "classic" Mac OS USB driver in Mac OS 9.2.2 that
uses one USBPB structure and completion proc to do continuous
background reads from my device's data pipe that occasionally kicks
off another to light the device's LED via the control pipe then
issue USBDelay calls polling an activity flag so it can turn the LED
off again. Its all working well but every so often the USB Log will
get filled with an error repeated over and over, here's a sample:
345.243: [ 0]: USL - processDelayQ count gone negative,
breaking 3
345.244: [ 0]: USL - processDelayQ count gone negative,
breaking 3
345.246: [ 0]: USL - processDelayQ count gone negative,
breaking 3
I haven't been able to catch the exact moment when they start in the
logs but this could be related to unplugging and re-plugging the
device. I'm careful not to reuse USBPB structures and my finalize
routine calls USBAbortPipeByReference on both my data and control
pipes. Also, to hopefully ensure that the USBDelay call would get
aborted in finalize I set its usbReference field to the control
pipe. Not sure if this is necessary or particularly helpful but I'm
guessing this error is somehow related to a USBDelay call.
Anyone have any ideas what I might be doing wrong to cause this?
Thanks.
-----
Dave Warker <email@hidden>
http://warker.com
_______________________________________________
usb mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/usb
Do not post admin requests to the list. They will be ignored.
