https://bugzilla.suse.com/show_bug.cgi?id=1192623 Bug ID: 1192623 Summary: ltp_nfs FCNTL_LOCKTESTS test causes stack trace in dmesg Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: petr.vorel@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Tumbleweed Build 20211110 kernel 5.14.14-2-default (2b5383f) (but it might have been failing in 5.13 and older kernels) https://openqa.opensuse.org/tests/2029105/file/serial0.txt Prints really long stack trace, which begins: [ 5211.445898][ C0] sysrq: Show State [ 5211.446508][ C0] task:systemd state:S stack: 0 pid: 1 ppid: 0 flags:0x00000000 [ 5211.447686][ C0] Call Trace: [ 5211.448216][ C0] __schedule+0x325/0x1530 [ 5211.448874][ C0] ? kmem_cache_alloc+0x151/0x480 [ 5211.449593][ C0] schedule+0x44/0xa0 [ 5211.450202][ C0] schedule_hrtimeout_range_clock+0x10b/0x120 [ 5211.451077][ C0] ? kfree+0xba/0x3c0 [ 5211.451934][ C0] ? sock_poll+0x4f/0xe0 [ 5211.452914][ C0] ? ep_done_scan+0xa7/0xf0 [ 5211.453723][ C0] do_epoll_wait+0x542/0x700 [ 5211.454594][ C0] ? wait_woken+0x70/0x70 [ 5211.455511][ C0] __x64_sys_epoll_wait+0x60/0x100 [ 5211.456475][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.457467][ C0] do_syscall_64+0x5c/0x80 [ 5211.458342][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.459302][ C0] ? do_syscall_64+0x69/0x80 [ 5211.460048][ C0] ? ksys_read+0x5f/0xe0 [ 5211.460755][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.461615][ C0] ? do_syscall_64+0x69/0x80 [ 5211.462361][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.463276][ C0] ? do_syscall_64+0x69/0x80 [ 5211.464043][ C0] ? exc_page_fault+0x68/0x130 [ 5211.464821][ C0] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 5211.465736][ C0] RIP: 0033:0x7fe070700c1e [ 5211.466480][ C0] RSP: 002b:00007ffc484b5ed0 EFLAGS: 00000293 ORIG_RAX: 00000000000000e8 [ 5211.467713][ C0] RAX: ffffffffffffffda RBX: 0000562627698e40 RCX: 00007fe070700c1e [ 5211.468853][ C0] RDX: 00000000000000ae RSI: 000056262788a3e0 RDI: 0000000000000004 [ 5211.469999][ C0] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000006 [ 5211.471147][ C0] R10: 00000000ffffffff R11: 0000000000000293 R12: 0000000000000352 [ 5211.472315][ C0] R13: 00000000000000ae R14: 0000000000000055 R15: 0000562627698fd0 [ 5211.473472][ C0] task:kthreadd state:S stack: 0 pid: 2 ppid: 0 flags:0x00004000 [ 5211.474773][ C0] Call Trace: [ 5211.475449][ C0] __schedule+0x325/0x1530 [ 5211.476249][ C0] ? kernel_thread+0x55/0x70 [ 5211.477068][ C0] schedule+0x44/0xa0 [ 5211.477836][ C0] kthreadd+0x2c0/0x2e0 [ 5211.478647][ C0] ? kthread_is_per_cpu+0x30/0x30 [ 5211.479670][ C0] ret_from_fork+0x22/0x30 [ 5211.480495][ C0] task:rcu_gp state:I stack: 0 pid: 3 ppid: 2 flags:0x00004000 -- You are receiving this mail because: You are the assignee for the bug.