https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245
Alfredo Dal'Ava Júnior <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #59 from Alfredo Dal'Ava Júnior <[email protected]> --- I can reproduce similar issue (same stack on panic) on QEMU using the following 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 kernel (that was just built), the panic is hit again. (something like a bad persistent state affecting only the new kernel, that only disappears after closing QEMU). -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
