can't enter KDB after panic?

[Ken Preslan]

On Fri, Feb 23, 2001 at 03:12:43PM +1100, Keith Owens wrote:
> This patch renames the existing kdb panic to oops and adds panic.
> Because of the way that kdb is entered from the panic() routine, it has
> no valid exception frame.  kdb tries to synthesise an exception frame
> but that is tricky and does not always work.  If backtrace from panic
> says "not in kernel" then get the pid from the earlier message and do
> "btp pid" instead.  You can also get invalid kernel addresses due to
> the incorrect exception frame, ignore those messages.

Sweet!  Thanks for you help.


-- 
Ken Preslan <kpreslan at sistina.com>
Code Monkey
Sistina Software, Inc.