Re: Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 since 5.17

Willy Tarreau
2022-03-31T04:09:08Z

Hi Ben,

On Wed, Mar 30, 2022 at 02:27:56PM -0700, Ben Greear wrote:
> Run /init as init process
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
> /init: error whitsc: Refined TSC clocksource calibration: 2903.996 MHz
> le loading shareCPU: 2 PID: 1 Comm: init Not tainted 5.17.0+ #12
> d libraries: libclocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x29dc020bb13, max_idle_ns: 440795273180 ns
> rt.so.1: cannot Hardware name: Default string Default string/SKYBAY, BIOS 5.12 08/04/2020
> open shared objeCall Trace:
> ct file: No such <TASK>
> file or directo dump_stack_lvl+0x47/0x5c
> ry

The coincidence between this error about your userland "libclocksource"
and the messages about the clock sources being refined makes me wonder
if there could be an error experienced during this lib's initialization
at a moment where the list of clocksources appears empty or opening one
of the /sys file is temporarily refused. I suspect that making a much
larger or much smaller initrd could change the initialization order
enough to prevent such an event from happening, but that sounds a bit
odd :-/

Willy