panic at in_pcbremlists()
A couple of days ago I posted a message about panicing whenever shutting down inetd. The panic persists, but now it seems to happen at any time, always stopping at in_pcbremlists(). The kernel is up-to-date, a kernel built on July 30th runs stable as a rock. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10001 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02e044a stack pointer = 0x10:0xd68d9c08 frame pointer = 0x10:0xd68d9c14 code segment = base 0x0 limit 0x, type 0x1b = DPL 0, pres 1, def32 1,gran 1 processor eflags= interrupt enabled, resume, IOPL=0 current process = 11 (swi7: tty:sio clock) trap number = 12 panic page fault DDB says: Stopped at in_pcbremlists+0x8d stack trace: in_pcbremlists() in_pcbdetach() tcp_twclose() tcp_timer tcp_slowtimeo() pfslowtimeo() softclock() ithread_loop() fork_exit() fork_trampoline() ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
FYI: Panic at in_pcbremlists()
I got a panic with today's current. I don't know I can reproduce this panic or not... Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0100 fault virtual address = 0x14 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0214186 stack pointer = 0x10:0xe519cc88 frame pointer = 0x10:0xe519cc8c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 13 (swi6: tty:sio clock) kernel: type 12 trap, code=0 Stopped at in_pcbremlists+0x82:movl%eax,0x4(%edx) db Context switches not allowed in the debugger. db trace in_pcbremlists(e9fb11e0,e9fb11e0,0,e9fb12a0,e9fb11e0) at in_pcbremlists+0x82 in_pcbdetach(e9fb11e0,6,e9fb12a0,c0225f0c,e9fb12a0) at in_pcbdetach+0x35 tcp_close(e9fb12a0,e519ccf8,c01c4246,e9fb12a0,c386c2c0) at tcp_close+0x236 tcp_timer_2msl(e9fb12a0) at tcp_timer_2msl+0x52 softclock(0) at softclock+0x136 ithread_loop(c386d180,e519cd48,c386d180,c01aeef0,0) at ithread_loop+0x12e fork_exit(c01aeef0,c386d180,e519cd48) at fork_exit+0x9c fork_trampoline() at fork_trampoline+0x8 -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FYI: Panic at in_pcbremlists()
In article local.mail.freebsd-current/[EMAIL PROTECTED] you write:
I got a panic with today's current. I don't know I can reproduce this
panic or not...
This probably is in:
1015if (LIST_FIRST(phd-phd_pcblist) == NULL) {
1016LIST_REMOVE(phd, phd_hash);
1017free(phd, M_PCB);
but without the structure pointers, there isn't much to debug.
Is there a crash dump available?
--
Jonathan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: FYI: Panic at in_pcbremlists()
At Fri, 21 Dec 2001 10:06:38 -0600 (CST),
Jonathan Lemon wrote:
I got a panic with today's current. I don't know I can reproduce this
panic or not...
This probably is in:
1015if (LIST_FIRST(phd-phd_pcblist) == NULL) {
1016LIST_REMOVE(phd, phd_hash);
1017free(phd, M_PCB);
but without the structure pointers, there isn't much to debug.
Is there a crash dump available?
Yes, I have. But this machine have 2GB memory and dump is 2GB, too.
So it is difficult to send dump. If you can instruct how I should do,
I'll follow you.
--
Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
