What does it mean this assert ?

On WXPSP1 Checked/debug build I met assert:
Assertion failed: IopmDiffTableEntries < MaxIopmTableEntries
Source file: d:\xpsp1\base\hals\halx86\i386\xxbiosc.c

This assert is invoked after calling NdisAcquireSpinLock() in my driver.
What does it mean this assert message ?

Peter

"Peter" <> wrote in message
news:...
> On WXPSP1 Checked/debug build I met assert:
> Assertion failed: IopmDiffTableEntries < MaxIopmTableEntries
> Source file: d:\xpsp1\base\hals\halx86\i386\xxbiosc.c
>
> This assert is invoked after calling NdisAcquireSpinLock() in my driver.
> What does it mean this assert message ?

It has to do with setting the I/O privilege mask, which isn't even vaguely
related to what you're doing. You might not be passing the address of the
spinlock to NASL properly. Also, what does the stack trace look like?

-Brian

Brian Catlin, Sannas Consulting 310-944-9492
Windows Network, Video, WDM Device Driver Training & Consulting
See WWW.AZIUS.COM.bad for courses and scheduling
REMOVE .BAD FROM EMAIL AND WEB ADDRESS

"Brian Catlin" <> wrote in message
news:#...
> "Peter" <> wrote in message
> news:...
> > On WXPSP1 Checked/debug build I met assert:
> > Assertion failed: IopmDiffTableEntries < MaxIopmTableEntries
> > Source file: d:\xpsp1\base\hals\halx86\i386\xxbiosc.c
> >
> > This assert is invoked after calling NdisAcquireSpinLock() in my driver.
> > What does it mean this assert message ?
>
> It has to do with setting the I/O privilege mask, which isn't even vaguely
> related to what you're doing. You might not be passing the address of the
> spinlock to NASL properly. Also, what does the stack trace look like?
>
> -Brian
>
> Brian Catlin, Sannas Consulting 310-944-9492
> Windows Network, Video, WDM Device Driver Training & Consulting
> See WWW.AZIUS.COM.bad for courses and scheduling
> REMOVE .BAD FROM EMAIL AND WEB ADDRESS
>
Sorry, I have not dumped call stack for this case...
But reason was incorrent using of spin lock.
I met this assert also on other place in my code
where reason was incorrent using of MmProbeAndLockPages().
Now problem is solved.

Thanks for the answer !
Peter