On 8.6.2022. 7:33, Hrvoje Popovski wrote: > On 8.6.2022. 0:42, Alexandr Nedvedicky wrote: >> Hello Hrvoje, >> >> </snip> >>> Hi, >>> >>> while booting with this diff I've got this log: >>> >>> starting early daemons: syslogd pflogd ntpdwitness: lock_object >>> uninitialized: 0xfffffd8785c81a >>> 90 >>> Starting stack trace... >>> witness_checkorder(fffffd8785c81a90,9,0) at witness_checkorder+0xad >>> mtx_enter(fffffd8785c81a80) at mtx_enter+0x34 >>> pf_remove_state(fffffd8785c81988) at pf_remove_state+0x1da >>> pfsync_in_del_c(fffffd80028977b0,c,2,2) at pfsync_in_del_c+0x9f >>> pfsync_input(ffff800020b056e8,ffff800020b056f4,f0,2) at pfsync_input+0x33c >>> ip_deliver(ffff800020b056e8,ffff800020b056f4,f0,2) at ip_deliver+0x103 >>> ip_local(ffff800020b056e8,ffff800020b056f4,fe0000007fff0220,0) at >>> ip_local+0x1b7 >>> ipintr() at ipintr+0x5f >>> if_netisr(0) at if_netisr+0xca >>> taskq_thread(ffff800000036000) at taskq_thread+0x11a >> thanks for quick test with pfsync. it has turned out I've forgot to >> initialize >> a pf_state::mtx in pfsync_state_import() function. >> >> below is updated diff, which should fix a stack trace reported by >> witness. > > Hi, > > yes, stack trace is gone with this diff. will leave it running for a > while to see if panic goes away ... > > Thank you ... >
Hi, after 4 days of running this diff firewall seems stable. It should panic by now ..
