sysptes command

WINDBG
1

Hi

I’m trying to debug a System PTE leak issue on a W2K box.
Set up the magic registry value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Memory Management\TrackPtes
as per the WinDbg documentaion. The !sysptes 4 command, however, doesn’t
appear to work. It returns something like this:

kd> !sysptes 4

0xad8 System PTEs allocated to mapping locked pages

VA MDL PageCount Caller/CallersCaller
85df9a40 80481f80 0
+0x837c6e68/hal!HalAllocateAdapterChannel+0x11b
00000001: Unable to get System PTE individual lock consumer information

Tried on w2k3 ES with the similar results. (In both cases I used WinDbg
6.4.0007.0).

Has anyone tried to use !sysptes successfully? Any other
alternatives/ideas for debugging Sys PTEs leaks?

Thank you,

  • Vitaly
2

May be a symbols issue. What is the output of ‘!lmi nt’?

Jason

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Vitaly Vatnikov
Sent: Tuesday, February 15, 2005 5:43 PM
To: Kernel Debugging Interest List
Subject: [windbg] sysptes command

Hi

I’m trying to debug a System PTE leak issue on a W2K box.

Set up the magic registry value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Memory Management\TrackPtes

as per the WinDbg documentaion. The !sysptes 4 command, however, doesn’t
appear to work. It returns something like this:

kd> !sysptes 4

0xad8 System PTEs allocated to mapping locked pages

VA MDL PageCount Caller/CallersCaller
85df9a40 80481f80 0
+0x837c6e68/hal!HalAllocateAdapterChannel+0x11b
00000001: Unable to get System PTE individual lock consumer information

Tried on w2k3 ES with the similar results. (In both cases I used WinDbg
6.4.0007.0).

Has anyone tried to use !sysptes successfully? Any other
alternatives/ideas for debugging Sys PTEs leaks?

Thank you,

  • Vitaly

You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

Jason,
Here’s the output from a w2k3 box:

0: kd> !lmi nt
Loaded Module Info: [nt]
Module: ntkrnlmp
Base Address: 804de000
Image Name: ntkrnlmp.exe
Machine Type: 332 (I386)
Time Stamp: 3e8015c6 Tue Mar 25 03:39:34 2003
Size: 266000
CheckSum: 254553
Characteristics: 10e perf
Debug Data Dirs: Type Size VA Pointer
CODEVIEW 25, 827a4, 81fa4 RSDS - GUID: (0x4e4a894d,
0xd1a6, 0x4bc3, 0xad, 0xfe, 0xa7, 0x1f, 0x18, 0xe2, 0x93, 0x64)
Age: 2, Pdb: ntkrnlmp.pdb
CLSID 4, 827a0, 81fa0 [Data not mapped]
Image Type: MEMORY - Image read successfully from loaded memory.
Symbol Type: PDB - Symbols loaded successfully from symbol
server.

c:\websymbols\ntkrnlmp.pdb\4E4A894DD1A64BC3ADFEA71F18E293642\ntkrnlmp.pd
b
Load Report: public symbols

c:\websymbols\ntkrnlmp.pdb\4E4A894DD1A64BC3ADFEA71F18E293642\ntkrnlmp.pd
b
0: kd> !sysptes 4
8057f8a0: Unable to get System PTE lock consumer information

Subject: RE: sysptes command
From: “Jason Shay”
Date: Wed, 16 Feb 2005 16:08:54 -0800
X-Message-Number: 2

This is a multi-part message in MIME format.

------_=_NextPart_001_01C51485.0FE695BC
Content-Type: text/plain;
charset=“us-ascii”
Content-Transfer-Encoding: quoted-printable

May be a symbols issue. What is the output of ‘!lmi nt’?

=20

Jason=20

________________________________

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Vitaly Vatnikov
Sent: Tuesday, February 15, 2005 5:43 PM
To: Kernel Debugging Interest List
Subject: [windbg] sysptes command

=20

Hi

=20

I’m trying to debug a System PTE leak issue on a W2K box.

Set up the magic registry value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Memory Management\TrackPtes=20

as per the WinDbg documentaion. The !sysptes 4 command, however, doesn’t
appear to work. It returns something like this:

=20

kd> !sysptes 4

=20

0xad8 System PTEs allocated to mapping locked pages

=20

VA MDL PageCount Caller/CallersCaller
85df9a40 80481f80 0
+0x837c6e68/hal!HalAllocateAdapterChannel+0x11b
00000001: Unable to get System PTE individual lock consumer information

Tried on w2k3 ES with the similar results. (In both cases I used WinDbg
6.4.0007.0).

=20

Has anyone tried to use !sysptes successfully? Any other
alternatives/ideas for debugging Sys PTEs leaks?

=20

Thank you,

=20

- Vitaly

=20

=20

—=20
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’=20 To unsubscribe send a blank email to
xxxxx@lists.osr.com=20