Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Feb 2018 12:35:50 -0800
From:      Gleb Smirnoff <glebius@FreeBSD.org>
To:        Juan =?iso-8859-1?Q?Ram=F3n?= Molina Menor <listjm@club.fr>
Cc:        freebsd-current@freebsd.org, manfredantar@gmail.com
Subject:   Re: Panic on Boot - Current AMD64
Message-ID:  <20180207203550.GM1063@FreeBSD.org>
In-Reply-To: <ecc36195-7ff9-5645-3507-94c0c48c3c89@club.fr>
References:  <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> <ecc36195-7ff9-5645-3507-94c0c48c3c89@club.fr>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 07, 2018 at 12:18:26PM +0100, Juan Ramón Molina Menor wrote:
J> > Same panic here with HEAD from this afternoon in a Lenovo ThinkPad S440 
J> > with 4 GB.
J> > 
J> > Workaround: break into the loader prompt and:
J> > 
J> > set vm.boot_pages=120
J> > boot
J> > 
J> > When booting kernel.old, vm.boot_pages is 64.
J> > 
J> > There is something wrong with r328916.
J> 
J> Recent commits 328955, 328953 and 328952 by glebius@ do not resolve the 
J> issue here.

r328982 should fix the boot without specifing vm.boot_pages.

I'm sorry for problems.

-- 
Gleb Smirnoff



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180207203550.GM1063>