Re: Usb stack and STATUS_TIMEOUT by KeWaitForSingleObject - IRP hang
- From: Slavo Tomascik <ssutaz@xxxxxxxxx>
- Date: Mon, 26 Sep 2005 00:24:38 +0200
Doron Holan [MS] wrote:
after you call IoCancelIrp, you MUST infinitely wait for the irp to come back. IoBuildDeviceIoControlRequest will create an irp that is tied to the calling thread, so the calling thread must exist when the irp completes. this would be the cause for your code to sometimes bugcheck after IoCancelIrp.
d
Sorry, I know about this. It's only for test purposes (I forgot to correct this befor I sent it), and as I wrote in previous mail - "As result of hang IRP ...". The Main problem is hanging (deadlocking) IRP in lower USB stack drivers.
Slavo Tomascik .
- References:
- Re: Usb stack and STATUS_TIMEOUT by KeWaitForSingleObject - IRP hang
- From: Doron Holan [MS]
- Re: Usb stack and STATUS_TIMEOUT by KeWaitForSingleObject - IRP hang
- Prev by Date: Re: How to reboot the computer on the driver???
- Next by Date: A question about mirror driver
- Previous by thread: Re: Usb stack and STATUS_TIMEOUT by KeWaitForSingleObject - IRP hang
- Next by thread: Re: MiniportHandleInterrupt not queued.
- Index(es):
Relevant Pages
|