On Tue, Sep 07, 1999 at 07:09:12AM -0600, Trevin Beattie wrote:
> Admittedly my system hangs under different circumstances (randomly when
> starting an X session, or playing xboing), but I've had this problem since
> NetBSD 1.3 (maybe earlier) and it still exists under 1.4.1.  It's happened
> on both a 486/100 and a K6-2/380 system, using an accelerated server or
> just plain VGA16.  But since nobody seemed to be able to help me with it, I
> had thought I was the only person experiencing this lockup problem ...
> until now.

lookup problems are not uncommon, especially with -current but to my knowledge
the cause has always been fixed.
Most often the apparent lookup is just that the kernel was in ddb.

> 
> At 09:58 am 9/7/99 +0200, Manuel Bouyer wrote:
> >It's possible that the kernel fall under debugger, but as you were running
> >X you didn't see it. Recompile a kernel without 'options DDB' to avoid this.
> 
> If this were the case, would I be able to shut down X Windows with
> Ctrl-Alt-Del or switch virtual terminals with Ctrl-Alt-Fn?

No,

> Or would the
> Num Lock and Caps Lock LED's stop working when I hit those keys?

I don't know, I don't remenber :)
> The
> former case happens when X locks up starting a new session, and the latter
> happens when xboing freezes.
> 
> Also: If the kernel is falling into the debugger, that would indicate an
> internal problem, wouldn't it?  Then we wouldn't want the kernel to ignore
> the problem.  So what's another way we can tell whether the kernel is in
> its debugger and why?

Without 'options DDB' it will panic and do a core dump. This can be examinated
later to find the problem.

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
--