[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: Thu, 26 Dec 2024 01:11:14 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028 --- Comment #304 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to George Mitchell from comment #303) I moved all the information recording into static storage and eliminated the printf messages that I'd used before. The log showed no attempt to put a dump into the swap space. I figured the static storage would be less invasive. But it may just be differently invasive. It is possible that the memory layout differences have changed the behavior of the code (different bad memory places referenced, with different consequences. Similary, the recording of history would change the relative timing of potential race conditions and such but differently than all the activity for printf output. Nothing I did should be a valid fix, even if it accidentally improves things for you in some contexts. What I did presumes that you would not be unloading or reloading modules or such, for example. It is very specific to gathering information from the specifics of the context of failure, not for operation in general use. If this kernel does not produce the failure anywhere near as often, an interesting experiment might be to disable all use of the extra static storage but to leave the extra storage present: in essence, to only change the memory layout, not any operation. -- You are receiving this mail because: You are the assignee for the bug.