Date: Fri, 27 Aug 2021 13:19:46 +0000 From: bugzilla-noreply@freebsd.org To: ipfw@FreeBSD.org Subject: [Bug 255775] panic with ipfw turned on at boot time Message-ID: <bug-255775-8303-owgKdOogYr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255775-8303@https.bugs.freebsd.org/bugzilla/> References: <bug-255775-8303@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=3D255775 Mark Johnston <markj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |Closed Resolution|--- |Overcome By Events --- Comment #26 from Mark Johnston <markj@FreeBSD.org> --- (In reply to Michael Meiszl from comment #25) > I guess I can now dare to update the external production machine too (if = they would crash I have no means to get to the console and start into singl= e user mode, so I am very very careful when it comes to kernel crashes and = instant reboots) If you're building kernels from source you might try installing like this: # make installkernel INSTKERNNAME=3Dkernel.test # nextboot -k kernel.test # shutdown -r now so if the new kernel (installed to /boot/kernel.test) panics and reboots, t= he system will boot back into the old kernel without intervention in single-us= er mode. Be sure to try this before updating userland. --=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-255775-8303-owgKdOogYr>