Hi Adrian, After an initial glance at the Debian S7-2 panic message, I will try resetting my LDOM settings to factory default via Solaris. Then try to boot Debian again. Wondering if something about my LDOM configuration is causing a problem? FYI, Solaris has no problem with it.
If Debian still panics after the LDOM reset then I will try the non-smp kernel as suggested. Will reply and let you know the result. PS - Can’t do this today, have other plans, but will do so tomorrow. Regards, Tony > On Aug 26, 2025, at 11:25 PM, John Paul Adrian Glaubitz > <[email protected]> wrote: > > Hello, > >> On Tue, 2025-08-26 at 18:59 -0700, Tony Rodriguez wrote: >> Are Michael's 6.12.38 kernel fixes added into kernel 6.16.3-1? > > No, the patches were just posted for the first time yesterday while > the image was built last week. > >> Just tried the latest 08/21/2025 ports ISO on an Oracle S7-2 system. >> >> https://cdimage.debian.org/cdimage/ports/snapshots/2025-08-21/ >> >> *Note: The bare-metal install with lxde is fine. However, receive the >> following panic/error after first reboot (when initial install is >> finished). Due to this, I will hold off on T5140 and IBM Power 7/8 >> Debian installs (unless someone requests I try them). >> >> Loading Linux 6.16.3+deb14-sparc64-smp ... >> Loading initial ramdisk ... >> >> [ 1.026613] ds-1: ds_conn_reset() from ldc_rx >> [ 2.674023] Kernel panic - not syncing: corrupted stack end detected >> inside scheduler >> [ 2.689447] CPU: 14 UID: 0 PID: 288 Comm: (udev-worker) Tainted: G >> W 6.16.3+deb14-sparc64-smp #1 NONE Debian 6.16.3-1 >> [ 2.713919] Tainted: [W]=WARN >> [ 2.719812] Call Trace: >> [ 2.724672] [<0000000000437408>] dump_stack+0x8/0x18 >> [ 2.734573] [<0000000000429540>] panic+0xf4/0x398 >> [ 2.743944] [<0000000000f80964>] switch_to_pc+0x918/0x934 >> [ 2.754710] [<0000000000f8099c>] schedule+0x1c/0x180 >> [ 2.913102] Press Stop-A (L1-A) from sun keyboard or send break >> [ 2.913102] twice on console to return to the boot prom >> [ 2.935109] ---[ end Kernel panic - not syncing: corrupted stack end >> detected inside scheduler ]--- > > The installer uses the non-SMP kernel while the installed system uses the SMP > kernel. Can you try whether the non-SMP kernel works? > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer > `. `' Physicist > `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
