Re: Netbsd-7/i386 won't boot on new motherboard/CPU
On Thu, Nov 16, 2017 at 5:10 PM, ssartorwrote: > Kind of a ‘me too’ but I just bought a Zotac Zbox Ci327 for use as a small > home office server/firewall. Like your MSI board, it has a newer generation > CPU, in this case a Celeron N3450 quad-core (Apollo Lake, Goldmont > architecture, slightly older than Kaby Lake). In my case, neither NetBSD 7, > 8 or current would boot — always died with a ‘cpu 1: failed to start’ > message. After some poking around I found I could boot the machine by turning > off SMP (boot -1). It’s running fine now on NetBSD 7 but it does seem as if > current generation Intel parts are problematic. I built a new netbsd-8 kernel (with source from about the same time as the binaries I used to install) and the only difference from GENERIC is I enabled PAE in the config. It now runs fine with smp and acpi enabled. No idea why it was so unstable before. Andy
Re: NetBSD-8/i386 SMP Panic? (was: Re: Netbsd-7/i386 won't boot on new motherboard/CPU)
Date:Thu, 16 Nov 2017 07:16:32 -0700 From:Andy RuhlMessage-ID:
Re: NetBSD-8/i386 SMP Panic? (was: Re: Netbsd-7/i386 won't boot on new motherboard/CPU)
On Thu, Nov 16, 2017 at 3:53 AM, Robert Elzwrote: 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)
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)
Date:Wed, 15 Nov 2017 20:48:14 -0700 From:Andy RuhlMessage-ID:
NetBSD-8/i386 SMP Panic? (was: Re: Netbsd-7/i386 won't boot on new motherboard/CPU)
Thanks for all of the responses! On Wed, Nov 15, 2017 at 8:52 AM, Robert Elzwrote: > | 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
Re: Netbsd-7/i386 won't boot on new motherboard/CPU
On Wed, Nov 15, 2017 at 08:02:44AM -0700, Andy Ruhl wrote: > > http://acruhl.freeshell.org/netbsd_wont_boot2.jpg > > (last message is kern.module.path=/stand/i386/8.0/modules) > > I don't know what's happening at this point. Hi Andy, If you have a PS/2 keyboard you should be able to use ddb (ctrl+alt+escape), and see where it's stuck. Another option is boot -d (in the boot prompt) if I'm wrong about the string to enter ddb.
Re: Netbsd-7/i386 won't boot on new motherboard/CPU
Date:Wed, 15 Nov 2017 08:02:44 -0700 From:Andy RuhlMessage-ID: | This is what I've done so far: | Before the reboot I unplugged all disks except the root disk, which is | partitioned "old style" with separate partitions for /, /usr, /tmp, | and /var Perfectly reasonable "new style" too... | 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. | 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.) | (P.S. - For people new to NetBSD, disregard all of this. These are all | "old man" problems. Right up my bailiwick... kre
Re: Netbsd-7/i386 won't boot on new motherboard/CPU
On Wed, Nov 15, 2017 at 6:35 AM, Robert Elzwrote: > Date:Wed, 15 Nov 2017 06:03:40 -0700 > From:Andy Ruhl > Message-ID: > > > | I can't seem to make this motherboard's BIOS disable ACPI. > > The intent was to disable it in NetBSD via the boot prompt - but that > is only possible if your boot.cfg (on the netbsd-7 root) was set up to > give the menu and wait a few seconds for you to interrupt. > > If you don't have a menu entry for booting with ACPI disabled, you should > still be able to boot manually from the boot prompt, just give > netbsd the "-2" option. Ok, I sort of got past that but it might still be an issue. This is what I've done so far: Booted the Netbsd-8 installer, used the /bin/sh prompt to mount the internal disk and configure a USB network interface. I put an install kernel in the root of the boot disk and rebooted. Interruped the bootloader and booted the install kernel. Before the reboot I unplugged all disks except the root disk, which is partitioned "old style" with separate partitions for /, /usr, /tmp, and /var The installer complained about the disks it couldn't find but eventually I upgraded to netbsd-8. I rebooted and confirmed that it works (other than complaints about the disks which don't exist). ACPI appears to be working. So now it hangs here: http://acruhl.freeshell.org/netbsd_wont_boot2.jpg (last message is kern.module.path=/stand/i386/8.0/modules) I don't know what's happening at this point. Andy (P.S. - For people new to NetBSD, disregard all of this. These are all "old man" problems. Don't be discouraged by this nonsense! Just use amd64 like normal people.)
Re: Netbsd-7/i386 won't boot on new motherboard/CPU
Date:Wed, 15 Nov 2017 06:03:40 -0700 From:Andy RuhlMessage-ID: | I can't seem to make this motherboard's BIOS disable ACPI. The intent was to disable it in NetBSD via the boot prompt - but that is only possible if your boot.cfg (on the netbsd-7 root) was set up to give the menu and wait a few seconds for you to interrupt. If you don't have a menu entry for booting with ACPI disabled, you should still be able to boot manually from the boot prompt, just give netbsd the "-2" option. kre
Re: Netbsd-7/i386 won't boot on new motherboard/CPU
On Wed, Nov 15, 2017 at 2:00 AM, Benny Siegertwrote: >> The kernel boots just past the first acpi message and then just sits >> there "forever" (minutes is all I've waited). > > Try disabling ACPI. There is probably an option in the bootloader menu > to do that. I got a few private responses, thanks for that. Some more notes: I can't seem to make this motherboard's BIOS disable ACPI. >From here I have sort of "chicken and egg" problems. I wrote a i386/8.0 installer to a USB stick and it boots past the kernel (so no ACPI issues), but it wants me to tell it what root disk to use. I thought it would want to use the USB stick as the root. It only allows me to give it "wd0a", which has a netbsd-7 userland and no modules, so it just dumps me to a sh prompt. Found out I need to tell the USB stick's bootloader to disable ACPI and use no SMP (not sure about SMP though), then it boots semi properly. >From the /bin/sh I can't do "anything" though. I plugged in another USB stick with an 8.0 install kernel, but I can't figure out how to mount it. mount -t msdos /dev/sd1{a,d,e} /mnt doesn't work (Invalid argument for sd1d, others don't exist). Also, ifconfig only shows lo0, so no network adapter. I'll try putting another one in. I guess I could try netbooting using PXE from the BIOS. Was hoping it would be easier to get to 8.0 than that though. Still working on it. Andy
Re: Netbsd-7/i386 won't boot on new motherboard/CPU
> The kernel boots just past the first acpi message and then just sits > there "forever" (minutes is all I've waited). Try disabling ACPI. There is probably an option in the bootloader menu to do that.