Hi
I have 2 Win XP profession SP2.
On 1st machines, poolusage is as given:
Pool Used:
NonPaged Paged
Tag Allocs Used Allocs Used
GetGlobalValue: unable to get nt!KeNumberProcessors type size
MmCm 2189 65110560 0 0 Calls made to MmAllocateContiguousMemory , Binary: nt!mm
Cont 3 21037200 0 0 Contiguous physical memory allocations for device drivers
But, on the 2nd machine, MmCm and Cont Pooltags are just a few KBs.
When I saw the loaded drivers, On the 1st machine where MmCm is 65MB, diskdump driver is loaded. But, on the 2nd machine, its not loaded at all.
If I remove diskdump driver on the 1st machine, the MmCm pooltag comes down to 9MB from 65MB.
Can anyone tell me why there is this kind of a difference in pooltag allocations and would it depend on the hardware ?
Thanks in advance,
Vinay
The adapter miniport driver (cloned in diskdump.sys) has allocated a huge
block of contiguous memory for common buffer dma.
On Mon, Jun 2, 2008 at 6:26 AM, wrote:
> Hi
>
> I have 2 Win XP profession SP2.
>
> On 1st machines, poolusage is as given:
>
> Pool Used:
> NonPaged Paged
> Tag Allocs Used Allocs Used
> GetGlobalValue: unable to get nt!KeNumberProcessors type size
> MmCm 2189 65110560 0 0 Calls made to
> MmAllocateContiguousMemory , Binary: nt!mm
> Cont 3 21037200 0 0 Contiguous physical memory
> allocations for device drivers
>
> But, on the 2nd machine, MmCm and Cont Pooltags are just a few KBs.
>
> When I saw the loaded drivers, On the 1st machine where MmCm is 65MB,
> diskdump driver is loaded. But, on the 2nd machine, its not loaded at all.
>
> If I remove diskdump driver on the 1st machine, the MmCm pooltag comes down
> to 9MB from 65MB.
>
> Can anyone tell me why there is this kind of a difference in pooltag
> allocations and would it depend on the hardware ?
>
> Thanks in advance,
> Vinay
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
Mark Roddy
Mark,
I don’t think I got what you said. Can you please elaborate.
Vinay
diskdump.sys is a copy of the boot hba driver. That ‘cloned’ driver on your
system appears to have allocated a large chunk of contiguous memory for
common buffer dma purposes. What about that do you not understand?
On Tue, Jun 3, 2008 at 12:12 AM, wrote:
>
> Mark,
>
> I don’t think I got what you said. Can you please elaborate.
>
> Vinay
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
Mark Roddy
Actually, diskdump.sys is loaded under the name (in the loaded module list)
of dump_scsiport.sys
The SCSIPORT’s miniport for the HBA is also loaded the second time under
the name of dump_.sys
DISKDUMP has the same exports as SCSIPORT, so, the second instance of HBA
driver is bound to the exports in DISKDUMP.
Then SCSIPORT of the main stack responds to IOCTL_SCSI_GET_DUMP_POINTERS
from the kernel proper on pagefile init, the kernel saves the response and the
the DriverEntry address of DISKDUMP - it is NOT called till the crash will
occur.
On crash, DriverEntry of DISKDUMP is called with the “dump pointers”
response, this returns some functions to the kernel - Start/Write/End IIRC, the
kernel writes the dump by calling them.
–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
“Mark Roddy” wrote in message news:xxxxx@ntdev…
> diskdump.sys is a copy of the boot hba driver. That ‘cloned’ driver on your
> system appears to have allocated a large chunk of contiguous memory for
> common buffer dma purposes. What about that do you not understand?
>
> On Tue, Jun 3, 2008 at 12:12 AM, wrote:
>
> >
> > Mark,
> >
> > I don’t think I got what you said. Can you please elaborate.
> >
> > Vinay
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
>
>
>
> –
> Mark Roddy
>
I see two modules loaded disk_.sys.
1. dump_diskdump
2. dump_MegaSR
any ideawhat these drivers are ?. I see these drivers loaded on one windows XP machine and I dont see them on the other windows XP machine. Why such a difference ?. Is is some kind of a configuration that is preventing these drivers to be loaded on other machines ?
Vinay
These drivers are loaded based on the settings for crash dumps on the
computer. If there is no crash dump you don’t have these loaded.
dump_diskdump is the equivalent of the scsiport or storport driver for crash
dumps, and the dump_MegaSR is a copy of the MegaSR driver to be used for
crash dumps.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply
wrote in message news:xxxxx@ntdev…
>I see two modules loaded disk_.sys.
> 1. dump_diskdump
> 2. dump_MegaSR
>
> any ideawhat these drivers are ?. I see these drivers loaded on one
> windows XP machine and I dont see them on the other windows XP machine.
> Why such a difference ?. Is is some kind of a configuration that is
> preventing these drivers to be loaded on other machines ?
>
> Vinay
>
> I see two modules loaded disk_.sys.
> 1. dump_diskdump
> 2. dump_MegaSR
>
> any ideawhat these drivers are ?.
The first loaded module list entry corresponds to DISKDUMP.SYS, which plays the
role of SCSIPORT for dump_MegaSR
The second one corresponds to the second instance of the MegaSR miniport loaded
for dump stack.
>I see these drivers loaded on one windows XP machine and I dont see them on
>the other windows XP machine. Why such a difference ?. Is is some kind of a
>configuration that is preventing these drivers to be loaded on other machines
?
Disabled crash dumps, or the disk controller other then MegaSR
–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
Don Burn,
Does it mean that each driver thats loaded ( like storport miniport driver) will in turn load diskdump.sys ?
If that’s corret, why would they do that ?.
Thanks,
Vinay
SCSI miniport requires the SCSIPORT (or STORPORT which is actually just
SCSIPORT v 1.1) binary to satisfy its imports.
So, if the SCSI miniport is loaded for a dump stack, it will require the
instance of the port library to satisfy its imports, and, in this case, the OS
is smart enough to substitute DISKDUMP for this purpose.
–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
wrote in message news:xxxxx@ntdev…
> Don Burn,
>
> Does it mean that each driver thats loaded ( like storport miniport driver)
will in turn load diskdump.sys ?
>
> If that’s corret, why would they do that ?.
>
> Thanks,
> Vinay
>