Date: Mon, 12 Aug 2019 11:38:29 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig Message-ID: <bug-239245-227-fU8IfBQ9PY@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=3D239245 Alfredo Dal'Ava J=C3=BAnior <alfredo.junior@eldorado.org.br> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luporl@FreeBSD.org --- Comment #59 from Alfredo Dal'Ava J=C3=BAnior <alfredo.junior@eldorado.o= rg.br> --- I can reproduce similar issue (same stack on panic) on QEMU using the follo= wing steps: 1 - take a clean-installed FreeBSD 12 RELEASE 2 - get src at r350672; 3 - buildkernel 4 - installkernel 5 - shutdown -r now It's not reproduced all the times, reproduce rate is bellow 20%. Looking at= my continuous integration logs, I see this panic first appearing on early June. For the record: - commenting out NUMA option on kernel config file will workaround it. - NUMA feature was introduced/made default in early April, two months before the first time my testbed hit the issue for the first time. So it doesn't appear like a bug in the original code. Something between April and June has changed it, or maybe triggered it. - Once panics, QEMU system_reset will hit the panic again. Closing QEMU and starting it again will make it boot. (power cycle?) - Once the panic, if I do QEMU system_reset and make loader boot the old (FreeBSD 12) kernel, it works fine. If I issue reboot and load the new kern= el (that was just built), the panic is hit again. (something like a bad persis= tent state affecting only the new kernel, that only disappears after closing QEM= U). --=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-239245-227-fU8IfBQ9PY>