Date: Tue, 10 Dec 2024 17:03:05 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Message-ID: <bug-267028-227-siS2W1sV3K@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267028-227@https.bugs.freebsd.org/bugzilla/> References: <bug-267028-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=3D267028 --- Comment #195 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to George Mitchell from comment #192) As for having a swap partition ready for use for dumping as early as possible: assign dumpdev in /boot/loader.conf . An example from one of my contexts: # grep -i dump /boot/loader.conf dumpdev=3D"/dev/gpt/OptBswp364" The kernel does have to be far enough along to put it to use but the above is the only way to have things configured for the earliest point at which dumping is supported, as far as I know. For dumping to swap partitions and this earlier time frame, to my knowledge single user mode vs. not boot attempts would not make a difference. Actually, the above may do one thing that interferes: /dev/gpt/ use might not be the best idea for earliest possible dumps. Use an exact device reference instead. In my context, as it is now, /dev/gpt/OptBswp364 is actually /dev/nda2p2 . So: dumpdev=3D"/dev/nda2p2" would likely be better for earliest-dump-possible in my context. --=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-267028-227-siS2W1sV3K>