There have been numerous fixes since 4.4 and developers are no longer familiar with this 3.5-year-old code which has been heavily changed in the interim, I suggest updating and trying to reproduce..
On 2011-10-24, ML mail <mlnos...@yahoo.com> wrote: > Hi, > > My firewall just crashed this morning and wondered if anyone maybe had an > idea what could be wrong... It's a soon 3 years old network appliance from > Nexcom loaded with OpenBSD 4.4 i386 on a compact flash card. Below I pasted > the messages from the crash logged in /var/log/messages. > > Regards, > ML > > > Oct 24 09:12:09 firewall /bsd: fatal machine check (18) in supervisor mode > Oct 24 09:12:09 firewall /bsd: trap type 18 code 0 eip d0317060 cs 50 eflags > 10216 cr2 3c0207e4 cpl 40 > Oct 24 09:12:09 firewall /bsd: panic: trap type 18, code=0, pc=d0317060 > Oct 24 09:12:09 firewall /bsd: Starting stack trace... > Oct 24 09:12:10 firewall /bsd: panic(d07d9fdc,40,dd110c80,40,d7b652b0) at > panic+0x65 > Oct 24 09:12:10 firewall /bsd: panic(d071d2e7,12,0,d0317060,3000002) at > panic+0x65 > Oct 24 09:12:10 firewall /bsd: trap() at trap+0x119 > Oct 24 09:12:10 firewall /bsd: --- trap (number 18) --- > Oct 24 09:12:10 firewall /bsd: > pf_insert_src_node(dd110d70,dd552a28,d79dbf00,d7661b54) at > pf_insert_src_node+0x2e8 > Oct 24 09:12:10 firewall /bsd: > pf_state_tree_RB_FIND(d08355d8,dd110d70,dd110d78,d03b224a,40) at > pf_state_tree_RB_FIND+0x1e > Oct 24 09:12:10 firewall /bsd: > pf_find_state(d19ae200,dd110d70,1,d7a75400,d78d0000) at pf_find_state+0x32 > Oct 24 09:12:10 firewall /bsd: > pf_test_state_tcp(dd110e08,1,d19ae200,d7a75400,14) at pf_test_state_tcp+0x93 > Oct 24 09:12:10 firewall /bsd: pf_test(1,d1d67400,dd110f10,0) at pf_test+0xb65 > Oct 24 09:12:10 firewall /bsd: > ipv4_input(d7a75400,d199b600,d08f1354,d7b652b0) at ipv4_input+0x124 > Oct 24 09:12:10 firewall /bsd: ipintr(d0630058,10,10,dd110010,d7b652b0) at > ipintr+0x64 > Oct 24 09:12:10 firewall /bsd: Bad frame pointer: 0xdd110f28 > Oct 24 09:12:10 firewall /bsd: End of stack trace.
