Date: Sun, 21 Apr 2013 14:27:49 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Ganbold Tsagaankhuu <ganbold@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: panic when booting HEAD on i386 Message-ID: <20130421112749.GF67273@kib.kiev.ua> In-Reply-To: <CAGtf9xO%2Bh-hhZ516VJrgfd4XbN0dk6EAOWM_hc8QM5qAoEJ3mA@mail.gmail.com> References: <CAGtf9xO3wd8WxtzT-zT0LAk9qi0y01Zg_iA6yx%2B85Z4f7kJJEA@mail.gmail.com> <20130420152102.GC67273@kib.kiev.ua> <CAGtf9xO%2Bh-hhZ516VJrgfd4XbN0dk6EAOWM_hc8QM5qAoEJ3mA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--b8GWCKCLzrXbuNet Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 21, 2013 at 01:57:03PM +0800, Ganbold Tsagaankhuu wrote: > On Sat, Apr 20, 2013 at 11:21 PM, Konstantin Belousov > <kostikbel@gmail.com>wrote: >=20 > > On Sat, Apr 20, 2013 at 10:52:35PM +0800, Ganbold Tsagaankhuu wrote: > > > Hi, > > > > > > I'm trying to boot HEAD after updating, but unfortunately it panics w= ith > > > following message: > > > > > > panic: kmem_suballoc: bad status return of 3. > > > > > > I was only able to get image of the panic. > > > > > > http://www.mnbsd.org/ganbold/IMG_20130420_222353-2.jpg > > > > > > Does anybody see same panic booting on i386 lately? > > > Tried clang, and it panics also. > > > > How much memory do you have ? > > Do you have any tunables in the loader.conf ? > > >=20 > Following settings caused the panic: >=20 > vm.kmem_size=3D"999M" > vm.kmem_size_max=3D"999M" I cannot imagine how this could work earlier as well, except by chance. >=20 > Whether it is regression or not in previous version of kernel (r244046) it > didn't panic on boot. > Seems no information on UPDATING either. Do you propose to enumerate all non-working or panic-provoking settings in loader.conf ? Why did you set this value at all ? KVA on i386 is limited to slightly less then 1GB, where all the kernel maps must be instantiated. Kernel uses the value of the tunable vm.kmem_size literally, except it makes a mild attempt to prevent foot-shooting by capping kmem_size to 2 * physical memory size. You neglected to answer how much memory is installed on your machine, but I suspect you have enough so that overblown kmem_map cannot coexists with other kernel VA consumers. --b8GWCKCLzrXbuNet Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRc801AAoJEJDCuSvBvK1BPAwQAKpE/rjQTlNB1+uqhBJAmhlm HV/jcDb0OVi/O1A8LW4fAZCvdnvenutGYU6izuR+t85c4S55xOt/uwJak+oFOb21 rbisvNw6FPRczd1djPINqTo+8HYeO4ijkxjK9LYpUyJJrmsudy5A5zWvurYkNGPs G8XA6oDBh8jrEKRBaWCP69nSgEh4QiDgyB1leBVGj4XD33pCn4ISTSMKxgjdbqzw s9FVjUFENLSjXf7CEKNJvfivmJOVZgCR+A6SYBK8O+S2cZ8BS4gM9MRj5s7eFwsu oZ2RMrRcWvSCeWPy4ig6eK33rSAT5CU/gsOZ/+j7yvN2QGnbAfRqEcGolJ1tygTz dWRKywhTXR/JHwbyL4v9msiS0aTt4vx2HlvjQBrYaEpk4VBPBPqf7C9QjOc678iZ tM0MaLnevJpNDeAU25w8pbpnJca9CrWTjTsPCk7bsHcJ0IhidXYA3F94SuMghHvc BZHlE03P25F6WC2J8iibdu8dpX7qcFg8h7Rubi1Q6Xt+Mt8V+jI2Dp4/a36taARY o4s1tZWcNOkW5EAQv0qLmnFfHbkzCkI9u4S0PK04WKpvgD38HL4bp3lVN7yo06Mo 5MsLpAsqq0HjjUmbqprw6GqB8s83g9LOzZptmhJs7ScTO16Jb0sCkuVB9VHXV2WL LPbtTXb/pwGqv7femAVV =D8pm -----END PGP SIGNATURE----- --b8GWCKCLzrXbuNet--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130421112749.GF67273>