HI Joel, On Thu, 25 May 2023 at 20:51, Joel Fernandes <joel@xxxxxxxxxxxxxxxxx> wrote: > > Hello Naresh, > > On Wed, May 24, 2023 at 5:02 AM Naresh Kamboju > <naresh.kamboju@xxxxxxxxxx> wrote: > > > > Following kernel crash noticed while running perf testing on qemu-x86_64 > > with stable-rc 6.3.4-rc2 + kselftest merge configs. > > > > Reported-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx> > > > > logs: > > ===== > > INFO: Performing perf record test... > > > > Parse sched tracepoints fields: Ok > > 16: syscalls:sys_enter_openat event fields : > > --- start --- > > test child forked, pid 255 > > <4>[ 152.221288] int3: 0000 [#1] PREEMPT SMP PTI > > <4>[ 152.221564] CPU: 0 PID: 255 Comm: perf Not tainted 6.3.4-rc2 #1 > > <4>[ 152.221607] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), > > BIOS 1.14.0-2 04/01/2014 > > <4>[ 152.221733] RIP: 0010:__schedule+0x29e/0xaa0 <trim> > I wonder if this is a deadlock related to runqueue lock since another > CPU call stack are similarly in schedule. > > I tried to run gdb on your vmlinux but it does not have symbols, would > it be possible for you to provide a copy of vmlinux with symbols? DEBUG_INFO not enabled on this build. > > Were you able to narrow down the commit/release using git bisect to > see when it started happening? I will bisect this problem and get back to you. > > Thank you, > > - Joel - Naresh
