Re: epoch callback panic

2022-04-07 Thread Mark Johnston
On Fri, Apr 01, 2022 at 09:15:39PM +, Bjoern A. Zeeb wrote: > On 1 Apr 2022, at 20:51, Peter Holm wrote: > > > On Fri, Apr 01, 2022 at 10:33:15PM +0200, Hans Petter Selasky wrote: > >> On 4/1/22 19:07, Peter Holm wrote: > >>> markj@ asked me to post this one: > >>> > >>> panic: rw lock 0xf

Re: epoch callback panic

2022-04-01 Thread Bjoern A. Zeeb
On 1 Apr 2022, at 20:51, Peter Holm wrote: On Fri, Apr 01, 2022 at 10:33:15PM +0200, Hans Petter Selasky wrote: On 4/1/22 19:07, Peter Holm wrote: markj@ asked me to post this one: panic: rw lock 0xf801bccb1410 not unlocked cpuid = 4 time = 1648770125 KDB: stack backtrace: db_trace_self_w

Re: epoch callback panic

2022-04-01 Thread Peter Holm
On Fri, Apr 01, 2022 at 10:33:15PM +0200, Hans Petter Selasky wrote: > On 4/1/22 19:07, Peter Holm wrote: > > markj@ asked me to post this one: > > > > panic: rw lock 0xf801bccb1410 not unlocked > > cpuid = 4 > > time = 1648770125 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_tra

Re: epoch callback panic

2022-04-01 Thread Hans Petter Selasky
On 4/1/22 22:33, Hans Petter Selasky wrote: Hi, Maybe you need to grab the lock before destroying it? Is this easily reproducible? --HPS Can you figure out the owner of the lock? I guess the owner is not in an epoch section like it should! --HPS

Re: epoch callback panic

2022-04-01 Thread Hans Petter Selasky
On 4/1/22 19:07, Peter Holm wrote: markj@ asked me to post this one: panic: rw lock 0xf801bccb1410 not unlocked cpuid = 4 time = 1648770125 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00e48a3d10 vpanic() at vpanic+0x17f/frame 0xfe00e48a3d60 p

epoch callback panic

2022-04-01 Thread Peter Holm
markj@ asked me to post this one: panic: rw lock 0xf801bccb1410 not unlocked cpuid = 4 time = 1648770125 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00e48a3d10 vpanic() at vpanic+0x17f/frame 0xfe00e48a3d60 panic() at panic+0x43/frame 0xfe00