[Gray, Zachary C] Any plans on the MS end of things to fix the
ACPI-related extensions on Win2k3 x64? I am talking about the
extensions that dumpt the static tables such as !mapic, !rsdt, etc… I
can provide a complete list if necessary! 
Fixing !idt for x64 would be nice too!
-Zach
ZACHARY:
I waited on this one for a while myself. I may be fixed; I don’t know.
Eventually, I just wrote an extension to do it. While not my first
choice, it got to the point it was a really big inconvenience not to
have it. I don’t know what your needs are, but, assuming you don’t get
any good news shortly on the subject, and you have immediate need, if
you’re familiar enough with extensions to avoid the learning curve that
would otherwise accrue, writing one to at least dump the tables can be
very painless if you just use one of the samples and steal the ACPI
headers form some other (open source) source - something like a little
more than a day. For the little I needed, I can only relate that I wish
I had done it sooner, because I wasted so much more time incorrectly
reading the raw data dumps. Your mileage may vary.
mm
>> xxxxx@intel.com 2006-10-10 16:21 >>>
[Gray, Zachary C] Any plans on the MS end of things to fix the
ACPI-related extensions on Win2k3 x64? I am talking about the
extensions that dumpt the static tables such as !mapic, !rsdt, etc…
I
can provide a complete list if necessary!
Fixing !idt for x64 would be nice too!
-Zach
You are currently subscribed to windbg as: unknown lmsubst tag
argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
I forwarded this to the ACPI team and they didn’t know of any specific
reasons why ACPI extensions would not work on x64. They mentioned that
they have been using them successfully on x64. However, there is still
the all-platforms limitation that !amli, etc., require a private PDB,
and in many scenarios, requires a checked ACPI.sys as well.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gray, Zachary C
Sent: Tuesday, October 10, 2006 1:21 PM
To: Kernel Debugging Interest List
Subject: speaking of broken extensions… RE: [windbg] Trouble with
!irpfind
[Gray, Zachary C] Any plans on the MS end of things to fix the
ACPI-related extensions on Win2k3 x64? I am talking about the
extensions that dumpt the static tables such as !mapic, !rsdt, etc… I
can provide a complete list if necessary!
Fixing !idt for x64 would be nice too!
-Zach
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Drew,
According to the OS builds I have downloaded from MSDN this is simply
not the case. There are several extensions that simply do not work,
although it is possible that I am doing something wrong…
For the record I am using the checked builds of Win2k3 provided via
MSDN, a relatively recent build of the debugger, and the symbols
downloaded via the symbol server. With the x86 OS the commands work,
but with the x64 OS I get noise about symbols being incorrect. Some
commands do work fine (!amli for example), so I am confident the symbols
are getting loaded, it just seems that the symbols on the server for x86
and x64 are not equally “functional”
Also for the record, I am not scoping this specifically to ACPI stuff,
but also to related extensions like !ioapic, !idt, etc…
I will send you the KD logs separately. Thanks for your help on this!
-Zach
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-265852-
xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Wednesday, October 11, 2006 9:18 AM
To: Kernel Debugging Interest List
Subject: RE: speaking of broken extensions… RE: [windbg] Trouble
with !irpfindI forwarded this to the ACPI team and they didn’t know of any specific
reasons why ACPI extensions would not work on x64. They mentioned that
they have been using them successfully on x64. However, there is still
the all-platforms limitation that !amli, etc., require a private PDB,
and in many scenarios, requires a checked ACPI.sys as well.-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gray, Zachary C
Sent: Tuesday, October 10, 2006 1:21 PM
To: Kernel Debugging Interest List
Subject: speaking of broken extensions… RE: [windbg] Trouble with
!irpfind[Gray, Zachary C] Any plans on the MS end of things to fix the
ACPI-related extensions on Win2k3 x64? I am talking about the
extensions that dumpt the static tables such as !mapic, !rsdt, etc… I
can provide a complete list if necessary!Fixing !idt for x64 would be nice too!
-Zach
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
When you say “this is not the case” what are you referring to with
“this”?
The symbols available on the Microsoft public server and not full
symbols and so will not allow full functionality.
I’ll forward this and your logs to the ACPI team.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gray, Zachary C
Sent: Wednesday, October 11, 2006 4:11 PM
To: Kernel Debugging Interest List
Subject: RE: speaking of broken extensions… RE: [windbg] Trouble with
!irpfind
Drew,
According to the OS builds I have downloaded from MSDN this is simply
not the case. There are several extensions that simply do not work,
although it is possible that I am doing something wrong…
For the record I am using the checked builds of Win2k3 provided via
MSDN, a relatively recent build of the debugger, and the symbols
downloaded via the symbol server. With the x86 OS the commands work,
but with the x64 OS I get noise about symbols being incorrect. Some
commands do work fine (!amli for example), so I am confident the symbols
are getting loaded, it just seems that the symbols on the server for x86
and x64 are not equally “functional”
Also for the record, I am not scoping this specifically to ACPI stuff,
but also to related extensions like !ioapic, !idt, etc…
I will send you the KD logs separately. Thanks for your help on this!
-Zach
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-265852-
xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Wednesday, October 11, 2006 9:18 AM
To: Kernel Debugging Interest List
Subject: RE: speaking of broken extensions… RE: [windbg] Trouble with
!irpfind
I forwarded this to the ACPI team and they didn’t know of any specific
reasons why ACPI extensions would not work on x64. They mentioned that
they have been using them successfully on x64. However, there is still
the all-platforms limitation that !amli, etc., require a private PDB,
and in many scenarios, requires a checked ACPI.sys as well.-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gray, Zachary C
Sent: Tuesday, October 10, 2006 1:21 PM
To: Kernel Debugging Interest List
Subject: speaking of broken extensions… RE: [windbg] Trouble with
!irpfind[Gray, Zachary C] Any plans on the MS end of things to fix the
ACPI-related extensions on Win2k3 x64? I am talking about the
extensions that dumpt the static tables such as !mapic, !rsdt, etc… I
can provide a complete list if necessary!
Fixing !idt for x64 would be nice too!
-Zach
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
“This” == statement by ACPI team that extensions should work on x64.
Which I interpret as “should work for a normal developer who only has
access to the public materials provided my Microsoft”
I realize the symbols on the server are not the full, unstripped symbols
that might be used by internal developers, but the symbols for the two
different architectures are not consistent in what they allow. On the
x86 architecture these extensions seem to work, while on x64 they do
not. This is on the same system booting from different OS images on the
same HDD, with the same version/configuration of KD. All things being
equal the x64 OS (and associated collateral) does not support these
extensions.
Thanks again!
-Zach
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-265967-
xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Wednesday, October 11, 2006 9:01 PM
To: Kernel Debugging Interest List
Subject: RE: speaking of broken extensions… RE: [windbg] Trouble
with !irpfindWhen you say “this is not the case” what are you referring to with
“this”?The symbols available on the Microsoft public server and not full
symbols and so will not allow full functionality.I’ll forward this and your logs to the ACPI team.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gray, Zachary C
Sent: Wednesday, October 11, 2006 4:11 PM
To: Kernel Debugging Interest List
Subject: RE: speaking of broken extensions… RE: [windbg] Trouble with
!irpfindDrew,
According to the OS builds I have downloaded from MSDN this is simply
not the case. There are several extensions that simply do not work,
although it is possible that I am doing something wrong…For the record I am using the checked builds of Win2k3 provided via
MSDN, a relatively recent build of the debugger, and the symbols
downloaded via the symbol server. With the x86 OS the commands work,
but with the x64 OS I get noise about symbols being incorrect. Some
commands do work fine (!amli for example), so I am confident the
symbols
are getting loaded, it just seems that the symbols on the server for
x86
and x64 are not equally “functional”Also for the record, I am not scoping this specifically to ACPI stuff,
but also to related extensions like !ioapic, !idt, etc…I will send you the KD logs separately. Thanks for your help on this!
-Zach
>-----Original Message-----
>From: xxxxx@lists.osr.com [mailto:bounce-265852-
>xxxxx@lists.osr.com] On Behalf Of Drew Bliss
>Sent: Wednesday, October 11, 2006 9:18 AM
>To: Kernel Debugging Interest List
>Subject: RE: speaking of broken extensions… RE: [windbg] Trouble
with>!irpfind
>
>I forwarded this to the ACPI team and they didn’t know of any specific
>reasons why ACPI extensions would not work on x64. They mentioned
that>they have been using them successfully on x64. However, there is
still>the all-platforms limitation that !amli, etc., require a private PDB,
>and in many scenarios, requires a checked ACPI.sys as well.
>
>-----Original Message-----
>From: xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Gray, Zachary
C
>Sent: Tuesday, October 10, 2006 1:21 PM
>To: Kernel Debugging Interest List
>Subject: speaking of broken extensions… RE: [windbg] Trouble with
>!irpfind
>
>
>
>
>[Gray, Zachary C] Any plans on the MS end of things to fix the
>ACPI-related extensions on Win2k3 x64? I am talking about the
>extensions that dumpt the static tables such as !mapic, !rsdt, etc…
I>can provide a complete list if necessary!
>
>Fixing !idt for x64 would be nice too!
>
> -Zach
>
>—
>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
The ACPI team mentioned that they thought that the ACPI extensions would
only work with private symbols and a checked acpi.sys, so I believe they
definitely do not think they would work with any normal developer with
only public materials.
I’ve sent them your logs; I haven’t heard anything back so far.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gray, Zachary C
Sent: Thursday, October 12, 2006 8:41 AM
To: Kernel Debugging Interest List
Subject: RE: speaking of broken extensions… RE: [windbg] Trouble with
!irpfind
“This” == statement by ACPI team that extensions should work on x64.
Which I interpret as “should work for a normal developer who only has
access to the public materials provided my Microsoft”
I realize the symbols on the server are not the full, unstripped symbols
that might be used by internal developers, but the symbols for the two
different architectures are not consistent in what they allow. On the
x86 architecture these extensions seem to work, while on x64 they do
not. This is on the same system booting from different OS images on the
same HDD, with the same version/configuration of KD. All things being
equal the x64 OS (and associated collateral) does not support these
extensions.
Thanks again!
-Zach
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-265967-
xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Wednesday, October 11, 2006 9:01 PM
To: Kernel Debugging Interest List
Subject: RE: speaking of broken extensions… RE: [windbg] Trouble with
!irpfind
When you say “this is not the case” what are you referring to with
“this”?The symbols available on the Microsoft public server and not full
symbols and so will not allow full functionality.I’ll forward this and your logs to the ACPI team.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gray, Zachary C
Sent: Wednesday, October 11, 2006 4:11 PM
To: Kernel Debugging Interest List
Subject: RE: speaking of broken extensions… RE: [windbg] Trouble with
!irpfind
Drew,
According to the OS builds I have downloaded from MSDN this is simply
not the case. There are several extensions that simply do not work,
although it is possible that I am doing something wrong…For the record I am using the checked builds of Win2k3 provided via
MSDN, a relatively recent build of the debugger, and the symbols
downloaded via the symbol server. With the x86 OS the commands work,
but with the x64 OS I get noise about symbols being incorrect. Some
commands do work fine (!amli for example), so I am confident the
symbols
are getting loaded, it just seems that the symbols on the server for
x86
and x64 are not equally “functional”Also for the record, I am not scoping this specifically to ACPI stuff,
but also to related extensions like !ioapic, !idt, etc…I will send you the KD logs separately. Thanks for your help on this!
-Zach
>-----Original Message-----
>From: xxxxx@lists.osr.com [mailto:bounce-265852-
>xxxxx@lists.osr.com] On Behalf Of Drew Bliss
>Sent: Wednesday, October 11, 2006 9:18 AM
>To: Kernel Debugging Interest List
>Subject: RE: speaking of broken extensions… RE: [windbg] Trouble
with>!irpfind
>
>I forwarded this to the ACPI team and they didn’t know of any specific
>reasons why ACPI extensions would not work on x64. They mentioned
that>they have been using them successfully on x64. However, there is
still>the all-platforms limitation that !amli, etc., require a private PDB,
>and in many scenarios, requires a checked ACPI.sys as well.
>
>-----Original Message-----
>From: xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Gray, Zachary
C
>Sent: Tuesday, October 10, 2006 1:21 PM
>To: Kernel Debugging Interest List
>Subject: speaking of broken extensions… RE: [windbg] Trouble with
>!irpfind
>
>
>
>
>[Gray, Zachary C] Any plans on the MS end of things to fix the
>ACPI-related extensions on Win2k3 x64? I am talking about the
>extensions that dumpt the static tables such as !mapic, !rsdt, etc…
I>can provide a complete list if necessary!
>
>Fixing !idt for x64 would be nice too!
>
> -Zach
>
>—
>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
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
For whatever it is worth, I can confirm every problem Zachary mentions
on the same platforms.
mm
>> xxxxx@intel.com 2006-10-12 11:40 >>>
“This” == statement by ACPI team that extensions should work on x64.
Which I interpret as “should work for a normal developer who only has
access to the public materials provided my Microsoft”
I realize the symbols on the server are not the full, unstripped
symbols
that might be used by internal developers, but the symbols for the two
different architectures are not consistent in what they allow. On the
x86 architecture these extensions seem to work, while on x64 they do
not. This is on the same system booting from different OS images on
the
same HDD, with the same version/configuration of KD. All things being
equal the x64 OS (and associated collateral) does not support these
extensions.
Thanks again!
-Zach
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-265967-
xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Wednesday, October 11, 2006 9:01 PM
To: Kernel Debugging Interest List
Subject: RE: speaking of broken extensions… RE: [windbg] Trouble
with !irpfindWhen you say “this is not the case” what are you referring to with
“this”?The symbols available on the Microsoft public server and not full
symbols and so will not allow full functionality.I’ll forward this and your logs to the ACPI team.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gray, Zachary
C
Sent: Wednesday, October 11, 2006 4:11 PM
To: Kernel Debugging Interest List
Subject: RE: speaking of broken extensions… RE: [windbg] Trouble
with
!irpfindDrew,
According to the OS builds I have downloaded from MSDN this is simply
not the case. There are several extensions that simply do not work,
although it is possible that I am doing something wrong…For the record I am using the checked builds of Win2k3 provided via
MSDN, a relatively recent build of the debugger, and the symbols
downloaded via the symbol server. With the x86 OS the commands work,
but with the x64 OS I get noise about symbols being incorrect. Some
commands do work fine (!amli for example), so I am confident the
symbols
are getting loaded, it just seems that the symbols on the server for
x86
and x64 are not equally “functional”Also for the record, I am not scoping this specifically to ACPI
stuff,
but also to related extensions like !ioapic, !idt, etc…I will send you the KD logs separately. Thanks for your help on
this!
-Zach
>-----Original Message-----
>From: xxxxx@lists.osr.com [mailto:bounce-265852-
>xxxxx@lists.osr.com] On Behalf Of Drew Bliss
>Sent: Wednesday, October 11, 2006 9:18 AM
>To: Kernel Debugging Interest List
>Subject: RE: speaking of broken extensions… RE: [windbg] Trouble
with>!irpfind
>
>I forwarded this to the ACPI team and they didn’t know of any
specific
>reasons why ACPI extensions would not work on x64. They mentioned
that>they have been using them successfully on x64. However, there is
still>the all-platforms limitation that !amli, etc., require a private
PDB,
>and in many scenarios, requires a checked ACPI.sys as well.
>
>-----Original Message-----
>From: xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Gray,
Zachary
C
>Sent: Tuesday, October 10, 2006 1:21 PM
>To: Kernel Debugging Interest List
>Subject: speaking of broken extensions… RE: [windbg] Trouble with
>!irpfind
>
>
>
>
>[Gray, Zachary C] Any plans on the MS end of things to fix the
>ACPI-related extensions on Win2k3 x64? I am talking about the
>extensions that dumpt the static tables such as !mapic, !rsdt, etc…
I>can provide a complete list if necessary!
>
>Fixing !idt for x64 would be nice too!
>
> -Zach
>
>—
>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
You are currently subscribed to windbg as: unknown lmsubst tag
argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com