Re: Reboot while booting with new per-CPU allocator

From: Stephane E. Potvin <sepotvin_at_videotron.ca>
Date: Fri, 17 Jun 2005 11:50:06 -0400
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Watson wrote:
> 
> On Fri, 17 Jun 2005, Eric Anderson wrote:
> 
>>> Interestingly, there's been a bunch of reports of this in the past
>>> few days, and there weren't immediately after the malloc commit.  I
>>> wonder if some other recent change has increased the amount of UMA
>>> memory allocated early in the boot, increasing the level of reports...
>>
>>
>>  Increase UMA_BOOT_PAGES to prevent a crash during initialization.  See
>>  http://docs.FreeBSD.org/cgi/mid.cgi?42AD8270.8060906 for a detailed
>>  description of the crash.
> 
> 
> Yeah, this is the fix, but I guess I'm wondering what caused a recent
> spate of problem reports -- was it a delayed response to the malloc
> change as people gradually upgraded, or some other recent kernel change
> that caused increase demand for memory.

Well, I had this problem since the day of the commit. I didn't had time to
investigate what was happening so I just reverted to an older known
working kernel. It might be a peculiarity of my setup that caused it to
fail earlier though.

Steph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCsvEumdOXtTCX/nsRAhuZAJ94ouxzf6Hl8O5QsStk4q7SG3WsgACdEGnO
xTRTl6Ypo/sccfcfaOU7Zgk=
=Km7g
-----END PGP SIGNATURE-----
Received on Fri Jun 17 2005 - 13:51:52 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:37 UTC