Subject: port-i386/14587: i386 ddb apm interactions can be poor
To: None <email@example.com>
From: John Hawkinson <firstname.lastname@example.org>
Date: 11/14/2001 11:09:37
>Synopsis: i386 ddb apm interactions can be poor
>Arrival-Date: Wed Nov 14 08:10:00 PST 2001
>Originator: John Hawkinson
>Release: 1.5W of 24 Jun 2001
System: NetBSD zorkmid.mit.edu 1.5W NetBSD 1.5W (ZORKMID-$Revision: 1.12 $) #104: Sun Jun 24 21:48:35 EDT 2001 email@example.com:/usr/local/netbsd-current/src/sys/arch/i386/compile/ZORKMID i386
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.
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.
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.