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:  

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

2017-11-15 Thread Andy Ruhl
Thanks for all of the responses!

On Wed, Nov 15, 2017 at 8:52 AM, Robert Elz  wrote:
>   | I rebooted and confirmed that it works (other than complaints about
>   | the disks which don't exist). ACPI appears to be working.
>
> NetBSD- (Beta) will have a newer ACPI in it than your old -7 kernel.

I'm actually using netbsd-8 from the 201711131530Z directory on nyftp.
I downloaded the install kernel from there and then did a full install
from the ftp site.

I tried booting with and without -2 and I'm not sure if it affects the
new problem I'm having.

>
>   | So now it hangs here:
>   | http://acruhl.freeshell.org/netbsd_wont_boot2.jpg
>   |
>   | (last message is kern.module.path=/stand/i386/8.0/modules)
>
> That's the last of the normal kernel printfs during boot, at that point,
> init should be running, and running /etc/rc
>
> If I had to guess, I'd say that your /dev/console isn't correct, as the
> next messages should be appearing there.   Check what's there (using the
> method you used to install to get your real root filesystem mounted and
> visible.)

I booted the install kernel and mounted the root disk and did sh
MAKEDEV all in /mnt/dev and it seems to have got me past that point.

Now I see "white" boot messages, but it sometimes hangs in fsck,
probably on /dev/rwd0e which is /usr. This happens if I use the
generic kernel I just installed or with the install kernel and do fsck
manually on /dev/wd0e.

Here's the hokey part. Sometimes ctrl-c hangs. Sometimes it dumps me
back to a prompt. Sometimes it panics.

If I boot with "boot -1 -2" it seems to solve the hangs during fsck,
but I'm not 100% sure about that.

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

I think this is SMP related, but I'm not sure.

I got 2 panics that looked pretty similar to this when I did ctrl-c
during fsck which seemed to hang.

Andy