[wdmaudiodev] Re: Using KeAcquireInStackQueuedSpinLock
- From: "Daniel E. Germann" <deg@xxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Tue, 3 Mar 2009 08:05:04 -0600
Hi, KS.
What does the output from "analyze -v" say?
Are you sure the contents of the KSPIN_LOCK structure aren't getting
overwritten between the call to KeInitializeSpinLock() and the call to
KeAcquireInStackQueuedSpinLock()? If the bugcheck is happening inside
KeAcquireInStackQueuedSpinLock(), the only thing that makes sense is that
something is wrong with one of the parameters. And the only parameter
that's initialized is the KSPIN_LOCK.
Try turning on Driver Verifier for your driver. It should catch problems
like that. And when it does, "analyze -v" will tell you what's going on.
http://support.microsoft.com/kb/244617
-Dan
----- Original Message -----
From: KS <wakeup1504@xxxxxxxxx>
Subject: [wdmaudiodev] Re: Using KeAcquireInStackQueuedSpinLock
Date: Tue, 3 Mar 2009 00:21:39 +0800
Hi Dan,
I'm sure the bugcheck happen in the call as I've tried to step into the
code
using WinDbg and the problem occurs while I'm inside the call.
As for the KSPIN_LOCK structure and KLOCK_QUEUE_HANDLE, I've tried
declaring
the spin lock in global non-paged memory with the queue handle on the
stack,
and also both in global non-paged memory, but the results seems the same.
Thanks for your advise.
KS
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
Other related posts:
