Date: Fri, 24 Jun 2005 20:31:19 +0200 From: =?ISO-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net> To: stable@freebsd.org Subject: Network/fxp related panic in 5.4? Message-ID: <0C2E62BF-3F7C-48A1-9FBF-FD9CBDC00169@anduin.net>
next in thread | raw e-mail | index | archive | help
Hi all, I recently re-enabled SMP on one of my 5.4 servers (dual intel p3), and after a relatively short while (couple of days) it starts acting up. Today it was frozen and had jumped into kernel debugger on serial console. Problem is that my serial console was controlled by a terminal at work, and when I got home it seemed that the work terminal had disconnected. All I could do was a 'trace' - I don't have the panic screen (if any) nor do I have any other output because the watchdog triggered the powerswitch cycle just after I got the trace: Tracing pid 29 tid 100000 td 0xc22a0000 fxp_intr_body(c2404000,c2404000,40,ffffffff,8) at fxp_intr_body+0xd0 fxp_intr(c2404000,0,0,0,0) at fxp_intr+0x14e ithread_loop(c22f6500,e3384d38,0,0,0) at ithread_loop+0x1b8 fork_exit(c06a9150,c22f6500,e3384d38) at fork_exit+0x80 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe3384d6c, ebp = 0 --- db> What makes me wonder is ... When I connected the serial console, the db> prompt was already there. Does that mean that the work terminal disconnect somehow sent a telnet break, and triggered the kernel debugger? I.e. - this was no panic, but a stupid serial console hiccup? Is there any way to prevent this in the future - like changing the control character that would trigger the kernel debugger? (I have BREAK_TO_DEBUGGER in my kernel config..) Thanks, /Eirik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0C2E62BF-3F7C-48A1-9FBF-FD9CBDC00169>