Date: Sun, 08 Jan 2023 22:47:30 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 268832] panics in check_uidgid() for outgoing packets Message-ID: <bug-268832-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268832 Bug ID: 268832 Summary: panics in check_uidgid() for outgoing packets Product: Base System Version: 13.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: nikita@druba.su Created attachment 239348 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D239348&action= =3Dedit kgdb -n last; bt Hi! Several days ago I was update of my FreeBSD from 12.3 to 13.1 and got the n= ext trouble: After boot fully updated OS(with packages), the OS freeze without any comme= nts. I didn't have a chance to get some information about error or safely power = off the system. It was fully freezed.=20 OS was binary updated by freebsd-update. Freezing also repeated after switc= hing to 13.1-RELENG kernel, builded from sources.=20 After some time of troubleshooting and help from colleagues, got some idea about the reasons of this error. Presumably, it was some component of ipfw. In attachments is ipfw show outp= ut, There a few lines at the beginning of rules is a counts, automatically adde= d by cbsdd. In FreeBSD 12.3 they worked without errors, but after upgrade led to= the described problem. When I disabling this cbsdd function, OS working well and dont try to freeze.=20 To be more specific, I will describe the well-reproducing event, where I ge= t an freezing. After compiling kernel with debug options I got a possibility to = saw a reason of freeze. With debug kernel system stopped freezing, showed me ke= rnel panic message and rebooted OS. In attachments I will rest backtrace of this event.=20 Sequencing:=20 Booting updated OS (without jails and any VMs, only primitive service apps)= ,=20 starting jail with a postgres (its can stable work a long time) starting jail with a zabbix-server (that start to interact with a postgres jail) after 10-60 seconds after launch of zabbix jail I get kernel panic. I can easily repeat sequencing and get panic again to collect more informat= ion, if it needed. --=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-268832-227>