Re: [PATCH v2 08/13] sparc64: vdso: Switch to the generic vDSO library

[Andreas Larsson]

On 2025-08-28 17:38, Andreas Larsson wrote:
> and with all of them applied I got: 
> 
> ----------------%<----------------
> [    1.849344] Run /init as init process
> [    1.851309] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
> [    1.851339] CPU: 4 UID: 0 PID: 1 Comm: init Not tainted 6.17.0-rc1+ #3 VOLUNTARY
> [    1.851363] Call Trace:
> [    1.851374] [<0000000000436524>] dump_stack+0x8/0x18
> [    1.851400] [<00000000004291f4>] vpanic+0xdc/0x320
> [    1.851420] [<000000000042945c>] panic+0x24/0x30
> [    1.851437] [<00000000004844a4>] do_exit+0xac4/0xae0
> [    1.851458] [<0000000000484684>] do_group_exit+0x24/0xa0
> [    1.851476] [<0000000000494c60>] get_signal+0x900/0x940
> [    1.851495] [<000000000043ecb8>] do_notify_resume+0xf8/0x600
> [    1.851514] [<0000000000404b48>] __handle_signal+0xc/0x30
> [    1.852291] Press Stop-A (L1-A) from sun keyboard or send break
> [    1.852291] twice on console to return to the boot prom
> [    1.852310] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
> ----------------%<----------------
> 
> but given that I don't have the kernel anymore I'm starting to
> question myself if that run was really with the same base
> commit. I'll do a rebuild and see.

I found out that my previous kernel installation for the kernel with the first 8
patches was a broken mess. Sorry about the confusion. With that sorted out and a
rebuilt kernel with all patches, the failure above is the one I get for both 8
and 13 patches, and it is repeatable.

Cheers,
Andreas