Unable to run Windbg 6.0.0017.0 on Micron ClentPro

Fred_Walters · June 27, 2002, 2:57pm

Windbg not working on Micron ClientPro PC. (I’ve verified this on
multiple Micron’s and they fail in the same manner)

Anyone else run into this problem? I verified the serial port via
HyperTerminal the and boot.ini settings. (The same host machine connects
okay to other target machines…just not the Micron). Attempting to boot
Windows 2000 with Windbg debuging enabled just hangs the target machine.
The host machine simply shows the following:

Opened \.\com1
Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: *** Invalid *** : Verify _NT_SYMBOL_PATH setting
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger.
using .sympath and .sympath+ *
******************************************************************
ERROR: Symbol file could not be found. Defaulted to export symbols
for ntoskrnl.exe -
Windows 2000 Kernel Version 2195 UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046a4c0
System Uptime: not available</symbol_path>

David_Holcomb · June 27, 2002, 3:02pm

That is a valid connection to the target. You just don’t have your
symbol path set.

Instructions on setting your symbol path can be found in debugger.chm
and on http://www.microsoft.com/ddk/debugging. Look for the symbols
link.

-----Original Message-----
From: xxxxx@charter.net [mailto:xxxxx@charter.net]
Sent: Thursday, June 27, 2002 11:58 AM
To: Kernel Debugging Interest List
Subject: [windbg] Unable to run Windbg 6.0.0017.0 on Micron ClentPro

Windbg not working on Micron ClientPro PC. (I’ve verified this on
multiple Micron’s and they fail in the same manner)

Anyone else run into this problem? I verified the serial port via
HyperTerminal the and boot.ini settings. (The same host machine
connects okay to other target machines…just not the Micron).
Attempting to boot Windows 2000 with Windbg debuging enabled just hangs
the target machine.
The host machine simply shows the following:

Opened \.\com1
Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE Kernel
Debugger connection established. Symbol search path is: *** Invalid ***
: Verify _NT_SYMBOL_PATH setting Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger.
using .sympath and .sympath+ *
******************************************************************
ERROR: Symbol file could not be found. Defaulted to export symbols
for ntoskrnl.exe - Windows 2000 Kernel Version 2195 UP Free x86
compatible Kernel base = 0x80400000 PsLoadedModuleList = 0x8046a4c0
System Uptime: not available

—
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%</symbol_path>

Fred_Walters · June 27, 2002, 5:07pm

The problem occurs regardless of if symbols are found/loaded. Besides,
loading (or not loading) symbols should never hang the target machine.

So, once again: A target machine (always a Micron ClientPro) simply
freezes during a debug boot-up but the host never gains control. The host
does show the initial connection (as shown in my previous post). But,
can’t break into the target. Any Ideas?

Thanks in advance!

Nathan_Nesbit · June 27, 2002, 5:14pm

The only thing that comes to mind is to turn off “legacy usb” in the
bios of the target machine. This is a workaround for a known issue with
some chipsets which messes up the serial communication.

-----Original Message-----
From: xxxxx@charter.net [mailto:xxxxx@charter.net]
Sent: Thursday, June 27, 2002 2:07 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Unable to run Windbg 6.0.0017.0 on Micron ClentPro

The problem occurs regardless of if symbols are found/loaded. Besides,
loading (or not loading) symbols should never hang the target machine.

So, once again: A target machine (always a Micron ClientPro) simply
freezes during a debug boot-up but the host never gains control. The
host does show the initial connection (as shown in my previous post).
But, can’t break into the target. Any Ideas?

Thanks in advance!

You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%