On Thu, 25 Aug 2005, Jason wrote:

so my system was running for about 1.5 days now and now there is no sign of the Aug 22 17:20:18 monsterjam kernel: calcru: runtime went backwards from 17036511 usec to 16590577 usec for pid 71 (schedcpu) message..

but it appears to have dumped into the debugger today for no apparent reason.

The below looks like you ran a terminal application on the client end of the serial console that generated a break signal, then initialized the modem using an AT command string. I.e., you might want to set your communication client to not generate a break signal and initialize the modem... If that's not possible, try using ALT_BREAK_TO_DEBUGGER instead of BREAK_TO_DEBUGGER in order to avoid accidental breaking to the debugger.

Robert N M Watson



here is a trace..

db> AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
No such command
db>
db> trace
Tracing pid 12 tid 100004 td 0xc2284600
kdb_enter(c0807c53) at kdb_enter+0x2b
siointr1(c2438800,c08ee3c0,0,c0807a1b,6ad) at siointr1+0xce
siointr(c2438800) at siointr+0x21
intr_execute_handlers(c2278c90,e3392cb4,4,e3392cf8,c07754a3) at 
intr_execute_handlers+0x9d
lapic_handle_intr(34) at lapic_handle_intr+0x2e
Xapic_isr1() at Xapic_isr1+0x33
--- interrupt, eip = 0xc077c87d, esp = 0xe3392cf8, ebp = 0xe3392cf8 ---
cpu_idle_default(e3392d0c,c05ed9c5,c2283a98,e3392d24,c05ed78c) at 
cpu_idle_default+0x5
cpu_idle(c2283a98,e3392d24,c05ed78c,0,e3392d38) at cpu_idle+0x28
idle_proc(0,e3392d38,0,c05ed968,0) at idle_proc+0x5d
fork_exit(c05ed968,0,e3392d38) at fork_exit+0xa4
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xe3392d6c, ebp = 0 ---
db>

and i did "continue"
and now its seeming to be running ok.

please advise.

Jason

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to