Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

KeWaitForSingleObject

239 views
Skip to first unread message

SH Luk

unread,
Nov 25, 1999, 3:00:00 AM11/25/99
to
Hi All,

In my driver, I have to wait for the completion of IoCallDriver. I put
KeWaitForSingleObject right after IoCallDriver. For some reasons, there is a
timeout set in KeWaitForSingleObject. My understanding is that it will only
return 4 status. In fact, I found it only return STATUS_SUCCESS or
STATUS_TIMEOUT in my driver. However, it return -1 sometimes and it surely
cause problem in my driver. Besides, I have no idea about what is that means
and why did it happen. Do anybody know what is that "-1" means?

Thanks

SH

tim.perkins

unread,
Nov 26, 1999, 3:00:00 AM11/26/99
to
I read this in the Kernel mode discussion, (magically my news server resusitated
that news group for me)

Subject:
Status - 0xFFFFFFFF
Date:
Wed, 27 Oct 1999 18:26:28 GMT
From:
Prabhashankar <sha...@my-deja.com>
Organization:
Deja.com - Before you buy.
Newsgroups:
comp.os.ms-windows.programmer.nt.kernel-mode


Hi there,
In my USB driver, I use 'IoBuildDeviceIoControlRequest' to build an IRP
and call IoCallDriver (see BulkUsb_CallUSBD in Bulk_USB Sample, it's the
same). After this, I wait for the event to trigger. It works just fine,
but, some times the Wait (KeWaitForSingleObject) results in a status
code of 0xFFFFFFFF! After this, the whole system crashes. The stack
shows '_VWIN32_CloseVxDHandle'. Any Ideas? I thought I was corrupting
the stack some how, but, I am very sure that I am not...This happens
even if I cancel the IRP with 'IoCancelIrp'. By the way, when this
happens, the URB Status will be 0x40000001! There is no description of
this error code in USBDI.H. Any help will be appreciated...

Thanks
Prabhu

Subject:
Re: Status - 0xFFFFFFFF
Date:
Wed, 27 Oct 1999 12:19:39 -0700
From:
"Dennis Krueger" <kru...@halcyon.com>
Organization:
Smart Technology Enablers
Newsgroups:
comp.os.ms-windows.programmer.nt.kernel-mode
References:
1


From the symptoms you describe, it sounds like you are executing at an
elevated IRQL. In USB drivers, this usually results from calling WDM
functions from a VxD.

The -0xFFFFFFFF from the KeWait is an undocumented return code that
indicates the raised IRQL.

-- Dennis

SH Luk

unread,
Nov 29, 1999, 3:00:00 AM11/29/99
to
But I have checked it. The IRQL before and after KeWaitForSingleObject is
the same -- it is 0 or 1 which is PASSIVE_LEVEL or APC_LEVEL. It is
acceptable for KeWaitForSingleObject according to DDK. Any clue?

tim.perkins <tim.p...@s-s-g.com> wrote in message
news:383F23D9...@s-s-g.com...

SH Luk

unread,
Dec 1, 1999, 3:00:00 AM12/1/99
to

SH Luk

unread,
Dec 1, 1999, 3:00:00 AM12/1/99
to
But I have checked it. The IRQL before and after KeWaitForSingleObject is
the same -- it is 0 or 1 which is PASSIVE_LEVEL or APC_LEVEL. It is
acceptable for KeWaitForSingleObject according to DDK. Any clue?


SH Luk <sh...@stdhk.com> wrote in message
news:3844...@newsgate.imsbiz.com...

0 new messages