Date: Sat, 20 Dec 2025 20:09:02 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: Ronald Klop <ronald-lists@klop.ws> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Panic during boot on assertion in ipfw strtup Message-ID: <CAN6yY1v9%2BjJgex4-nzNqJ8x1LEPk7ePTzpNRA8%2Bo%2B=HrLvGkoQ@mail.gmail.com> In-Reply-To: <1163988110.212299.1766221725540@localhost> References: <CAN6yY1uY3LEX4jJre0EqxyvziU6NLPWNwqHEXADZ19EsuWWdrA@mail.gmail.com> <1163988110.212299.1766221725540@localhost>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sat, Dec 20, 2025 at 1:08 AM Ronald Klop <ronald-lists@klop.ws> wrote: > There were changes to bpf. Maybe try those. > > Regards, > Ronald > > *Van:* Kevin Oberman <rkoberman@gmail.com> > *Datum:* 20 december 2025 06:24 > *Aan:* FreeBSD Current <freebsd-current@freebsd.org> > *Onderwerp:* Panic during boot on assertion in ipfw strtup > > As of current as of Dec 16 21:22:39 UTC 2025 m system panics when > starting ipfw. was not happening on 2f29d0f3e6d2 on Saturday Dec 13. I > tried to get a dump, but the system did an immediate reboot when I tried > 'panic'. Here is the panic output: > Dec 19 07:12:30 ptavv kernel: ipfw2 (+ipv6) initialized, divert loadable, > nat loadable, default to deny, logging disabled > Dec 19 07:12:30 ptavv kernel: panic: Assertion tap->rule == rule failed at > /usr/src/sys/netpfil/ipfw/ip_fw_bpf.c:86 > Dec 19 07:12:30 ptavv kernel: cpuid = 11 > Dec 19 07:12:30 ptavv kernel: time = 1766124707 > Dec 19 07:12:30 ptavv kernel: KDB: stack backtrace: > Dec 19 07:12:30 ptavv kernel: db_trace_self_wrapper() at > db_trace_self_wrapper+0x2b/frame 0xfffffe00eb3d3900 > Dec 19 07:12:30 ptavv kernel: vpanic() at vpanic+0x136/frame > 0xfffffe00eb3d3a30 > Dec 19 07:12:30 ptavv kernel: panic() at panic+0x43/frame > 0xfffffe00eb3d3a90 > Dec 19 07:12:30 ptavv kernel: ipfw_tap_alloc() at > ipfw_tap_alloc+0x2f7/frame 0xfffffe00eb3d3ac0 > Dec 19 07:12:30 ptavv kernel: add_rules() at add_rules+0x137/frame > 0xfffffe00eb3d3b30 > Dec 19 07:12:30 ptavv kernel: ipfw_ctl3() at ipfw_ctl3+0x365/frame > 0xfffffe00eb3d3ce0 > Dec 19 07:12:30 ptavv kernel: sogetopt() at sogetopt+0x15a/frame > 0xfffffe00eb3d3d40 > Dec 19 07:12:30 ptavv kernel: kern_getsockopt() at > kern_getsockopt+0xb5/frame 0xfffffe00eb3d3dd0 > Dec 19 07:12:30 ptavv kernel: sys_getsockopt() at > sys_getsockopt+0x52/frame 0xfffffe00eb3d3e00 > Dec 19 07:12:30 ptavv kernel: amd64_syscall() at amd64_syscall+0x169/frame > 0xfffffe00eb3d3f30 > Dec 19 07:12:30 ptavv kernel: fast_syscall_common() at > fast_syscall_common+0xf8/frame 0xfffffe00eb3d3f30 > Dec 19 07:12:30 ptavv kernel: --- syscall (118, FreeBSD ELF64, > getsockopt), rip = 0x1d91f7dd13da, rsp = 0x1d91f513d1a8$ > Dec 19 07:12:30 ptavv kernel: KDB: enter: panic > > I saw no commits to netpfilt that look like candidates during hte three > day window, so I suspect that it is triggered by some other part of the > ipfw start. > > I can do a bisect if nothing else seems useful. I'm afraid that I don't > have a hash for the one that is the initial failure on Dec 16, so I'll try > to track down something close. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > Thnks, Ronald, but I bisected the and tracked the culprit looks like 3daae1ac1d82ecdcd855101bab5206e914b1235. While I have not looked at the details of the commit, it certainly looks likely to be the issue. I have submitted 291854 now that I have found it. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">On Sat, Dec 20, 2025 at 1:08 AM Ronald Klop <<a href="mailto:ronald-lists@klop.ws">ronald-lists@klop.ws</a>> wrote:</div></div><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>There were changes to bpf. Maybe try those. <div><br></div><div>Regards,</div><div>Ronald<br><div><br><p><small><b>Van:</b> Kevin Oberman <<a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a>><br><b>Datum:</b> 20 december 2025 06:24<br><b>Aan:</b> FreeBSD Current <<a href="mailto:freebsd-current@freebsd.org" target="_blank">freebsd-current@freebsd.org</a>><br><b>Onderwerp:</b> Panic during boot on assertion in ipfw strtup<br></small></p><blockquote style="margin-left:5px;border-left:3px solid rgb(204,204,204);margin-right:0px;padding-left:5px"><div id="m_7949064476785528050P"> <div> <div id="m_7949064476785528050P.P.P"> <div><div><div style="font-family:tahoma,sans-serif;font-size:small">As of current as of Dec 16 21:22:39 UTC 2025 m system panics when starting ipfw. was not happening on 2f29d0f3e6d2 on Saturday Dec 13. I tried to get a dump, but the system did an immediate reboot when I tried 'panic'. Here is the panic output:</div><div style="font-family:tahoma,sans-serif;font-size:small">Dec 19 07:12:30 ptavv kernel: ipfw2 (+ipv6) initialized, divert loadable, nat loadable, default to deny, logging disabled<br>Dec 19 07:12:30 ptavv kernel: panic: Assertion tap->rule == rule failed at /usr/src/sys/netpfil/ipfw/ip_fw_bpf.c:86<br>Dec 19 07:12:30 ptavv kernel: cpuid = 11<br>Dec 19 07:12:30 ptavv kernel: time = 1766124707<br>Dec 19 07:12:30 ptavv kernel: KDB: stack backtrace:<br>Dec 19 07:12:30 ptavv kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00eb3d3900<br>Dec 19 07:12:30 ptavv kernel: vpanic() at vpanic+0x136/frame 0xfffffe00eb3d3a30<br>Dec 19 07:12:30 ptavv kernel: panic() at panic+0x43/frame 0xfffffe00eb3d3a90<br>Dec 19 07:12:30 ptavv kernel: ipfw_tap_alloc() at ipfw_tap_alloc+0x2f7/frame 0xfffffe00eb3d3ac0<br>Dec 19 07:12:30 ptavv kernel: add_rules() at add_rules+0x137/frame 0xfffffe00eb3d3b30<br>Dec 19 07:12:30 ptavv kernel: ipfw_ctl3() at ipfw_ctl3+0x365/frame 0xfffffe00eb3d3ce0<br>Dec 19 07:12:30 ptavv kernel: sogetopt() at sogetopt+0x15a/frame 0xfffffe00eb3d3d40<br>Dec 19 07:12:30 ptavv kernel: kern_getsockopt() at kern_getsockopt+0xb5/frame 0xfffffe00eb3d3dd0<br>Dec 19 07:12:30 ptavv kernel: sys_getsockopt() at sys_getsockopt+0x52/frame 0xfffffe00eb3d3e00<br>Dec 19 07:12:30 ptavv kernel: amd64_syscall() at amd64_syscall+0x169/frame 0xfffffe00eb3d3f30<br>Dec 19 07:12:30 ptavv kernel: fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00eb3d3f30<br>Dec 19 07:12:30 ptavv kernel: --- syscall (118, FreeBSD ELF64, getsockopt), rip = 0x1d91f7dd13da, rsp = 0x1d91f513d1a8$<br>Dec 19 07:12:30 ptavv kernel: KDB: enter: panic<br><br></div><div style="font-family:tahoma,sans-serif;font-size:small">I saw no commits to netpfilt that look like candidates during hte three day window, so I suspect that it is triggered by some other part of the ipfw start.</div><div style="font-family:tahoma,sans-serif;font-size:small"><br></div><div style="font-family:tahoma,sans-serif;font-size:small">I can do a bisect if nothing else seems useful. I'm afraid that I don't have a hash for the one that is the initial failure on Dec 16, so I'll try to track down something close.</div></div><span class="gmail_signature_prefix">-- </span><br><div class="gmail_signature"><div><div><div><div><div><div><div>Kevin Oberman, Part time kid herder and retired Network Engineer<br>E-mail: <a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div></div> </div> </div> </div></blockquote></div></div></div></blockquote><div><span class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Thnks, Ronald, but I bisected the and tracked the </span>culprit looks like 3daae1ac1d82ecdcd855101bab5206e914b1235. While I have not looked at the details of the commit, it certainly <span class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">looks</span> likely to be the issue.</div><div><br></div><div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">I have submitted <span id="gmail-title">291854 </span>now that I have found it.</div></div></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Kevin Oberman, Part time kid herder and retired Network Engineer<br>E-mail: <a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div></div>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1v9%2BjJgex4-nzNqJ8x1LEPk7ePTzpNRA8%2Bo%2B=HrLvGkoQ>