Josh Hope wrote:
> 
> Okay, well...NetBSD froze again last night. It was frozen for about 8
> hours (there was a running clock on the screen, so I knew excatly what
> time it froze).
> 
> This time, I did a trace and wrote down the results:
> 
> db> trace
> _Debugger(d51ba,5764a,7ffbd0,32be,2) + 6
> _nmihand(2,cbf7c9cb,21042c,2) + 26
> _lev7intr(105418,6babc00,6b1b950,6b3c780,6babc00,14) + 12

>From here up is the result of hitting the programmer's switch.  From here
down is what your machine was doing when it locked up....

> _ip_output(6babc00,0,6ba0224,0,0) + 34a
> _tcp_output(6b8c500,6b9e680,9,14,14) + 6d6
> _tcp_input(6b9e680,14) + 10dc
> _ipintr(7ffd8c,db120,0,16af,16af) + 3be
> _netintr(0,16af,16af,118,3c) + 36
> _tnap(9,0,0) + 3a0
> rei(?)
> _mi_switch(0,2004,6b26f00,0,7fff80) + 98
> _tsleep(f9810,118,2c4d8,3c) + 178
> _sys_select(6b26f00,7fff88,7fff80) + 250
> _syscall(5d) + 13e
> _trap() + e
> db>
> 
> There it is, in all it's enigmatic glory :)
> 
> I hope this helps someone solve this most mysterious problem. Upon
> freezing last night, the box had been up without freezing for about 2
> days. So why is it freezing all of a sudden in seemingly random intervals?
> I don't get it.

Are you sure this machine isn't on a network?  This actually looks kinda
like the LAND bug attack, but I don't know enough about that to say for
sure....
 
> Oh, BTW, after the new db> prompt, it freezes again, and I can't type
> anything on the prompt, and interrupt switch doesn't bring it back...

That's not too surprising.  It often does that for me, too.

> Thanks a lot for all your help!

What kernel are you using here?

Later.

-- 
Colin Wood                                 cwood@ichips.intel.com
Component Design Engineer - MD6                 Intel Corporation
-----------------------------------------------------------------
I speak only on my own behalf, not for my employer.