5.4-RELEASE lockups on amd64 SMP

Grooms, Matthew MGrooms at seton.org
Wed Jun 8 23:22:52 GMT 2005


Matthew,

can you try the attached diff.  Available for 5 and CURRENT.  I recall that 
this problem was seen before, strange that I didn't see the problem.  Sounds 
familiar to you?  Please try the patch and let me know if that helps.  Thanks 
a lot.

On Wednesday 08 June 2005 01:35, Matthew Grooms wrote:
> Once again, here are the backtraces for the panic and lor ...
>
> Tracing id 110 tid 100089 td 0xffffff012f3f0c80
> kdb_enter() at kdb_enter+0x2f
> panic() at panic+0x249
> uma_dbg_free() at uma_dbg_free+0x188
> uma_zfree_arg() at uma_zfree_arg+0x1b0
> pf_purge_expired_states() at pf_purge_expired_states+0x41
> pfsync_input at pfsync_input+xb35
> pf_input() at ip_input+0x10f
> netisr_processqueue() at netisr_processqueue+0x17
> swi_net() at swi_net+0xa8
> ithread_loop() at ithread_loop+0xd9
> fork_exit() at fork_exit+0xc3
> fork_trampoline() at fork_trampoline+0xe
> --- trap 0, rip = 0, rsp = 0xffffffffb44f9d00, rbp = 0 ---
> db> continue
> boot() called on cpu#0
> Uptime: 13h42m43s
> Dumping 4864 MB
>   16 32 ...
>
> lock order reversal
...
> alltraps_with_regs_pushed() at alltraps_with_regs_pushed+0x5
> pf_state_tree_lan_ext_RB_REMOVE() at pf_state_tree_lan_ext_RB_REMOVE+0x10c

This LOR is a consequence of the fault, so it can be disregarded.

-- 
/"\  Best regards,                      | mlaier at freebsd.org
\ /  Max Laier                          | ICQ #67774661
 X   http://pf4freebsd.love2party.net/  | mlaier at EFnet
/ \  ASCII Ribbon Campaign              | Against HTML Mail and News



More information about the freebsd-pf mailing list