Re: NetBSD-8/i386 SMP Panic? (was: Re: Netbsd-7/i386 won't boot on new motherboard/CPU)

2017-11-16 Thread Robert Elz
Date:Thu, 16 Nov 2017 07:16:32 -0700
From:Andy Ruhl 
Message-ID:  

Re: NetBSD-8/i386 SMP Panic? (was: Re: Netbsd-7/i386 won't boot on new motherboard/CPU)

2017-11-16 Thread Andy Ruhl
On Thu, Nov 16, 2017 at 3:53 AM, Robert Elz  wrote:

Thanks, as always, for your detailed responses.

>   | I think this is SMP related, but I'm not sure.
>
> That might make the issue more likely to occur, but is probably not
> directly related (that is, the busier the system gets, the more likely
> the pmap issues are to happen).

Yes, the machine is nearly unusable when booting with SMP (I think). I
booted it with -1 -2 last night and it's still running this morning.
All it has done is a few cvs checkouts and updates though.

Another detail, not sure if it's related:

I have a wm network adapter and performance with it was horrible, I
was getting +4000ms pings to my gateway on a wired gigabit network. I
switched to USB3 gigabit adapter (cdce) and things are working
normally.

I am checking out -current right now and I will build a kernel and report back.

There are no PRs about this recently, I'm willing to open one for this
panic if this will help.

Andy


Re: NetBSD-8/i386 SMP Panic? (was: Re: Netbsd-7/i386 won't boot on new motherboard/CPU)

2017-11-16 Thread Martin Husemann
On Thu, Nov 16, 2017 at 05:53:49PM +0700, Robert Elz wrote:
>   | I took photos of the panic at:
>   | 
>   | http://acruhl.freeshell.org/netbsd-i386-8-panic1.jpg
>   | http://acruhl.freeshell.org/netbsd-i386-8-panic2.jpg
> 
> Those are UVM (x86 pmap) issues - there have been recent "issues" with
> some of that code.  I wasn't aware it had been pulled up to -8, but I
> guess it has.

No, the recent changes (that make -current pretty instable right now)
have NOT been pulled up.

Martin


Re: NetBSD-8/i386 SMP Panic? (was: Re: Netbsd-7/i386 won't boot on new motherboard/CPU)

2017-11-16 Thread Robert Elz
Date:Wed, 15 Nov 2017 20:48:14 -0700
From:Andy Ruhl 
Message-ID: