From nobody Thu Dec 25 17:30: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 4dcbPN30Dvz6LgNw for ; Thu, 25 Dec 2025 17:30:48 +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 4dcbPM6V4wz3sDx for ; Thu, 25 Dec 2025 17:30:47 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Authentication-Results: mx1.freebsd.org; none Received: from smtp-relay-int-backup.realworks.nl (crmlive5.colo2.realworks.nl [10.2.52.25]) by mailrelayint1.colo2.realworks.nl (Postfix) with ESMTP id 4dcbPK43nRzb3; Thu, 25 Dec 2025 18:30:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1766683845; 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=2y5WSFomewjGsdT8gwNhLa25OLBXgY7t5KDCrsc8MkI=; b=ZpaF/T3kw6rZoh72VeMqeSyeQK/dCkB6yOg56LTLN4fIa/NYl2R2dToR0IgoZ/kuj2vdvs URILFpK81Zpp1Ur3YusgN1HMaCVNzVmsc8MxElrbodzOVb8qDf3SzVUXlBDDP9JxnBHM0T PRcV4Q+mEXDFpkF0rl1Ipsqiaa4FDurewI7aOSa+sPl56byy+vNq0m0UJT3NT4u1bywGBY 469xCNhzeX7OnnpnAbg46eOb/B7sj7P34EvWI1lVGa5f5E77KntDGzWbGs93k2vJH9HP8J jMomOJR+4kbJvGauqed1HYSxFPFzl/0c112AmkDrk9RX1GrRXMEc/s54V5zRnw== Received: from crmlive5.colo2.realworks.nl (localhost [127.0.0.1]) by crmlive5.colo2.realworks.nl (Postfix) with ESMTP id 45316123890; Thu, 25 Dec 2025 18:30:45 +0100 (CET) Date: Thu, 25 Dec 2025 18:30:45 +0100 (CET) From: Ronald Klop To: FreeBSD User Cc: FreeBSD CURRENT Message-ID: <902742484.3865.1766683845222@localhost> In-Reply-To: <20251225170828.7aef61df@hermann> Subject: Re: CURRENT: kernel panic in IPFW while stopping jails 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_3864_824756654.1766683845219" X-Mailer: Realworks (777.87) X-Originating-Host: from (localhost [127.0.0.1]) by crmlive5 [10.2.52.25] with HTTP; Thu, 25 Dec 2025 18:30:45 +0100 Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dcbPM6V4wz3sDx ------=_Part_3864_824756654.1766683845219 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Do you use bpf or tap in your ipfw rules? A panic with that was mentioned on the 20th. And fixed in the mean time of I remember correctly. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291854 Regards,Ronald Van: FreeBSD User Datum: 25 december 2025 17:09 Aan: FreeBSD CURRENT Onderwerp: CURRENT: kernel panic in IPFW while stopping jails > > > Hello, > > on recent CURRENT ipfw (in my case compiled into kernel) either restarting > "ipfw" via "service ipfw restart" or restarting jails using also ipfw on a host > also using ipfw (jail-hoster also ipfw compiled into kernel) causes a fatal > kernel crash. > > This issue is present since last week an wreak havok to several boxes with OS > installed on UFS/FFS SSDs. In one case I have only pictures/screenshots made > via smartphone - while crashing, kernel debugger input pops up on console, but > I'm able to typein something within the first seconds and this is mostly > "reboot" but gets stuck with "re" in most cases. "bt" freezes system > immediately. > > At least I can reproduce this misbehaviour on all recent CURRENT were IPFW is > compiled into kernel. Anybody else havong this trouble? > > Kind regards, > > Oliver > > Merry Christmas to everyone. > > -- > > A FreeBSD user > > > > > ------=_Part_3864_824756654.1766683845219 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Do you use bpf or tap in your ipfw rules?

A panic with that was mentioned on the 20th. And fixed in the mean time of I remember correctly. 

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291854

Regards,
Ronald

Van: FreeBSD User <freebsd@walstatt-de.de>
Datum: 25 december 2025 17:09
Aan: FreeBSD CURRENT <freebsd-current@freebsd.org>
Onderwerp: CURRENT: kernel panic in IPFW while stopping jails

Hello,

on recent CURRENT ipfw (in my case compiled into kernel) either restarting
"ipfw" via "service ipfw restart" or restarting jails using also ipfw on a host
also using ipfw (jail-hoster also ipfw compiled into kernel) causes a fatal
kernel crash.

This issue is present since last week an wreak havok to several boxes with OS
installed on UFS/FFS SSDs. In one case I have only pictures/screenshots made
via smartphone - while crashing, kernel debugger input pops up on console, but
I'm able to typein something within the first seconds and this is mostly
"reboot" but gets stuck with "re" in most cases. "bt" freezes system
immediately.

At least I can reproduce this misbehaviour on all recent CURRENT were IPFW is
compiled into kernel. Anybody else havong this trouble?

Kind regards,

Oliver

Merry Christmas to everyone.

-- 

A FreeBSD user




------=_Part_3864_824756654.1766683845219--