Date: Mon, 13 Oct 2025 11:31:09 +0000 From: bugzilla-noreply@freebsd.org To: pf@FreeBSD.org Subject: [Bug 290177] PF - panicking after upgrade to 15.0-STABLE Message-ID: <bug-290177-16861-JaPrHYVVD1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-290177-16861@https.bugs.freebsd.org/bugzilla/> References: <bug-290177-16861@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=3D290177 --- Comment #2 from Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> --- (In reply to Kristof Provost from comment #1) I can share pf.conf, but not publicly. During the middle of the week, I wil= l be able to insert a USB flash drive into this machine to collect crash dumps. >I've had a first look on the assumption that https://cgit.freebsd.org/src/= commit/?id=3Db93394a38bc41f8afceaf0c03ed5d8b8b5a9aefb >is the trigger for the panic. Unfortunately I don't really see how. It was also my initial thought, but I have not reverted this commit. Moreov= er, I am running this code on several machines, but so far only one of them has= had issues. It's challenging to determine how it's triggered, as this host is running numerous different network services, but I suspect Squid or OpenVPN clients from crowded networks with data loss are triggering this (I might be completely wrong, though). Instead of reverting the suspicious commit, I have commented "scrub in" rul= e, and I am monitoring the machine - no panics in the recent 14 hours, but the first panic, beginning yesterday's series, was more than 24h after upgrade = to 15.0-STABLE. --=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-290177-16861-JaPrHYVVD1>