Date: Thu, 21 May 2020 19:21:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 246638] panic on boot: "cannot find a large enough size" Message-ID: <bug-246638-227-nr1PdQluwV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-246638-227@https.bugs.freebsd.org/bugzilla/> References: <bug-246638-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246638 --- Comment #8 from Conrad Meyer <cem@freebsd.org> --- (In reply to Rafael Kitover from comment #7) Probably the 34MB is wrongly carved from some other domain to not have an unpopulated domain 0. Is it possible the DIMMS are installed in an order n= ot recommended by the motherboard vendor? Usually crappy board video chips ju= st borrow some system RAM, and that allocation wouldn't be visible to the host= OS (IIRC). Re: capturing earlier bootup logs, you can put 'kern.msgbufsize=3D"512k"' in /boot/loader.conf (or similar) to use a larger-than-default msgbufsize. The default msgbuf size on CURRENT and STABLE/12 is 96 kB unless configured otherwise. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246638-227-nr1PdQluwV>