Fixed ! Re: Interesting panic very early in the boot

2002-07-18 Thread Szilveszter Adam
Hello everybody, I would like to report that after incorporating today's fixes into the kernel source and recompiling, the panic does not occur again. This is probably due to the commit to pmap.c (rev 1.345 by Peter Wemm). Although the log only talks about SMP, this UP box likes it too. So

Re: Fixed ! Re: Interesting panic very early in the boot

2002-07-18 Thread Bosko Milekic
On Thu, Jul 18, 2002 at 07:38:39PM +0200, Szilveszter Adam wrote: Hello everybody, I would like to report that after incorporating today's fixes into the kernel source and recompiling, the panic does not occur again. This is probably due to the commit to pmap.c (rev 1.345 by Peter Wemm).

Re: Fixed ! Re: Interesting panic very early in the boot

2002-07-18 Thread Szilveszter Adam
On Thu, Jul 18, 2002 at 01:40:48PM -0400, Bosko Milekic wrote: As pointed out, the change was fairly bogus. There's a new change that should be committed soon that fixes the problem in a sort of less bogus way. When Peter gets around to reviewing it, it'll be committed and you

Re: Interesting panic very early in the boot

2002-07-17 Thread Szilveszter Adam
On Wed, Jul 17, 2002 at 09:57:41AM -0700, Bakul Shah wrote: Terry suggested: I believe setting DISABLE_PSE in the config file and rebuilding will make this go away. Terry, thanks for the suggestion but that didn't do it. Ok, so it's time to speculate a bit more about this. Although I

Re: Interesting panic very early in the boot

2002-07-17 Thread Bakul Shah
I believe setting DISABLE_PSE in the config file and rebuilding will make this go away. Terry, thanks for the suggestion but that didn't do it. Time to review recent changes and single step the kernel. BTW, how do you stop the kernel before it panics? It panics so early that there is no time

Re: Interesting panic very early in the boot

2002-07-17 Thread Terry Lambert
Bakul Shah wrote: I believe setting DISABLE_PSE in the config file and rebuilding will make this go away. Terry, thanks for the suggestion but that didn't do it. This surprises me. I thought it would be the result of Peter's recent pmap changes, and the fact that there is a bad problem

Re: Interesting panic very early in the boot

2002-07-17 Thread Terry Lambert
Szilveszter Adam wrote: Ok, so it's time to speculate a bit more about this. Although I have been seeing this panic since Sunday, only one other person has reported it so far. Although it may be that this is due to the fact that developers do not run up-to-date -CURRENT and hence do not

Re: Interesting panic very early in the boot

2002-07-17 Thread Szilveszter Adam
On Wed, Jul 17, 2002 at 07:38:22PM +0200, Szilveszter Adam wrote: Bakul mentioned that the panic happens on a PPro. For me, it's a PII. I am using a CPUTYPE setting of p2 in /etc/make.conf. This gets converted to a -march=pentiumpro on the actual compile line. This may be the same for the

Re: Interesting panic very early in the boot

2002-07-17 Thread Szilveszter Adam
On Wed, Jul 17, 2002 at 11:35:35AM -0700, Terry Lambert wrote: My bet on the root cause, if I am correct, means that if you change the amount of physical RAM installed in the machine, the problem will go away, and that the problem is probably rare because it depends on certain things that are

Re: Interesting panic very early in the boot

2002-07-17 Thread Terry Lambert
Szilveszter Adam wrote: On Wed, Jul 17, 2002 at 11:35:35AM -0700, Terry Lambert wrote: My bet on the root cause, if I am correct, means that if you change the amount of physical RAM installed in the machine, the problem will go away, and that the problem is probably rare because it depends

Re: Interesting panic very early in the boot

2002-07-17 Thread Bakul Shah
That there could be a real error in that code surprises me, since Peter really knows what he's doing, even if that low in the hardware, there are undocumented interactions that even Intel's errata doesn't seem to know about. Turns out the workaround is to use DISABLE_PG_G. Two things made

Re: Interesting panic very early in the boot

2002-07-16 Thread Bakul Shah
I've run into a very similar bug -- the kernel panics almost right after it is started by the loader. With remote gdb I've traced it to this point so far: (kgdb) target remote /dev/cuaa0 Remote debugging using /dev/cuaa0 pmap_set_opt () at /usr/src/sys/i386/i386/pmap.c:449 449

Re: Interesting panic very early in the boot

2002-07-16 Thread Terry Lambert
Bakul Shah wrote: I've run into a very similar bug -- the kernel panics almost right after it is started by the loader. With remote gdb I've traced it to this point so far: I believe setting DISABLE_PSE in the config file and rebuilding will make this go away. -- Terry To Unsubscribe: send

Interesting panic very early in the boot

2002-07-14 Thread Szilveszter Adam
Hello everybody, I have recently finished to upgrade my system to today morning's -CURRENT, with sources just *before* the commit of rev 1.154 to src/sys/kern/kern_fork.c by Julian. I have an UP IA32 machine, I am not using any additional kernel modules, and now, upon rebooting with the new

Re: Interesting panic very early in the boot

2002-07-14 Thread Szilveszter Adam
On Sun, Jul 14, 2002 at 07:49:57PM +0200, Szilveszter Adam wrote: Hello everybody, I have recently finished to upgrade my system to today morning's -CURRENT, with sources just *before* the commit of rev 1.154 to src/sys/kern/kern_fork.c by Julian. I have an UP IA32 machine, I am not

Re: Interesting panic very early in the boot

2002-07-14 Thread Szilveszter Adam
On Sun, Jul 14, 2002 at 08:06:49PM +0200, Szilveszter Adam wrote: On Sun, Jul 14, 2002 at 07:49:57PM +0200, Szilveszter Adam wrote: Hello everybody, I have recently finished to upgrade my system to today morning's -CURRENT, with sources just *before* the commit of rev 1.154 to

Re: Interesting panic very early in the boot

2002-07-14 Thread Julian Elischer
you can use addr2line to get info, but at a pinch you can just use nm -n to figure out what function each address is in. On Sun, 14 Jul 2002, Szilveszter Adam wrote: Hello everybody, I have recently finished to upgrade my system to today morning's -CURRENT, with sources just *before* the