From nobody Sat Dec 20 05:22:31 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 4dYCTq4MBHz6LH1Y for ; Sat, 20 Dec 2025 05:22:55 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yw1-x112b.google.com (mail-yw1-x112b.google.com [IPv6:2607:f8b0:4864:20::112b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dYCTp5PHsz3RKY for ; Sat, 20 Dec 2025 05:22:54 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=izw3qptK; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::112b as permitted sender) smtp.mailfrom=kob6558@gmail.com Received: by mail-yw1-x112b.google.com with SMTP id 00721157ae682-78fb7ab7562so9739447b3.2 for ; Fri, 19 Dec 2025 21:22:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1766208168; x=1766812968; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=kfuNTAacFCUlFov/mZMSCOfRpYMXAINM0lA1IpD4gEE=; b=izw3qptKDZZ2U4cAL9c3o4s189gKyPdiltktwk+Fp58TW9Q+PLVfqDVHMaARbPkTuO 5ZTvq6hPH8eZ9QICMbCDhu+gPTn3/N/E91iK7R8vGPjWwHg2nms5xToewiIAwpe4FfHC k9TW3MbKLPVloCbjRzrwa8CphJuMTC9L9mXbc864tETpKsVxUCiXwp7Mwo84fGq9rfsI nsFxGXFaP5+HSkxt9hMN6BNgrbcmD0WGmV53g1fhMdS8Qqbc5q1eLavmrFyW4Uz8c2mh hNAMQG6AstCZ2ifjaCGOnfN1s1WM3WTRl+/ZsQqOrP4raTU+tBqYGPkAeUjIoyb7P2Wt IDKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1766208168; x=1766812968; h=to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=kfuNTAacFCUlFov/mZMSCOfRpYMXAINM0lA1IpD4gEE=; b=G8HkTHS/PP6hynhrHhu+FfsntKj/+tjb1sNCwc34JTHYcEd7/DK30Zh6sXFQjdAyzR rffTo7hgYMkfHV17EA4StoSfkAKS4UK18ODLZTjSKnP0lftgVkLMMnaA9glbWVFMO9Xu dcmg1+JldAr06C2EU2bMLcD9Ev1vMctQJsYAXDwAqs777JNOQwiDqSu/Gy+/MV1TKq6U CMhaMuAEUzwy3LvZP/NkEQ/OauzKqJDONvuPDKdqlJI45UD65LKzZ4hIw9Jy/5umhJKw vCquKxrkbqmlDL6wP1oHVsLqWrL/VKnDd+R8Iqcl25jfIq8CMIzlp0s+2ezY6T7fnhqi wfRQ== X-Gm-Message-State: AOJu0YxL7aCFwxk04A+opN3BFYB4Z/AIVvWlvza3tZwV1uwK6ghP1ztQ wrAWNo6WufEEJfYg5avSEQIbnKPbTr07rA2CF5k29UQHpBHs2I/TgfbJAXJUhQM2QUscvmXy0tv FrO6dCXzAXd7IAyWHmjGDG4mz85OL6Rd5KHH2hsw= X-Gm-Gg: AY/fxX46nXlKnznspCA3YCshVZO+7hrhmwPV6N1cugMfoZsLYfq8iInqpS6cYWTm2oR xsNX7ZiBhOLQUesGb3qtkvH2aTrMKSzhVjkuuD8vgcRigss59P3WObeVNsYeuM/I9fGXCgVmwev gVaME7fBYDExYJ10Wa4HxVvcHyQ/u72eHtxnqo3RJGla+lT4WzP5qFSRYPHY2tgZhul/MxCyfVi +sj/7lI6biANk8XrSKLTWCYsJJbMY4cEuwgGZ2VKZyRo4eneunCn8pICaotS5OSRsgS5Ohv X-Google-Smtp-Source: AGHT+IGx6UYA+IzD7gAe4NFH55a/GTeTsexI6LKKsUE0zx+o6bVZtcK0oPewqtKOPiTfi8tNL7B3JJGGGQe7+oCYok0= X-Received: by 2002:a05:690c:7488:b0:78f:858b:95ba with SMTP id 00721157ae682-78fb40915eamr81904597b3.49.1766208167937; Fri, 19 Dec 2025 21:22:47 -0800 (PST) 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 From: Kevin Oberman Date: Fri, 19 Dec 2025 21:22:31 -0800 X-Gm-Features: AQt7F2qBSjSk0JvpyOlgDRtQHC8StV-d_eZ0nyhxFec9apsIsDJS9XfnNn6mdQ8 Message-ID: Subject: Panic during boot on assertion in ipfw strtup To: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000730a9206465b6235" X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.70 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MISSING_XM_UA(0.00)[]; BLOCKLISTDE_FAIL(0.00)[2607:f8b0:4864:20::112b:server fail]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::112b:from] X-Rspamd-Queue-Id: 4dYCTp5PHsz3RKY --000000000000730a9206465b6235 Content-Type: text/plain; charset="UTF-8" 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 --000000000000730a9206465b6235 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
As of current as of=C2=A0Dec 16=C2=A0=C2=A0= 21:22:39 UTC 2025 m system panics when starting ipfw. was not happening on= =C2=A02f29d0f3e6d2 on Saturday Dec 13. I tried to get a dump, but the syste= m did an immediate reboot when I tried 'panic'. Here is the panic o= utput:
Dec 19 07:12:30 ptavv kernel: ipfw2 (+ipv6) initializ= ed, divert loadable, nat loadable, default to deny, logging disabled
Dec= 19 07:12:30 ptavv kernel: panic: Assertion tap->rule =3D=3D rule failed= at /usr/src/sys/netpfil/ipfw/ip_fw_bpf.c:86
Dec 19 07:12:30 ptavv kerne= l: cpuid =3D 11
Dec 19 07:12:30 ptavv kernel: time =3D 1766124707
Dec= 19 07:12:30 ptavv kernel: KDB: stack backtrace:
Dec 19 07:12:30 ptavv k= ernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe= 00eb3d3900
Dec 19 07:12:30 ptavv kernel: vpanic() at vpanic+0x136/frame = 0xfffffe00eb3d3a30
Dec 19 07:12:30 ptavv kernel: panic() at panic+0x43/f= rame 0xfffffe00eb3d3a90
Dec 19 07:12:30 ptavv kernel: ipfw_tap_alloc() a= t ipfw_tap_alloc+0x2f7/frame 0xfffffe00eb3d3ac0
Dec 19 07:12:30 ptavv ke= rnel: 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 0xffff= fe00eb3d3d40
Dec 19 07:12:30 ptavv kernel: kern_getsockopt() at kern_get= sockopt+0xb5/frame 0xfffffe00eb3d3dd0
Dec 19 07:12:30 ptavv kernel: sys_= getsockopt() at sys_getsockopt+0x52/frame 0xfffffe00eb3d3e00
Dec 19 07:1= 2:30 ptavv kernel: amd64_syscall() at amd64_syscall+0x169/frame 0xfffffe00e= b3d3f30
Dec 19 07:12:30 ptavv kernel: fast_syscall_common() at fast_sysc= all_common+0xf8/frame 0xfffffe00eb3d3f30
Dec 19 07:12:30 ptavv kernel: -= -- syscall (118, FreeBSD ELF64, getsockopt), rip =3D 0x1d91f7dd13da, rsp = =3D 0x1d91f513d1a8$
Dec 19 07:12:30 ptavv kernel: KDB: enter: panic
<= br>
I saw no commits=C2=A0to netpfilt=C2=A0that look like ca= ndidates=C2=A0during hte three day window, so I suspect that it is triggere= d by some other part of the ipfw start.

= I can do a bisect if nothing else seems useful. I'm afraid that I don&#= 39;t have a hash for the one that is the initial failure on Dec 16, so I= 9;ll=C2=A0 try to track down something close.
--
Kevin Oberman, Part time kid = herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fing= erprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--000000000000730a9206465b6235--