[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, 27 Feb 2023 20:02:46 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028 --- Comment #86 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to George Mitchell from comment #85) Where does dumpdev point for "test disk"? Someplace also on the "test disk" that a "regular disk" boot would not change? If yes, the first boot of the "test disk" after the crash should have picked up the dump information, even if the "regular disk" was booted between times. But if the dumpdev place is common to both types of boot, then the regular disk boot would have processed the dump. likely using a different /var/crash/ place to store things. Another question would be if there is sufficient room for /var/crash/ to contain the saved vmcore.* and related files. Yet another question is if the test disk has /usr/local/bin/gdb installed vs. not. ( When present, /usr/local/bin/gdb is used to provides one of the forms of backtrace, the one with source file references and line numbers and such. Much nicer to deal with.) If a vmcore.* was saved but some related information was not for some reason, it should be possible to have the related information produced based on the vmcore.* file. Side note: In case it is relevant, I'll note that defining dumpdev in /boot/loader.conf in a form the kernel chan handle, instead of in /etc/rc.conf , can be used to allow the system to produce dumps for earlier crashes. (But I'm guessing the crash was not that earliy to need such.) -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.