[Bug 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 23 Dec 2024 22:03:31 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028 --- Comment #287 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to George Mitchell from comment #286) The variations I was looking at at are for vmcore.1 and vmcore.3 , for example. The load ordering did not vary but detailed address involved in the found_modules list do vary. Nothing you did caused any problems. It is just that booting is not sequential/deterministic in detail. In one respect, this variability contrasts with the stability of the odd 0xfffff80000000007 value that shows up part way through the list for the failing boots. (We have yet to get an example that was associated with a different list. But there are older back-traces for such.) The mini dumps have holes in what is searchable and I'm not finding it practical to look for nodes from the list that can no longer be reached because of the 0xfffff80000000007 but that likely would still be well formed if found (likely not explicitly deleted). It is getting to the point that if it was a local, personal problem I was having, I'd probably make tailored diagnostic-information additions to the kernel so that I could see more related information in the vmcore.* files (or elsewhere). I've not identified any more to try with just after- the-failure content for what is currently recored in the vmcore.* files, at least for the found_modules list related failures that are usually seen. -- You are receiving this mail because: You are on the CC list for the bug.