Date: Tue, 4 Feb 2020 17:33:34 -0800 From: Mark Millard <marklmi@yahoo.com> To: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: head -r357529 for 32-bit powerpc on 64-bit PowerMac: boot fails for getnewbuf_empty: locked buf 0xd2800000 on freequeue Message-ID: <99E20FB7-69EB-44B9-9167-6017810D4AE6@yahoo.com> In-Reply-To: <37F12B38-B4E7-472B-B337-0C45880541CC@yahoo.com> References: <37F12B38-B4E7-472B-B337-0C45880541CC@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Feb-4, at 15:25, Mark Millard <marklmi@yahoo.com> wrote: > The old PowerMac happens to be a 64-bit capable one > but the FreeBSD is the 32-bit variant. It boots on the 32-bit PowerMac example. It panics on the two examples of 64-bit types of PowerMac, both types dual socket but 1 core each vs. 2 cores each. The kernel and world were non-debug builds (with symbols). > The backtrace goes like: > (typed from a screen picture) > > . . . > panic > getnewbug Typo above, should have been: getnewbuf > getblkx > breadn_flags > ffs_use_bread > readsuper > ffs_sbget > ffs_mount > vfs_domount > vfs_donmount > kernel_mount > parse_mount > vfs_mountroot > start_init > fork_exit > fork_trampoline So I installed the artifact.ci.freebsd.org -r357545 kernel and kernel-dbg (-r357529 was not available). But is failed earlier for the example 64-bit PowerMac tried. 32-bit booted okay. But I'll report details for this one in a separate submittal for the earlier problem. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99E20FB7-69EB-44B9-9167-6017810D4AE6>