I’ll try the “legacy USB” suggestion.
It’s independent of Windbg and I was asking because I was wondering if
anyone else has seen it. I was assuming others are in a position to have
done some remote debugging and thought that maybe someone else would
have seen it. Apparently not.
Regarding the last item, that makes since and I didn’t assume that you
could break in once shutdown occurred. I’d hope anyone being paid to
develop commercial drivers would realize this too. But then given some
of the stuff I’ve seen out there …
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Monday, November 05, 2001 6:14 PM
To: Kernel Debugging Interest List
Cc: Kernel Debugging Interest List
Subject: [windbg] RE: windbg digest: November 01, 2001
Have you tried the “legacy usb” thing on the target machine (the one
being debugged)?
Other than that I have no suggestions, except to try without Windbg
running and see if it is independent of windbg or not.
Concerning #2. Windbg needs a running OS to talk to. If the machine is
shutdown then there is nothing to respond to Windbg.
-----Original Message-----
From: Kelley, Jerry [mailto:xxxxx@nsisoftware.com]
Sent: Monday, November 05, 2001 2:13 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: windbg digest: November 01, 2001
Okay, since it seems confusing, I’ll try again:
-
I connect to a remote system that is running terminal services. This
system is running Windbg and is connected via the serial port to a
target system which is also running terminal services. So I have two
terminal services sessions running - one to the system running Windbg
and the other to the target system.
-
The remote target system needs to be rebooted for some reason. About
a third of the time, when “restart” is selected from the shutdown
window, the remote target actually goes to shutdown and does not reboot.
I can’t break into the remote target from the remote Windbg system via
Windbg.
-
This means that the remote target has gone into shutdown and did not
reboot. It’s just sitting there with the “system has been shutdown”
screen and no way to break in.
-
The way to be assured that this does not happen is to issue the
“.reboot” from the remote system that is running Windbg.
I’d appreciate it if, in the future, another post is confusing that I
hear about it so I can rewrite it. 
Thanks.
–jerry
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Monday, November 05, 2001 4:39 PM
To: Kernel Debugging Interest List
Cc: Kelley, Jerry
Subject: RE: [windbg] RE: windbg digest: November 01, 2001
Make sure you have “Legacy USB” disable in the BIOS for the machine.
This works around a known issue with some intel chipsets that mess up
serial communication during boot.
In all fairness your original post is somewhat confusing. It isn’t at
all clear (to me anyway) that you are doing debugging with Windbg when
the reboot happens (as your second post indicates).
If the above suggestion doesn’t help then send a message that better
describes what you are doing might help get some answers.
-----Original Message-----
From: Kelley, Jerry [mailto:xxxxx@nsisoftware.com]
Sent: Monday, November 05, 2001 1:33 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: windbg digest: November 01, 2001
Wow, this must have stumped everyone. Only one response.
Either we’re the only who’ve seen it or others have but no one knows how
to solve it. It is pretty annoying if you want to do remote debugging.
-----Original Message-----
From: Szepesi, Dan B. [mailto:xxxxx@digex.com]
Sent: Friday, November 02, 2001 5:52 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: windbg digest: November 01, 2001
Are these Compaq machines by any chance ?
We have seen these occur with Compaq servers - I think updating the BIOS
was
part of the solution.
*****************************************************
Daniel B. Szepesi, MCSE, MCP+I
Digex, Inc.
NT Operations Engineer
After Hours: 1-88 USE DIGEX (888-733-4439)
E-Mail: xxxxx@digex.com
*****************************************************
-----Original Message-----
From: Kernel Debugging Interest List digest
[mailto:xxxxx@lists.osr.com]
Sent: Thursday, November 01, 2001 11:00 PM
To: windbg digest recipients
Subject: windbg digest: November 01, 2001
WINDBG Digest for Thursday, November 01, 2001.
- breaking into a system at shutdown
Subject: breaking into a system at shutdown
From: “Jerry Kelley”
Date: Thu, 1 Nov 2001 05:45:02 -0500
X-Message-Number: 1
I’m debugging Win2K systems via terminal services and, occasionally,
when I restart the system, instead of performing a complete bounce it
decides to just shutdown rather than reboot. The problem is that when
I’m working remotely I can’t get to the system to physically reset it.
I’ve got Windbg attached but once it’s gone to shutdown, I can’t break
in. I’ve resorted to using the .reboot command to be sure that it truly
reboots and does not just shutdown.
A couple of questions:
1. Has anyone else experienced this where the system goes to shutdown
and doesn’t truly reboot?
2. Is there any way that, once the system has gone to shutdown, you can
break in with Windbg and reboot it?
–jerry
—
You are currently subscribed to windbg as: xxxxx@digex.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
END OF DIGEST
—
You are currently subscribed to windbg as: xxxxx@digex.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@nsisoftware.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@nsisoftware.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com