From nobody Sat Dec 20 09:08:45 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4dYJVZ2fdPz6LhDK for ; Sat, 20 Dec 2025 09:08:54 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp-relay-int-backup.realworks.nl (smtp-relay-int-backup.realworks.nl [87.255.56.188]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4dYJVY6Cv8z3sJ6 for ; Sat, 20 Dec 2025 09:08:53 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Authentication-Results: mx1.freebsd.org; none Received: from smtp-relay-int-backup.realworks.nl (crmlive6.colo2.realworks.nl [10.2.52.26]) by mailrelayint1.colo2.realworks.nl (Postfix) with ESMTP id 4dYJVP64HVzZF; Sat, 20 Dec 2025 10:08:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1766221726; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=ZEGO6Ox43UxoR++Lf+e5p/BMe+8faOq/Yc17QBhJIqo=; b=Z+J+mi7rZSEj4dBKnknmNiquiYawQAjGDfXY/fob9JfHZNdb8kRACEKPgK6CqLmUvSxbsE 02E6ola/JMt2GwkzqrbmulKJ/jlNmjPUYARaQsSj+am1yLhWO+A+y2VnBvXwqK4ZmikVwn bdpcRZIazTsmLWCG1zd4So6iCu6w3cS+KMKXik4zYPd8ffXjqRNGR+fK/HtA2pGJ78fYKV Y04sglM20tqmYHrIUAecq9lgYOQ7NCGylCQVSLsYW7VkqV3H9/JjbT1LVHBT73hp5msMej EwTy4z6PAfLfXoM9I8iv/moz2b8npAOkyLuyD3HTNA8phuTGBrwxGi/oYSBeeA== Received: from crmlive6.colo2.realworks.nl (localhost [127.0.0.1]) by crmlive6.colo2.realworks.nl (Postfix) with ESMTP id ABF6E28061F; Sat, 20 Dec 2025 10:08:45 +0100 (CET) Date: Sat, 20 Dec 2025 10:08:45 +0100 (CET) From: Ronald Klop To: Kevin Oberman Cc: FreeBSD Current Message-ID: <1163988110.212299.1766221725540@localhost> In-Reply-To: Subject: Re: Panic during boot on assertion in ipfw strtup List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_212298_1425430776.1766221725538" X-Mailer: Realworks (777.87) X-Originating-Host: from (localhost [127.0.0.1]) by crmlive6 [10.2.52.26] with HTTP; Sat, 20 Dec 2025 10:08:45 +0100 Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:38930, ipnet:87.255.32.0/19, country:NL] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dYJVY6Cv8z3sJ6 ------=_Part_212298_1425430776.1766221725538 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit There were changes to bpf. Maybe try those. Regards, Ronald Van: Kevin Oberman Datum: 20 december 2025 06:24 Aan: FreeBSD Current 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 > > ------=_Part_212298_1425430776.1766221725538 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable There were changes to bpf. Maybe try those. <= div>
Regards,
Ronald

= Van: Kevin Oberman <rkoberman@gmail.com>
Datum: 20 december 2025 06:24
Aan: FreeBSD Current <= ;freebsd-current@freebsd.org>
Onderwerp: Panic durin= g boot on assertion in ipfw strtup

As of current as of Dec 16  21:22:39 UTC 2025 m syste= m panics when starting ipfw. was not happening on 2f29d0f3e6d2 on Satu= rday Dec 13. I tried to get a dump, but the system did an immediate reboot = when I tried 'panic'. Here is the panic output:
I saw no commits to netpfilt that look like candidates=  during hte three day window, so I suspect that it is triggered by som= e other part of the ipfw start.

I can do a bisect if nothing else seems useful. I'm afr= aid 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 Obe= rman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF= 1B055683



------=_Part_212298_1425430776.1766221725538--