Bug 269726 - kern.msgbufsize=4587520 in loader.conf, kernel never boots
Summary: kern.msgbufsize=4587520 in loader.conf, kernel never boots
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: arm (show other bugs)
Version: CURRENT
Hardware: arm64 Any
: --- Affects Only Me
Assignee: freebsd-arm (Nobody)
URL: https://reviews.freebsd.org/D42734
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-21 00:38 UTC by Bjoern A. Zeeb
Modified: 2023-11-27 19:55 UTC (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bjoern A. Zeeb freebsd_committer freebsd_triage 2023-02-21 00:38:51 UTC 
Hi,

set kern.msgbufsize=4587520 in loader.conf on an arm64 system with 16G of RAM and after boot -v no kernel ever showed up.

This is loader.efi from a few weeks ago I assume.  I can dig into anything if needed.
Comment 1 Warner Losh freebsd_committer freebsd_triage 2023-02-21 06:59:11 UTC 
just out of curiosity, does 1MB or 512k have this same issue?
Comment 2 Bjoern A. Zeeb freebsd_committer freebsd_triage 2023-02-21 10:01:28 UTC 
1M does not.  That's my normal default :)  I was wondering if PAGE_SIZE had anything to do with it but haven't tried something just below that.  Should I?
Comment 3 Andrew Turner freebsd_committer freebsd_triage 2023-02-21 15:16:57 UTC 
We only allocate a small virtual address range for early kernel use. The msgbuf is allocated from this so when larger is overflowing this allocation. We could probably use the new pmap bootstrap code to handle this, although it's not something I've planned on doing.