[v6.1] BUG: soft lockup in do_idle

5 views
Skip to first unread message

syzbot

unread,
Jun 10, 2023, 4:51:49 AM6/10/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 2f3918bc53fb Linux 6.1.33
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=108b18d9280000
kernel config: https://syzkaller.appspot.com/x/.config?x=64e29382e385f1b9
dashboard link: https://syzkaller.appspot.com/bug?extid=ba8bc57653ea97a294c9
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10564f1d280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b5f0ab280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f180a77b248f/disk-2f3918bc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/582d3206652e/vmlinux-2f3918bc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/20934119e0f6/Image-2f3918bc.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ba8bc5...@syzkaller.appspotmail.com

hrtimer: interrupt took 34688440 ns
watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0]
Modules linked in:
irq event stamp: 127458
hardirqs last enabled at (127457): [<ffff8000121e1194>] default_idle_call+0x54/0xdc kernel/sched/idle.c:106
hardirqs last disabled at (127458): [<ffff8000120fe99c>] __el1_irq arch/arm64/kernel/entry-common.c:468 [inline]
hardirqs last disabled at (127458): [<ffff8000120fe99c>] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:486
softirqs last enabled at (127386): [<ffff800008020d74>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (127386): [<ffff800008020d74>] __do_softirq+0xc14/0xea0 kernel/softirq.c:600
softirqs last disabled at (126693): [<ffff80000802a994>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:79
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.33-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : arch_local_irq_enable+0xc/0x18 arch/arm64/include/asm/irqflags.h:44
lr : arch_cpu_idle+0x14/0x20 arch/arm64/kernel/idle.c:45
sp : ffff800015537cd0
x29: ffff800015537cd0 x28: 0000000000000000 x27: 1ffff00002ab7a6c
x26: 0000000000000000 x25: 1ffff00002ab7aa9 x24: 1ffff00002abca08
x23: dfff800000000000 x22: ffff8000155bd360 x21: ffff8000155e5040
x20: 0000000000000000 x19: ffff8000155e5040 x18: 1fffe000368b5f76
x17: ffff8000155bd000 x16: ffff800008065570 x15: ffff0001b45afbbc
x14: 1ffff00002ab80b0 x13: dfff800000000000 x12: 0000000000000003
x11: ff8080000aac42e8 x10: 0000000000000003 x9 : 0000000000000000
x8 : 00000000000000e0 x7 : ffff800008436e44 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff800012102474
x2 : 0000000000000001 x1 : ffff80001225c340 x0 : ffff80019f09e000
Call trace:
arch_local_irq_enable+0xc/0x18 arch/arm64/include/asm/irqflags.h:35
default_idle_call+0x68/0xdc kernel/sched/idle.c:109
cpuidle_idle_call kernel/sched/idle.c:191 [inline]
do_idle+0x1e0/0x514 kernel/sched/idle.c:303
cpu_startup_entry+0x24/0x28 kernel/sched/idle.c:400
rest_init+0x2d8/0x2f0 init/main.c:729
start_kernel+0x0/0x60c init/main.c:890
start_kernel+0x44c/0x60c init/main.c:1145
__primary_switched+0xb8/0xc0 arch/arm64/kernel/head.S:468


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages