5.4-RELEASE lockups on amd64 SMP

[Matthew Grooms]

Palle,

Its a dell 2850 w/ Dual CPU, AMR controller and 6x em devices ( 2x on 
board and 4x Intel Pro 1000 MT ). If you still want the full dmesg 
output, reply and I will send it to you.

I suspect the issues I am seeing are related to a SMP locking deficiency 
in pf/pfsync. I have a second identical system that has been running off 
and on for a couple of weeks now as the pfsync peer that hasn't hiccuped 
once. Its kernel is compiled without the SMP option.

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
1st 0xffffffff80752ec0 pf task mtx (pf task mtx) @ 
contrib/pf/net/if_pfsync.c:1621
2nd 0xffffffff8076e9f0 user map (user man) @ vm/vm_map.c:2998
KDB: stack backtrace:
witness_checkorder() at witness_checkorder+0x654
_sx_xlock() at _sx_xlock+0x51
vm_map_lookup() at vm_map_lookup+0x44
vm_fault() at vm_fault+0xba
trap() at trap+0x1c5
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
pf_purge_expired_states() at pf_purge_expired_states+0xab
pfsync_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 ---
KDB: enter: withness_ckeckorder
[thread pid 110 tid 100089]
Stopped at      kdb_enter+0x2f: nop
db> panic blockable sleep lock (sleep mutex) tty @ kern/kern_event.c:1453
cpuid = 0
boot() called on cpu#0
Uptime: 10m40s
Dumping 4864 mB
  16 32 ...

-Matthew

Palle Girgensohn wrote:
> --On måndag, juni 06, 2005 19.57.03 -0400 Kris Kennaway 
> <kris at obsecurity.org> wrote:
> 
>>
>> On Mon, Jun 06, 2005 at 06:54:05PM -0500, Grooms, Matthew wrote:
>>
>>> My appologies. With the debug options listed in my previous post (
>>> should have read 5.4 not 5.3 ), I got a lock order reversal. After a
>>> while, it paniced and spat out this ...
>>>
> 
> Hi,
> 
> Since I'm seeing panics with my Dell 2850 as soon as I add the second 
> CPU (and I'm not alone, it seems), may I ask what brand is this machine? 
> Can you send a dmesg? What are the ethernet devices?
> 
> /Palle
> 
>