Strange behaviour on "!sysptes 4"

WINDBG
1

Hi,
I am having a small problem with Windbg to look at PTEs. I am using
WinDbg 6.0.0017.0
version 5.1 (Build 2600.xpsp_sp2_gdr.050301-1519 : Service Pack 2)

The problem is that when I execute
“!sysptes 4”
I get the following error

8055ed00: Unable to get System PTE lock consumer information

The symbol tables are loaded OK.
!lmi nt gives
Loaded Module Info: [nt]
Module: ntoskrnl
Base Address: 804d7000
Image Name: ntoskrnl.exe
Machine Type: 332 (I386)
Time Stamp: 41108004 Wed Aug 04 16:19:48 2004
Size: 214780
CheckSum: 2160c9
Characteristics: 10e perf
Debug Data Dirs: Type Size VA Pointer
CODEVIEW 25, 7231c, 7231c RSDS - GUID: (0x8592b676, 0x3f34, 0x476b, 0x9b, 0xb5, 0x60, 0x39, 0x5a, 0x38, 0x3f, 0x96)
Age: 2, Pdb: ntoskrnl.pdb
CLSID 4, 72318, 72318 [Data not mapped]
Image Type: MEMORY - Image read successfully from loaded memory.
Symbol Type: PDB - Symbols loaded successfully from symbol search path.
e:\windows\symbols\exe\ntoskrnl.pdb
Load Report: public symbols - e:\windows\symbols\exe\ntoskrnl.pdb

Also I can step through the driver code no problems. Maybe there is some setting that I have to configure with gflags.exe ???

Regards

Dr David Braendler

2

Your debugger is 3 years old. I suggest upgrading and seeing if that
fixes it.
http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David Braendler
Sent: Tuesday, July 12, 2005 11:54 PM
To: Kernel Debugging Interest List
Subject: [windbg] Strange behaviour on “!sysptes 4”

Hi,
I am having a small problem with Windbg to look at PTEs. I am using
WinDbg 6.0.0017.0
version 5.1 (Build 2600.xpsp_sp2_gdr.050301-1519 : Service Pack 2)

The problem is that when I execute
“!sysptes 4”
I get the following error

8055ed00: Unable to get System PTE lock consumer information

The symbol tables are loaded OK.
!lmi nt gives
Loaded Module Info: [nt]
Module: ntoskrnl
Base Address: 804d7000
Image Name: ntoskrnl.exe
Machine Type: 332 (I386)
Time Stamp: 41108004 Wed Aug 04 16:19:48 2004
Size: 214780
CheckSum: 2160c9
Characteristics: 10e perf
Debug Data Dirs: Type Size VA Pointer
CODEVIEW 25, 7231c, 7231c RSDS - GUID: (0x8592b676,
0x3f34, 0x476b, 0x9b, 0xb5, 0x60, 0x39, 0x5a, 0x38, 0x3f, 0x96)
Age: 2, Pdb: ntoskrnl.pdb
CLSID 4, 72318, 72318 [Data not mapped]
Image Type: MEMORY - Image read successfully from loaded memory.
Symbol Type: PDB - Symbols loaded successfully from symbol
search path.
e:\windows\symbols\exe\ntoskrnl.pdb
Load Report: public symbols - e:\windows\symbols\exe\ntoskrnl.pdb

Also I can step through the driver code no problems. Maybe there is some
setting that I have to configure with gflags.exe ???

Regards

Dr David Braendler

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

3

I am getting the following on 6.5.3.7 on XP SP2

!sysptes 4
8055ed00: Unable to get System PTE lock consumer information

4

Perhaps type information is needed for MiPteHeader ??

5

Thanks, got a repro here (on server sp1 as well as xpsp2). We’re
looking into fixing up the PDBs and pushing out a fix.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Satya Das
Sent: Wednesday, July 13, 2005 10:25 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Strange behaviour on “!sysptes 4”

I am getting the following on 6.5.3.7 on XP SP2

!sysptes 4
8055ed00: Unable to get System PTE lock consumer information

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

6

Jason,

Do the symbol updates apply to all clients, or only 32 bit clients? I’m
asking because the previous discussion on missing symbols
(mssmbios!SMBIOS_DATA_OBJECT) still does not show up for my amd64 box.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
Sent: Wednesday, July 13, 2005 8:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Strange behaviour on “!sysptes 4”

Thanks, got a repro here (on server sp1 as well as xpsp2). We’re
looking into fixing up the PDBs and pushing out a fix.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Satya Das
Sent: Wednesday, July 13, 2005 10:25 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Strange behaviour on “!sysptes 4”

I am getting the following on 6.5.3.7 on XP SP2

!sysptes 4
8055ed00: Unable to get System PTE lock consumer information

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

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

7

I actually think you’re hitting a bug in our extension. Do you get
anything from this?
dt mssmbios!_SMBIOS_DATA_OBJECT

We’re missing the leading ‘_’ in the code which was released

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, July 13, 2005 5:35 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Strange behaviour on “!sysptes 4”

Jason,

Do the symbol updates apply to all clients, or only 32 bit clients? I’m
asking because the previous discussion on missing symbols
(mssmbios!SMBIOS_DATA_OBJECT) still does not show up for my amd64 box.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
Sent: Wednesday, July 13, 2005 8:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Strange behaviour on “!sysptes 4”

Thanks, got a repro here (on server sp1 as well as xpsp2). We’re
looking into fixing up the PDBs and pushing out a fix.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Satya Das
Sent: Wednesday, July 13, 2005 10:25 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Strange behaviour on “!sysptes 4”

I am getting the following on 6.5.3.7 on XP SP2

!sysptes 4
8055ed00: Unable to get System PTE lock consumer information

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

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

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

8

While you might have a bug in the extension, I suspect it is still a
symbol problem. I get the “Your debugger is not using the correct
symbols” error with either _SMBIOS_DATA_OBJECT or SMBIOS_DATA_OBJECT.

I just manually renamed the PDB file and then reloaded. The debugger
did extract a new file from the symbol server; it is dated 27 March
2005, exactly as the version that I renamed.

Thanks,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
Sent: Wednesday, July 13, 2005 10:00 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Strange behaviour on “!sysptes 4”

I actually think you’re hitting a bug in our extension. Do you get
anything from this?
dt mssmbios!_SMBIOS_DATA_OBJECT

We’re missing the leading ‘_’ in the code which was released

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, July 13, 2005 5:35 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Strange behaviour on “!sysptes 4”

Jason,

Do the symbol updates apply to all clients, or only 32 bit clients? I’m
asking because the previous discussion on missing symbols
(mssmbios!SMBIOS_DATA_OBJECT) still does not show up for my amd64 box.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
Sent: Wednesday, July 13, 2005 8:24 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Strange behaviour on “!sysptes 4”

Thanks, got a repro here (on server sp1 as well as xpsp2). We’re
looking into fixing up the PDBs and pushing out a fix.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Satya Das
Sent: Wednesday, July 13, 2005 10:25 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Strange behaviour on “!sysptes 4”

I am getting the following on 6.5.3.7 on XP SP2

!sysptes 4
8055ed00: Unable to get System PTE lock consumer information

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

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

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

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