Date: Tue, 16 Jul 2019 18:41:37 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239245] r350026 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig Message-ID: <bug-239245-227-jefV05P1By@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239245-227@https.bugs.freebsd.org/bugzilla/> References: <bug-239245-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=239245 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #7 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Johnston from comment #5) I tried but failed to repeat the original problem first: it booted just fine, making such output from my context probably not all that useful. Details follow. I grabbed materials from: https://artifact.ci.freebsd.org/snapshot/head/r350055/powerpc/powerpc64/ and put themn on a SSD parition for a 16 GiByte PowerMac G5 quad. It was unchanged, not even editing of /etc/fstab : just tar expansion of the .txz files after a newfs -U -t . (So I had to enter ufs:/dev/ada0s3 when prompted.) But it booted just fine. Interestingly, uname -apKU reports itself as being r350056 (not r350055). The revision.txt showed r350055. (So artifact's version indications can be wrong?) Possibilities for why it boots include: A) The amount of RAM matters. B) Some FreeBSD configuration that causes differing activity matters. C) ? -- 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-239245-227-jefV05P1By>