Re: How is possible that NDIS_PACKET->Head->MappedSystemVa is pageable
- From: "Thomas F. Divine [DDK MVP]" <tdivine@xxxxxxxxxxxxxxxx>
- Date: Sun, 7 May 2006 09:03:21 -0400
When you construct your packet ti indicate, do you insure that the first NDIS buffer contains the MAC header plus LookaheadSize bytes?
This is a requirement, and failure to comply can cause problems like the one you are seeing.
Thomas F. Divine, Windows DDK MVP
http://www.pcausa.com
"Peter" <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:23AF6F43-B238-433E-A23F-FE72C3E384D8@xxxxxxxxxxxxxxxx
I met bug:
DRIVER_IRQL_NOT_LESS_OR_EQUAL,
Bug occurred inside of: NdisMIndicateReceivePacket(...,myPacket, 1);
called from my driver.
Amazing is that address of memory referenced is inside of NDIS_PACKET:
MyPacket->Head->MappedSystemVa.
I see in memory in debugger that MappedSystemVa is not displayable ant it
show error ERROR_READ_FAULT, so it is probably paged.
I met this bug in system with debug versions of kernel,hal and ndis.sys
and on system running under memory stress with driver verifier turned on my
driver and ndis.sys.
MyPacket was allocated with NdisDprAllocatePacket() and buffers are created
by copying from original packet with help of NdisCopyBuffer().
How can be possible that packet created by such way has paged
Head->MappedSystemVa ?
What can I to do in my code to avoid of this ?
Peter
.
- Prev by Date: Re: How is possible that NDIS_PACKET->Head->MappedSystemVa is page
- Next by Date: Re: How is possible that NDIS_PACKET->Head->MappedSystemVa is page
- Previous by thread: Re: How is possible that NDIS_PACKET->Head->MappedSystemVa is page
- Next by thread: 1394 bus device enumaration
- Index(es):
Relevant Pages
|
Loading
