Re: New Fatal trap in Current SMP (random.dev changes ??)

2000-09-11 Thread Bruce Evans
On Sun, 10 Sep 2000, John Baldwin wrote: > I've got it fixed. The code is using TAILQ_REMOVE and TAILQ_FIRST to > pull entries out of a tailq while it is walking it via TAILQ_FOREACH. > Changing it to use a while(!TAILQ_EMPTY) instead of using TAILQ_FOREACH > fixes it. I'll be committing the fi

Re: New Fatal trap in Current SMP (random.dev changes ??)

2000-09-11 Thread Bruce Evans
On Sun, 10 Sep 2000, John Baldwin wrote: > Boris Popov wrote: > > Yes, after trap is occured ddb works. But it is impossible to > > continue from ddb because after typing 'c' machine becomes frozen. > > The same thing occur after any other panic (this is with SMP kernel). > > It only does th

Re: New Fatal trap in Current SMP (random.dev changes ??)

2000-09-10 Thread Mark Murray
> > And the panic goes away > > Manfred > > I've got it fixed. The code is using TAILQ_REMOVE and TAILQ_FIRST to > pull entries out of a tailq while it is walking it via TAILQ_FOREACH. > Changing it to use a while(!TAILQ_EMPTY) instead of using TAILQ_FOREACH > fixes it. I'll be committing the f

Re: New Fatal trap in Current SMP (random.dev changes ??)

2000-09-10 Thread John Baldwin
Boris Popov wrote: > On Sun, 10 Sep 2000, John Baldwin wrote: > > > > I think the random dev kicks in at this point > > > > > > Fatal trap 12: page fault while in kernel mode > > > cpuid = 1; lapic.id = 0c00 > > > fault virtual address = 0x2c > > > fault code= supervisor read

Re: New Fatal trap in Current SMP (random.dev changes ??)

2000-09-10 Thread Boris Popov
On Sun, 10 Sep 2000, John Baldwin wrote: > > I think the random dev kicks in at this point > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 1; lapic.id = 0c00 > > fault virtual address = 0x2c > > fault code = supervisor read, page not present > > instruction pointe

Re: New Fatal trap in Current SMP (random.dev changes ??)

2000-09-10 Thread John Baldwin
Manfred Antar wrote: > At 08:16 PM 9/10/2000 -0700, John Baldwin wrote: > >Manfred Antar wrote: > >> >From a new kernel compiled from sources current 7:30 pm 9/10/00 pacific time > >> Although the first occurrence happened this morning after compiling a kernel > >> after the random dev changes. >

Re: New Fatal trap in Current SMP (random.dev changes ??)

2000-09-10 Thread Manfred Antar
At 08:16 PM 9/10/2000 -0700, John Baldwin wrote: >Manfred Antar wrote: >> >From a new kernel compiled from sources current 7:30 pm 9/10/00 pacific time >> Although the first occurrence happened this morning after compiling a kernel >> after the random dev changes. >> The system boots and mounts d

Re: New Fatal trap in Current SMP (random.dev changes ??)

2000-09-10 Thread John Baldwin
Manfred Antar wrote: > >From a new kernel compiled from sources current 7:30 pm 9/10/00 pacific time > Although the first occurrence happened this morning after compiling a kernel > after the random dev changes. > The system boots and mounts disks. When it gets to this point: > Additional routing

New Fatal trap in Current SMP (random.dev changes ??)

2000-09-10 Thread Manfred Antar
>From a new kernel compiled from sources current 7:30 pm 9/10/00 pacific time Although the first occurrence happened this morning after compiling a kernel after the random dev changes. The system boots and mounts disks. When it gets to this point: Additional routing options: TCP extensions=NO TCP