Re: Panic in fork()

2003-02-14 Thread Kris Kennaway
On Sat, Feb 08, 2003 at 02:04:56PM -0800, Kris Kennaway wrote: OK, I suspected that. tjr was looking into this last night and proposed the following patch: http://people.freebsd.org/~tjr/kf.diff OK, I got another panic with this patch in place, so I guess that's not enough. Maybe I

Re: Panic in fork()

2003-02-14 Thread Alfred Perlstein
* Kris Kennaway [EMAIL PROTECTED] [030214 13:19] wrote: On Sat, Feb 08, 2003 at 02:04:56PM -0800, Kris Kennaway wrote: OK, I suspected that. tjr was looking into this last night and proposed the following patch: http://people.freebsd.org/~tjr/kf.diff OK, I got another panic with

Re: Panic in fork()

2003-02-14 Thread Kris Kennaway
On Fri, Feb 14, 2003 at 02:05:11PM -0800, Alfred Perlstein wrote: * Kris Kennaway [EMAIL PROTECTED] [030214 13:19] wrote: On Sat, Feb 08, 2003 at 02:04:56PM -0800, Kris Kennaway wrote: OK, I suspected that. tjr was looking into this last night and proposed the following patch:

Re: Panic in fork()

2003-02-09 Thread Thomas Moestl
On Sun, 2003/02/09 at 14:39:36 +1100, Tim Robbins wrote: On Sat, Feb 08, 2003 at 02:04:56PM -0800, Kris Kennaway wrote: On Sat, Feb 08, 2003 at 04:12:26PM +0100, Thomas Moestl wrote: addr2line will usually point to the first line of a statement if it spans multiple lines; in this

Re: Panic in fork()

2003-02-08 Thread Morten Rodal
On Sat, Feb 08, 2003 at 01:24:06AM -0800, Kris Kennaway wrote: Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 0100 fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01a1e2d stack pointer

Re: Panic in fork()

2003-02-08 Thread Kris Kennaway
On Sat, Feb 08, 2003 at 01:24:06AM -0800, Kris Kennaway wrote: Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 0100 fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01a1e2d stack pointer

Re: Panic in fork()

2003-02-08 Thread Morten Rodal
On Sat, Feb 08, 2003 at 03:05:12AM -0800, Kris Kennaway wrote: bento# addr2line -e kernel.debug 0xc01a1e2d ../../../kern/kern_fork.c:388 for (; p2 != NULL; p2 = LIST_NEXT(p2, p_list)) { PROC_LOCK(p2); 388 -- while (p2-p_pid == trypid

Re: Panic in fork()

2003-02-08 Thread Kris Kennaway
On Sat, Feb 08, 2003 at 04:12:26PM +0100, Thomas Moestl wrote: addr2line will usually point to the first line of a statement if it spans multiple lines; in this case, the full guard is: while (p2-p_pid == trypid || p2-p_pgrp-pg_id == trypid ||

Re: Panic in fork()

2003-02-08 Thread Tim Robbins
On Sat, Feb 08, 2003 at 02:04:56PM -0800, Kris Kennaway wrote: On Sat, Feb 08, 2003 at 04:12:26PM +0100, Thomas Moestl wrote: addr2line will usually point to the first line of a statement if it spans multiple lines; in this case, the full guard is: while (p2-p_pid

Re: panic in fork() on SMP 5.0-RELEASE

2003-01-27 Thread John Baldwin
On 25-Jan-2003 Nate Lawson wrote: On Sat, 25 Jan 2003, Morten Rodal wrote: The system is running 5.0-RELEASE with a pretty standard kernel (just removed all the drivers I don't use and added SMP support). I think the load of the system might have been high at the moment as I had just

RE: panic in fork() on SMP 5.0-RELEASE

2003-01-27 Thread John Baldwin
On 25-Jan-2003 Morten Rodal wrote: Is this a known panic? I tried to search the mailinglist archives to see if somebody had posted something similar, but I couldn't find anything. The system is running 5.0-RELEASE with a pretty standard kernel (just removed all the drivers I don't use and

Re: panic in fork() on SMP 5.0-RELEASE

2003-01-27 Thread Morten Rodal
On Mon, Jan 27, 2003 at 03:27:00PM -0500, John Baldwin wrote: Do you still have the kernel.debug from this kernel lying around? Can you pop gdb up on it and do 'l *0xc01bdb48' please? That is the instruction pointer from the fault and will give the line that the actual panic occurred at.

Re: panic in fork() on SMP 5.0-RELEASE

2003-01-27 Thread John Baldwin
On 27-Jan-2003 Morten Rodal wrote: On Mon, Jan 27, 2003 at 03:27:00PM -0500, John Baldwin wrote: Do you still have the kernel.debug from this kernel lying around? Can you pop gdb up on it and do 'l *0xc01bdb48' please? That is the instruction pointer from the fault and will give the line

Re: panic in fork() on SMP 5.0-RELEASE

2003-01-25 Thread Nate Lawson
On Sat, 25 Jan 2003, Morten Rodal wrote: The system is running 5.0-RELEASE with a pretty standard kernel (just removed all the drivers I don't use and added SMP support). I think the load of the system might have been high at the moment as I had just started cd /usr/ports make -j8 clean

Re: panic in fork() on SMP 5.0-RELEASE

2003-01-25 Thread Morten Rodal
On Sat, Jan 25, 2003 at 12:38:28PM -0800, Nate Lawson wrote: The question is, why? I suspect something to do with memory due to the second two bytes being a valid kernel address. How about a dmesg? [forgot to cc: [EMAIL PROTECTED]] Are you suspecting faulty memory? See attached dmesg.boot.