On Wed, Apr 27, 2016 at 09:13:40AM +0000, alexey.susli...@gmail.com wrote:
> Hi tech@.
> 
> (Maybe related to http://marc.info/?l=openbsd-bugs&m=146174654219490&w=2).
 
;-)

> Crashing server acts as a carp backup (master has same hardware config but
> don't crash, in contrast to backup). Will post additional information if
> necessary.

In my case, the server is acting as a backup for 2 carp devices and also
as a master for 2 other carp devices.
But indeed, it is always the same node (part of a 2 nodes setup) that is
crashing.  This node just crached again a few minutes ago. It seems
upgrading it to 5.9 makes the bug more frequent. So I am keeping the
other node with «OpenBSD 5.8-current (GENERIC.MP) #1661: Tue Nov 24
20:16:36 MST 2015» for now.


Here is frech output:

ddb{2}> trace
Debugger() at Debugger+0x9
panic() at panic+0xfe
pool_runqueue() at pool_runqueue
pool_get() at pool_get+0xb5
m_clget() at m_clget+0x51
m_dup_pkt() at m_dup_pkt+0x88
carp_input() at carp_input+0x17c
if_input_process() at if_input_process+0xcd
taskq_thread() at taskq_thread+0x6c
end trace frame: 0x0, count: -9
ddb{2}> show panic
pool_do_get: mcl2k free list modified: page 0xffffff00f1ec7000; item
addr 0xfff
fff00f1eca800; offset 0x0=0x0 != 0xaaa0cffd8d1e5cb4
ddb{2}> show register
rdi                              0x1
rsi                            0x292
rbp               0xffff800022519b50
rbx               0xffffffff817195a0    systqmp+0x1860
rdx                                0
rcx               0xffff80000004f000
rax                              0x1
r8                0xffff800022519a70
r9                                 0
r10               0xffff800022519a20
r11                              0x8
r12                            0x100
r13               0xffff800022519b60
r14                              0x2
r15                              0x2
rip               0xffffffff81349a09    Debugger+0x9
cs                               0x8
rflags                         0x282
rsp               0xffff800022519b40
ss                              0x10
Debugger+0x9:   leave
ddb{2}>


--
oc

Reply via email to