Hmm. Maybe adjust the code to panic the machine when this
situation occurs, then see if you can get a kernel dump out
of it.
As to the load issue... that sounds like a classic priority
inversion problem. Check the 'nice' of all the processes in
the system and see if some nice'd-down processes are hogging
the cpu. 'ps axlww' in a big window.
Also look at the user cpu verses system cpu percentage to see
where the cpu is going.
-Matt
Matthew Dillon
<dillon@backplane.com>
:Hi,
:
:...
:
:However, after the machine has been up for a while (variously from several
:days to as long as a few hours), the load starts shooting up, it develops
:some processes that show as "R" in ps, but are unkillable, and the
:following pops up in messages.
:
:Apr 7 00:47:53 server /kernel: kernel trap 9 with interrupts disabled
:Apr 7 00:48:24 server last message repeated 552 times
:Apr 7 00:50:00 server last message repeated 1861 times
:Apr 7 00:50:00 server /kernel: kernel trap 9 with interrupts disabled
:Apr 7 00:50:31 server last message repeated 537 times
:[etc etc etc]
:
:That appears to be
:
:#define T_PROTFLT 9 /* protection fault */
:
:I did some searching and it appears that this trap sometimes happens with
:the Linux emulator, but that's not loaded.
:
:Any suggestions as to how to go about debugging this?
:
:>From the source, I see two locations in machdep.c where it could also be
:caused...
:--
:Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message