On Feb 4, Jukka Marin wrote
> It froze again.  I hit ctrl-alt-esc about N times before I got into the
> debugger.  I viewed the process list, but couuldn't see anything odd
> (I couldn't run any command like 'ls' because the shells no longer accepted
> commands, so I don't know what state the 'ls' command would have been in).

Did you have a shell running on the console ? Did the keyboard still react 
(i.e. something gets printed on screen when you type letters) ?

>From the trace below, the debugger seems to be called from a clock interrupt
through pcvt_timeout. On a system in a good state, the trace after a 
ctrl-alt-esc looks like:
_Debugger
_sgetc
_pcintr
_Xresume1
(note that I'm using pccons, not pcvt).
Could it be possible that interrupts stays blocked (i.e. a missing splx()
somewhere) ?

> 
> Anyway, I typed 'tr' and here's what I got (didn't write down all the
> addresses):
> 
> _Debugger
> _sgetc
> _pcvt_timeout
> _softclock
> _hardclock
> _clockintr
> _Xintr0
> --- interrupt ---
> _idle(f4c11194, f08d0a00, f0206ad4, 100, f4c12f40) at _idle+0xd
> bpendtsleep(f4c11194, 128, f011b8a9, 0) at bpendtsleep
> _sys_sigsuspend(f08d0a00, f4c12f88, f4c12f80, 0, 0) at _sys_sigsuspend+0x42
> _syscall() at _syscall+0x21c
> --- syscall (number 111) ---
> 0x40071bb9:
> db>
> 

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
     {Net,Free}BSD: 21 ans d'experience feront toujours la difference
--