Date: Sat, 15 May 2021 07:24:51 +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-AOCdfDXnNB@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 #11 from Michael Meiszl <michael@meiszl.de> --- after running for some days (with fw started manually) it crashed again yesterday, but on a totally different function: Unread portion of the kernel message buffer: panic: Assertion stp->st_flags =3D=3D 0 failed at /root/src/sys/kern/sys_generic.c:1942 cpuid =3D 1 time =3D 1620999784 KDB: stack backtrace: #0 0xffffffff80c400e5 at kdb_backtrace+0x65 #1 0xffffffff80bf5be1 at vpanic+0x181 #2 0xffffffff80bf59b3 at panic+0x43 #3 0xffffffff80c63b20 at seltdfini+0xa0 #4 0xffffffff80bac8fa at exit1+0x49a #5 0xffffffff80bbddda at kproc_exit+0xaa #6 0xffffffff82b5116e at smb_iod_thread+0x37e #7 0xffffffff80bb1f00 at fork_exit+0x80 #8 0xffffffff8105c6ae at fork_trampoline+0xe Uptime: 2d2h27m29s I guess this has nothing to do with the main issue, but it made me revert to the original, unpatched 13.0 kernel for now. My current approach is to start the fw with a combination of cron and at: CronEntry: @reboot at -f /root/startfirewall now+3min Startfirewall script:=20 #!/bin/sh /usr/sbin/service ipfw onestart totally simple, but it seems to work for now. I did not notice the panic yesterday so the whole net ran without fw protection for almost a day. This= is not acceptable. Cron+at limit the dangerous time after a panic or reboot to 3mins --=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-AOCdfDXnNB>