[syzbot] [edac?] WARNING in mce_timer_fn
syzbot <[email protected]> Fri, 31 Jul 2026 10:16:43 -0700
| Newsgroups | org.kernel.vger.linux-edac,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
Hello, syzbot found the following issue on: HEAD commit: cc2b5f627e8c Add linux-next specific files for 20260714 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=1304e249580000 kernel config: https://syzkaller.appspot.com/x/.config?x=2290ccbf984c524f dashboard link: https://syzkaller.appspot.com/bug?extid=9d17de59c48d71bd6824 compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14efd632580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/6836f8efb1da/disk-cc2b5f62.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/0109d3477cc7/vmlinux-cc2b5f62.xz kernel image: https://storage.googleapis.com/syzbot-assets/c2e49e350bbf/bzImage-cc2b5f62.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: [email protected] ------------[ cut here ]------------ cpu_t != t WARNING: arch/x86/kernel/cpu/mce/core.c:1770 at mce_timer_fn+0x23f/0x280 arch/x86/kernel/cpu/mce/core.c:1770, CPU#0: ktimers/0/16 Modules linked in: CPU: 0 UID: 0 PID: 16 Comm: ktimers/0 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 RIP: 0010:mce_timer_fn+0x23f/0x280 arch/x86/kernel/cpu/mce/core.c:1770 Code: 00 75 0a e8 93 3b 55 00 e9 16 ff ff ff e8 89 3b 55 00 4c 8b 1d f2 b1 af 0c 2e 2e 2e 41 ff d3 e9 ff fe ff ff e8 72 3b 55 00 90 <0f> 0b 90 e9 33 fe ff ff e8 64 3b 55 00 48 c7 c7 a0 20 20 8e 4c 89 RSP: 0018:ffffc90000157a08 EFLAGS: 00010246 RAX: ffffffff8170683e RBX: ffff8880b87234a0 RCX: ffff88801daf8000 RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000100 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000100 R10: dffffc0000000000 R11: ffffffff81706600 R12: 0000000000000000 R13: dffffc0000000000 R14: ffffffff8dc427d0 R15: ffff8880b87234a0 FS: 0000000000000000(0000) GS:ffff8881259f2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f08d99b56c8 CR3: 000000003fe3e000 CR4: 00000000003526f0 Call Trace: <TASK> call_timer_fn+0x192/0x5e0 kernel/time/timer.c:1748 expire_timers kernel/time/timer.c:1799 [inline] __run_timers kernel/time/timer.c:2374 [inline] __run_timer_base+0x67b/0x9b0 kernel/time/timer.c:2386 run_timer_base kernel/time/timer.c:2395 [inline] run_timer_softirq+0x67/0x170 kernel/time/timer.c:2403 handle_softirqs+0x1d9/0x6c0 kernel/softirq.c:626 __do_softirq kernel/softirq.c:660 [inline] run_ktimerd+0x69/0x100 kernel/softirq.c:1155 smpboot_thread_fn+0x57c/0xa80 kernel/smpboot.c:160 kthread+0x388/0x470 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK> --- 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 [email protected]. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, 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 overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup