Hi all,
I am new one for Windbg. I have a problem with setting ACPI debug environment.
My environment lists as below:
Host:
OS: Win7 32bit
WDK: 8.0 & 8.1
Static IP: 192.168.1.10, mask:255.255.255.0
Target:
OS:Win8.1 pro 64bit free build http://msdn.microsoft.com/en-us/library/windows/hardware/ff547188(v=vs.85).aspx>
WDK: Win8.1
Static IP: 192.168.1.20, mask:255.255.255.0
BCD setting:
Command: bcdedit /enum
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {0e292734-f0f5-11e3-bc1e-a5539b2a498c}
displayorder {current}
{0e29273c-f0f5-11e3-bc1e-a5539b2a498c}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader “1”
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 8.1
locale en-US
inherit {bootloadersettings}
recoverysequence {0e292736-f0f5-11e3-bc1e-a5539b2a498c}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {0e292734-f0f5-11e3-bc1e-a5539b2a498c}
nx OptIn
bootmenupolicy Standard
usefirmwarepcisettings No
debug Yes
Windows Boot Loader “2” <- for checked build
-------------------
identifier {0e29273c-f0f5-11e3-bc1e-a5539b2a498c}
device partition=C:
path \Windows\system32\winload.efi
description Windows 8.1 Partial Checked Build"
locale en-US
inherit {bootloadersettings}
recoverysequence {0e292736-f0f5-11e3-bc1e-a5539b2a498c}
integrityservices Enable
recoveryenabled Yes
bootdebug Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
kernel ntkrnlmp.chk
hal hal.chk
resumeobject {0e292734-f0f5-11e3-bc1e-a5539b2a498c}
nx OptIn
bootmenupolicy Standard
usefirmwarepcisettings No
debug Yes
***
Command: bcdedit /dbgsettings
key a.b.c.d
debugtype NET
hostip 192.168.1.10
port 50000
dhcp Yes
When I finished every thing and restart my tartget PC to debug, and it happens error.
As following is my Windbg’s message:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Using NET for debugging
Opened WinSock 2.0
Waiting to reconnect…
Connected to target 169.254.246.253 on port 50000 on local IP 192.168.1.10.
BD: Boot Debugger Initialized
Connected to Windows Boot Debugger 9600 x64 target at (Wed Jun 25 14:02:55.899 2014 (UTC + 8:00)), ptr64 TRUE
Kernel Debugger connection established.
Symbol search path is: SRVC:\Symbolshttp://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Boot Debugger Kernel Version 9600 UP Free x64
Machine Name:
Primary image base = 0x00000000008e4000 Loaded module list = 0x0000000000abc8a0
System Uptime: not available
Windows is unable to verify the signature of
the file \Windows\system32\ntkrnlmp.chk. It will be allowed to load
because the boot debugger is enabled.
Windows is unable to verify the signature of
the file \Windows\system32\hal.chk. It will be allowed to load
because the boot debugger is enabled.
… Retry sending the same data packet for 64 times.
The transport connection between host kernel debugger and target Windows seems lost.
please try resync with target, recycle the host debugger, or reboot the target Windows.
KDNET received an out of sequence ping packet.
The target machine restarted without notifying the debugger.
Forcing a debugger reconnect…
…
…
…
Repeat and repeat
…
…
I have tried following tests:
1.Connect to Windows Boot Loader “1”: Windbg connect success and works well.
2.Connect to Windows Boot Loader “2”: The error happened
3.Connect to Windows Boot Loader “2” : Windbg connect success and works well, but I can not add a breakpoint on Windbg.
4.Connect to Windows Boot Loader “2” : The error happened
Is there any suggestions for this? Many thanks~
Hi all,
I am new one for Windbg. I have a problem with setting ACPI debug
environment.
My environment lists as below:cable wihtout through any switch or hub.>
Host:
OS: Win7 32bit
WDK: 8.0 & 8.1
Static IP: 192.168.1.10, mask:255.255.255.0
Target:
OS:Win8.1 pro 64bit free build change OS to checked build->
http://msdn.microsoft.com/en-us/library/windows/hardware/ff547188(v=vs.85).aspx>
WDK: Win8.1
Static IP: 192.168.1.20, mask:255.255.255.0
BCD setting:
Command: bcdedit /enum
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {0e292734-f0f5-11e3-bc1e-a5539b2a498c}
displayorder {current}
{0e29273c-f0f5-11e3-bc1e-a5539b2a498c}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader “1”
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 8.1
locale en-US
inherit {bootloadersettings}
recoverysequence {0e292736-f0f5-11e3-bc1e-a5539b2a498c}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {0e292734-f0f5-11e3-bc1e-a5539b2a498c}
nx OptIn
bootmenupolicy Standard
usefirmwarepcisettings No
debug Yes
Windows Boot Loader “2” <- for checked build
-------------------
identifier {0e29273c-f0f5-11e3-bc1e-a5539b2a498c}
device partition=C:
path \Windows\system32\winload.efi
description Windows 8.1 Partial Checked Build"
locale en-US
inherit {bootloadersettings}
recoverysequence {0e292736-f0f5-11e3-bc1e-a5539b2a498c}
integrityservices Enable
recoveryenabled Yes
bootdebug Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
kernel ntkrnlmp.chk
hal hal.chk
resumeobject {0e292734-f0f5-11e3-bc1e-a5539b2a498c}
nx OptIn
bootmenupolicy Standard
usefirmwarepcisettings No
debug Yes
******************************************************************
Command: bcdedit /dbgsettings
key a.b.c.d
debugtype NET
hostip 192.168.1.10
port 50000
dhcp Yes
When I finished every thing and restart my tartget PC to debug, and it
happens error.
As following is my Windbg’s message:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Using NET for debugging
Opened WinSock 2.0
Waiting to reconnect…
Connected to target 169.254.246.253 on port 50000 on local IP 192.168.1.10.
BD: Boot Debugger Initialized
Connected to Windows Boot Debugger 9600 x64 target at (Wed Jun 25
14:02:55.899 2014 (UTC + 8:00)), ptr64 TRUE
Kernel Debugger connection established.
Symbol search path is:
SRVC:\Symbolshttp://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Boot Debugger Kernel Version 9600 UP Free x64
Machine Name:
Primary image base = 0x00000000008e4000 Loaded module list = <br>0x0000000000abc8a0
System Uptime: not available
*** Windows is unable to verify the signature of
the file \Windows\system32\ntkrnlmp.chk. It will be allowed to load
because the boot debugger is enabled.
Windows is unable to verify the signature of
the file \Windows\system32\hal.chk. It will be allowed to load
because the boot debugger is enabled.
… Retry sending the same data packet for 64 times.
The transport connection between host kernel debugger and target Windows
seems lost.
please try resync with target, recycle the host debugger, or reboot the
target Windows.
KDNET received an out of sequence ping packet.
The target machine restarted without notifying the debugger.
Forcing a debugger reconnect…
…
…
…
Repeat and repeat
…
…
***********************************************************
I have tried following tests:
1.Connect to Windows Boot Loader “1”: Windbg connect success and works
well.
2.Connect to Windows Boot Loader “2”: The error happened
3.Connect to Windows Boot Loader “2” off>: Windbg connect success and works well, but I can not add a breakpoint on
Windbg.
4.Connect to Windows Boot Loader “2” : The
error happened
Is there any suggestions for this? Many thanks~
Why don’t you just turn on debugging first without replacing the kernel and the hal.
It looks from the spew below like your machine is rebooting sometime after the checked kernel and hal are loaded. (That is why you get the restarted message.)
It is possible to debug with the retail kernel and hal, and you should get that working first before you make things more complicated.
The checked hal and kernel will help catch problems in your code, but you can do that yourself even better by just stepping through your code in the debugger.
You can also turn on driver verifier on the retail kernel and hal and that will catch many issues also.
Most developers doing kernel development at Microsoft use non checked builds much of the time.
Joe.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Wednesday, June 25, 2014 12:18 AM
To: Kernel Debugging Interest List
Subject: RE:[windbg] ACPI debugging through NIC: connection lost error
Hi all,
I am new one for Windbg. I have a problem with setting ACPI debug environment.
My environment lists as below:
Host:
OS: Win7 32bit
WDK: 8.0 & 8.1
Static IP: 192.168.1.10, mask:255.255.255.0
Target:
OS:Win8.1 pro 64bit free build http://msdn.microsoft.com/en-us/library/windows/hardware/ff547188(v=vs.85).aspx>
WDK: Win8.1
Static IP: 192.168.1.20, mask:255.255.255.0
BCD setting:
Command: bcdedit /enum
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {0e292734-f0f5-11e3-bc1e-a5539b2a498c}
displayorder {current}
{0e29273c-f0f5-11e3-bc1e-a5539b2a498c}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader “1”
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 8.1
locale en-US
inherit {bootloadersettings}
recoverysequence {0e292736-f0f5-11e3-bc1e-a5539b2a498c}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {0e292734-f0f5-11e3-bc1e-a5539b2a498c}
nx OptIn
bootmenupolicy Standard
usefirmwarepcisettings No
debug Yes
Windows Boot Loader “2” <- for checked build
-------------------
identifier {0e29273c-f0f5-11e3-bc1e-a5539b2a498c}
device partition=C:
path \Windows\system32\winload.efi
description Windows 8.1 Partial Checked Build"
locale en-US
inherit {bootloadersettings}
recoverysequence {0e292736-f0f5-11e3-bc1e-a5539b2a498c}
integrityservices Enable
recoveryenabled Yes
bootdebug Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
kernel ntkrnlmp.chk
hal hal.chk
resumeobject {0e292734-f0f5-11e3-bc1e-a5539b2a498c}
nx OptIn
bootmenupolicy Standard
usefirmwarepcisettings No
debug Yes
******************************************************************
Command: bcdedit /dbgsettings
key a.b.c.d
debugtype NET
hostip 192.168.1.10
port 50000
dhcp Yes
When I finished every thing and restart my tartget PC to debug, and it happens error.
As following is my Windbg’s message:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Using NET for debugging
Opened WinSock 2.0
Waiting to reconnect…
Connected to target 169.254.246.253 on port 50000 on local IP 192.168.1.10.
BD: Boot Debugger Initialized
Connected to Windows Boot Debugger 9600 x64 target at (Wed Jun 25
14:02:55.899 2014 (UTC + 8:00)), ptr64 TRUE
Kernel Debugger connection established.
Symbol search path is:
SRVC:\Symbolshttp://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Boot Debugger Kernel Version 9600 UP Free x64
Machine Name:
Primary image base = 0x00000000008e4000 Loaded module list =<br>0x0000000000abc8a0
System Uptime: not available
*** Windows is unable to verify the signature of
the file \Windows\system32\ntkrnlmp.chk. It will be allowed to load
because the boot debugger is enabled.
Windows is unable to verify the signature of
the file \Windows\system32\hal.chk. It will be allowed to load
because the boot debugger is enabled.
… Retry sending the same data packet for 64 times.
The transport connection between host kernel debugger and target Windows seems lost.
please try resync with target, recycle the host debugger, or reboot the target Windows.
KDNET received an out of sequence ping packet.
The target machine restarted without notifying the debugger.
Forcing a debugger reconnect…
…
…
…
Repeat and repeat
…
…
***********************************************************
I have tried following tests:
1.Connect to Windows Boot Loader “1”: Windbg connect success and works well.
2.Connect to Windows Boot Loader “2”: The error happened
3.Connect to Windows Boot Loader “2” off>: Windbg connect success and works well, but I can not add a
off>breakpoint on
Windbg.
4.Connect to Windows Boot Loader “2” : The error happened
Is there any suggestions for this? Many thanks~
—
WINDBG is sponsored by OSR
OSR is hiring!! Info at http://www.osr.com/careers
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
Hi Joe,
Thanks for your suggestions.
Because I have to trace ACPI status, and I don’t have a checked build version.
So the only way I can do is try to make a free build version can debugged ACPI.
May be I should try to get a checked build version.
Jay