On Mon, Jan 15, 2024 at 2:07 PM Alexander Bluhm <[email protected]> wrote: > > On Mon, Jan 15, 2024 at 01:42:55PM -0300, K R wrote: > > >Synopsis: kernel panic: ip_output no HDR > > >Category: kernel amd64 > > >Environment: > > System : OpenBSD 7.4 > > Details : OpenBSD 7.4-stable (GENERIC.MP) #0: Mon Dec 11 > > 19:17:55 UTC 2023 > > > > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > > > ... > > pppoe0: received unexpected PADO > > panic: ip_output no HDR > > Starting stack trace... > > panic() at panic+0x130 > > ip_output() at ip_output+0x126 > > udp_output() at 0x3be > > sosend() at sosend+0x37f > > pflow_output_process() at pflow_output_process+0x67 > > taskq_thread() at taskq_thread+0x100 > > end trace frame: 0x0, count: 251 > > End of stack frame. > > > > Trace lines attached below. > > > > >How-To-Repeat: > > > > The machine export pflows to localhost: those are read by nfcapd, part > > of nfdump, from packages. This was a very stable setup -- the kernel > > panic started after upgrading to 7.4. > > > > This machine runs 7.4-stable. Same panic was also observed on another > > machine, running 7.4-release + all syspatches, also using pflow. > > There were some commits to if_pflow.c in current. mvs@ has fixed > a bunch of races. Would it be possible for you to install a -current > snapshot on the machine and test if the problem persists?
Hey Alexander, Thank you for the quick reply. This machine is in production so I may not be able to install -current. In the meantime, I'm trying to recreate the kernel panic in a VM under vmd. I'll keep you posted. Thanks! --Kor > > bluhm
