Does the initial breakpoint work?

WINDBG
1

I’m using WinDBG 2.0.11 Beta, with the 2.0.14 executable. Target is Win2K
SP1 Checked Build. I’ve tried to break into the boot using the initial
breakpoint two different ways, with identical results. The first way I
tried was to Ctrl+Alt+K, cycling the initial break until I got “Will request
initial breakpoint at next boot.” This resulted in the following output in
the command window:

Break instruction exception - code 80000003 (first chance)
804a3ce4 cc int 3
FreezeLock was jammed! Backup SpinLock was used!
Port lock was not acquired!
MM:***PAGE FAULT AT IRQL > 1 Va 00000FF8, IRQL 1f
FreezeLock was jammed! Backup SpinLock was used!
Port lock was not acquired!

*** Fatal System Error: 0x0000000a
(0x00000FF8,0x0000001F,0x00000000,0x80471FEA)

FreezeLock was jammed! Backup SpinLock was used!
Port lock was not acquired!

So I left the initial break off, and tried the /BREAK switch in boot.ini.
Same output. It looks to me like an accidental attempt to do a memory read
of IO space. Am I doing something wrong? Or is this fundamentally broken?

This one trashes the target so badly, the only way to get it restarted is to
cycle the power. That’s not so bad, but it also seems to confuse WinDBG so
much that the only way to reconnect is to close WinDBG and start another
session. It won’t ever reconnect if I just restart the target. I see the
same behavior on NT4, except that if the target is set to reboot on STOP
errors, it does reboot, leaving WinDBG thinking it’s still waiting for data
from the target.

Anyone got any wisdom for me?

Thanks,

Phil

* Philip D. Barila | (503) 264-8386
* Intel Corp. | M/S JF2-53 Office JF2-2-G6
* Storage Architecture and Performance
* Internet Systems Lab

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

2

I have seen the same issue intermittently with the following configuration.
The response I got from the windbg team was power cycle the target and
restart windbg. This makes me wonder if it is more an OS issue than a
windbg one as they were responsive about the other issue I’ve reported

Host
Compaq SP750 2 CPUs
W2K Free
WinDBG 2.0.11 & 2.0.14 executables

Target
Compaq SP750 2 CPUs
W2K free build

It happens about 1 time in 10 on my system, but since I am running free
build I haven’t seen the freezelock stuff, just the bugcheck.

–
Dan

-----Original Message-----
From: Barila, Phil [mailto:xxxxx@intel.com]
Sent: Thursday, December 21, 2000 4:03 PM
To: Kernel Debugging Interest List
Subject: [windbg] Does the initial breakpoint work?

I’m using WinDBG 2.0.11 Beta, with the 2.0.14 executable.
Target is Win2K
SP1 Checked Build. I’ve tried to break into the boot using
the initial
breakpoint two different ways, with identical results. The
first way I
tried was to Ctrl+Alt+K, cycling the initial break until I
got “Will request
initial breakpoint at next boot.” This resulted in the
following output in
the command window:

Break instruction exception - code 80000003 (first chance)
804a3ce4 cc int 3
FreezeLock was jammed! Backup SpinLock was used!
Port lock was not acquired!
MM:***PAGE FAULT AT IRQL > 1 Va 00000FF8, IRQL 1f
FreezeLock was jammed! Backup SpinLock was used!
Port lock was not acquired!

*** Fatal System Error: 0x0000000a
(0x00000FF8,0x0000001F,0x00000000,0x80471FEA)

FreezeLock was jammed! Backup SpinLock was used!
Port lock was not acquired!

So I left the initial break off, and tried the /BREAK switch
in boot.ini.
Same output. It looks to me like an accidental attempt to do
a memory read
of IO space. Am I doing something wrong? Or is this
fundamentally broken?

This one trashes the target so badly, the only way to get it
restarted is to
cycle the power. That’s not so bad, but it also seems to
confuse WinDBG so
much that the only way to reconnect is to close WinDBG and
start another
session. It won’t ever reconnect if I just restart the
target. I see the
same behavior on NT4, except that if the target is set to
reboot on STOP
errors, it does reboot, leaving WinDBG thinking it’s still
waiting for data
from the target.

Anyone got any wisdom for me?

Thanks,

Phil

* Philip D. Barila | (503) 264-8386
* Intel Corp. | M/S JF2-53 Office JF2-2-G6
* Storage Architecture and Performance
* Internet Systems Lab

You are currently subscribed to windbg as: xxxxx@emc.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