I got this error after upgrading a Debian machine (x86-64) from Stretch to Buster. Upgrade is successful, but the next boot it crashes. The machine is an Asus B360M-A with an Intel i7-8700 CPU and 16GB DDR4. My kernel is 4.20.17 (from kernel.org, not a distribution kernel), but I tried with 4.19.273 and 5.10.169 with the same .config. Here the offending part (with 4.19.273): [ 45.542326] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00 [ 45.542326] [ 45.652693] CPU: 1 PID: 1 Comm: init Not tainted 4.19.273 #1 [ 45.720976] Hardware name: System manufacturer System Product Name/PRIME B361 [ 45.833050] Call Trace: [ 45.862768] dump_stack+0x50/0x63 [ 45.902905] panic+0xec/0x23a [ 45.938876] ? __switch_to_asm+0x35/0x70 [ 45.986319] do_exit+0x9fd/0xbc0 [ 46.025417] do_group_exit+0x35/0xa0 [ 46.068689] __x64_sys_exit_group+0xf/0x10 [ 46.118213] do_syscall_64+0x43/0xf0 [ 46.161486] entry_SYSCALL_64_after_hwframe+0x5c/0xc1 [ 46.222475] RIP: 0033:0x7f31bbbc0836 [ 46.265741] Code: 83 c8 ff c3 89 fa 41 b8 e7 00 00 00 be 3c 00 00 00 eb 10 90 [ 46.491860] RSP: 002b:00007fff108fc028 EFLAGS: 00000206 ORIG_RAX: 00000000007 [ 46.583080] RAX: ffffffffffffffda RBX: 00007f31bbbc9208 RCX: 00007f31bbbc0836 [ 46.669089] RDX: 000000000000007f RSI: 000000000000003c RDI: 000000000000007f [ 46.755108] RBP: 00007f31bbb4ef00 R08: 00000000000000e7 R09: 00007fff108fbf38 [ 46.841129] R10: 00007fff108fc3b4 R11: 0000000000000206 R12: 0000000000000002 [ 46.927149] R13: 0000000000000004 R14: 00007f31bbb4ef30 R15: 0000000000000000 [ 47.013219] Kernel Offset: 0x3ca00000 from 0xffffffff81000000 (relocation ra) [ 47.143078] ---[ end Kernel panic - not syncing: Attempted to kill init! exi0 [ 47.143078] ]--- [ 47.268095] ------------[ cut here ]------------ [ 47.323875] sched: Unexpected reschedule of offline CPU#0! [ 47.390085] WARNING: CPU: 1 PID: 1 at arch/x86/kernel/smp.c:128 native_smp_s0 [ 47.500188] Modules linked in: [ 47.537201] CPU: 1 PID: 1 Comm: init Not tainted 4.19.273 #1 [ 47.605496] Hardware name: System manufacturer System Product Name/PRIME B361 [ 47.717585] RIP: 0010:native_smp_send_reschedule+0x2f/0x40 [ 47.783896] Code: 05 56 54 50 01 73 15 48 8b 05 ed 13 25 01 be fd 00 00 00 45 [ 48.010159] RSP: 0018:ffffa1e4ddc43ee8 EFLAGS: 00010086 [ 48.073348] RAX: 0000000000000000 RBX: ffffa1e4dbd78000 RCX: ffffffffbee47218 [ 48.159472] RDX: 0000000000000001 RSI: 0000000000000096 RDI: ffffffffbf4bb92c [ 48.245600] RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000aaaaaa [ 48.331727] R10: 0000000000000020 R11: 0000000000000001 R12: ffffa701c190bd68 [ 48.417852] R13: ffffa1e4ddc60a40 R14: ffffa1e4ddc60b38 R15: 00000007bc038078 [ 48.503972] FS: 0000000000000000(0000) GS:ffffa1e4ddc40000(0000) knlGS:00000 [ 48.601561] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 48.670998] CR2: 00007f31bb6f7570 CR3: 000000045922e002 CR4: 00000000003606e0 [ 48.757120] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 48.843243] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 48.929356] Call Trace: [ 48.959073] <IRQ> [ 48.983575] update_process_times+0x3b/0x50 [ 49.034145] tick_sched_handle+0x2f/0x40 [ 49.081583] tick_sched_timer+0x32/0x70 [ 49.127977] __hrtimer_run_queues+0xd8/0x260 [ 49.179589] ? tick_sched_do_timer+0x50/0x50 [ 49.231197] hrtimer_interrupt+0xfc/0x230 [ 49.279682] smp_apic_timer_interrupt+0x5d/0x130 [ 49.335459] apic_timer_interrupt+0xf/0x20 [ 49.384981] </IRQ> [ 49.410524] RIP: 0010:panic+0x1fb/0x23a [ 49.456924] Code: 48 83 c3 64 eb b0 83 3d 66 42 0a 01 00 74 05 e8 5f e0 66 f6 [ 49.683184] RSP: 0018:ffffa701c190be18 EFLAGS: 00000246 ORIG_RAX: ffffffffff3 [ 49.774421] RAX: 0000000000000056 RBX: 0000000000000000 RCX: ffffffffbee47218 [ 49.860446] RDX: 0000000000000000 RSI: 0000000000000092 RDI: ffffffffbf4bb92c [ 49.946472] RBP: ffffa701c190be90 R08: 0000000000000001 R09: 0000000000aaaaaa [ 50.032502] R10: 0000000000000082 R11: 0000000000000001 R12: 0000000000000000 [ 50.118521] R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000000 [ 50.204543] ? panic+0x1f8/0x23a [ 50.243644] ? __switch_to_asm+0x35/0x70 [ 50.291082] do_exit+0x9fd/0xbc0 [ 50.330183] do_group_exit+0x35/0xa0 [ 50.373457] __x64_sys_exit_group+0xf/0x10 [ 50.422986] do_syscall_64+0x43/0xf0 [ 50.466258] entry_SYSCALL_64_after_hwframe+0x5c/0xc1 [ 50.527252] RIP: 0033:0x7f31bbbc0836 [ 50.570519] Code: 83 c8 ff c3 89 fa 41 b8 e7 00 00 00 be 3c 00 00 00 eb 10 90 [ 50.796666] RSP: 002b:00007fff108fc028 EFLAGS: 00000206 ORIG_RAX: 00000000007 [ 50.887890] RAX: ffffffffffffffda RBX: 00007f31bbbc9208 RCX: 00007f31bbbc0836 [ 50.973905] RDX: 000000000000007f RSI: 000000000000003c RDI: 000000000000007f [ 51.059921] RBP: 00007f31bbb4ef00 R08: 00000000000000e7 R09: 00007fff108fbf38 [ 51.145932] R10: 00007fff108fc3b4 R11: 0000000000000206 R12: 0000000000000002 [ 51.231947] R13: 0000000000000004 R14: 00007f31bbb4ef30 R15: 0000000000000000 [ 51.317968] ---[ end trace 9b4faf7289c3e5db ]---
Created attachment 303781 [details] dmesg caught with serial console
Created attachment 303782 [details] kernel config
I use serial console to collect diagnostic data, but now I've found that it misses lines. In kernel boot line I put "console=ttyS0 console=tty0" so I get both local and serial console. But the issue is: tty0 shows more messages. Is there a way to get everything also on ttyS0? It would be useful, since you cant' scroll tty0 after a kernel panic. When kernel loads, tty0 scrolls very fast. I could see some more line but wasn't able to read. The only way I found was adding a (slow) speed to ttyS0, "console=ttyS0,1200" on kernel boot line. This slowed down ttyS0, and tty0 was forced to go at the same pace. So I could read a line (only on tty0), between "Run /sbin/init as init process" and start of kernel panic. That line complained that it could not find something in /usr/lib/.... At that stage, /usr was not mounted yet. Then I restored full disk image on the machine, an before upgrading from stretch to buster I merged / and /usr, so that /usr/lib/... was available from / mount. After that, kernel panic did not show anymore.
Missing file was /usr/lib/x86_64-linux-gnu/libseccomp.so.2. Maybe we can close this bug report. Is it expected that a missing file triggers a kernel panic?