Re: wapbl panic on new system with too much memory!

[Paul Goyette <paul%whooppee.com@localhost>]

On Wed, 7 Sep 2016, Roy Marples wrote:

> On 07/09/2016 09:48, Roy Marples wrote:
> > On 06/09/2016 08:39, Paul Goyette wrote:
> > > I'm in the process of installing a new machine, and I'm getting a
> > > reproducible panic at boot time.
> > >
> > > The machine is a Intel Core i7-6900 (8 cores, 16 threads, 3.2GHz) on an
> > > ASUS X99-E motherboard.  It is fully-populated with 8 x 16GB DDR4 DIMMs
> > > (for a total, yes, of 128GB!).
> > >
> > > Basically, I cloned the hard drive of my other machine using dd, and
> > > then put the copy in the new machine, and booted.  It comes up fine in
> > > single-user mode.  However, shortly after typing ^D to the single-user
> > > shell, it fails a KASSERT at sys/kern/vfs_wapbl.c line 1088.  The
> > > following is manually transcribed:
> >
> > I just replicated the same panic on a low memory and old T500 laptop.
> > I too booted single user mode, mounted / rw, editied /etc/rc.conf,
> > exited and then the system paniced after printing "Starting file system
> > checks:"
>
> So replicating it again, to prove it's consistent (which it is) has now
> stopped my system booting entirely.
> It now panics at each boot in ffs_newvnode dup alloc ino=blahblah
>
> I had to boot single user and fsck to clean up all errors and it boots
> once more.

Are you able to test the possible fix that was proposed?


+------------------+--------------------------+------------------------+
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:      |
| (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com   |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
+------------------+--------------------------+------------------------+