>Number:         14587
>Category:       port-i386
>Synopsis:       i386 ddb apm interactions can be poor
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Nov 14 08:10:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     John Hawkinson
>Release:        1.5W of 24 Jun 2001
>Organization:
MIT
>Environment:
	
System: NetBSD zorkmid.mit.edu 1.5W NetBSD 1.5W (ZORKMID-$Revision: 1.12 $) #104: Sun Jun 24 21:48:35 EDT 2001 jhawk@zorkmid.mit.edu:/usr/local/netbsd-current/src/sys/arch/i386/compile/ZORKMID i386


>Description:
	Some bad things can happen with DDB and apm. I'm filing this PR
for a mysterious "machine powers down a few seconds after entering ddb"
problem, but you can also single-step your way into an apm call and lose
pretty hard, too.

>How-To-Repeat:
	Not totally sure. Hit Ctrl-Alt-Esc. Type ps/w. Look at the
output. Watch the machine power itself down without a keypress or anything.
>Fix:
	Not totally sure. Add some ddb commands to disable apm interrupts,
	and then a sysctl or something to allow them to be executed
	automatically on entry to the debugger, and restored on exit.
	Or something.
>Release-Note:
>Audit-Trail:
>Unformatted: