Date: Fri, 27 Aug 2021 14:09:32 +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-MKFMTvFVCR@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 --- Comment #27 from Michael Meiszl <michael@meiszl.de> --- Tnx for your suggestions, but they are not usable for me: a) I usually don't build my own kernel (unless I was told to to activate debugging for catching the bug) b) this happened to me on the update from 12 to 13. So userland had to be updated too before it occured and then there was no way back but to throw in the complete backup c) the bug only showed up going multiuser. d) I need the network to be up and running to access the machine. The conso= le is serveral hundred miles away from me and my arms are not that long :-))) (But the hint is good if I ever plan to run my own kernel, although I have = no idea why I should use something different but GENERIC. Since additinal driv= ers can be added as loadable modules, there is no need for a custom kernel, at least for me) --=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-MKFMTvFVCR>