Re: Linux 6.17 panic during boot

2025-11-09 Thread John Paul Adrian Glaubitz
On Sun, 2025-11-09 at 13:58 +0100, Gregor Riepl wrote:
> > This issue is already known and tracked here [1].
> > 
> > It's a recent regression. Bugs come faster than we can hunt them down.
> 
> Thanks a lot, I added my +1, plus a similar panic during swapping. It looks 
> like it could have the same root cause.

Yes, please always check the issue tracker first before reporting here as
I'm trying to document every known bug there so that we avoid extra noise
and overhead.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: Linux 6.17 panic during boot

2025-11-09 Thread Gregor Riepl

This issue is already known and tracked here [1].

It's a recent regression. Bugs come faster than we can hunt them down.


Thanks a lot, I added my +1, plus a similar panic during swapping. It looks 
like it could have the same root cause.


[1] https://github.com/sparclinux/issues/issues/14




Re: Linux 6.17 panic during boot

2025-11-09 Thread John Paul Adrian Glaubitz
Hello Gregor,

On Sun, 2025-11-09 at 13:12 +0100, Gregor Riepl wrote:
> Kernel panic - not syncing: corrupted stack end detected inside scheduler
> CPU: 0 UID: 0 PID: 148 Comm: (udev-worker) Not tainted 6.17.7+deb14-sparc64 
> #1 NONE  Debian 6.17.7-1
> Call Trace:
> [<004353d8>] dump_stack+0x8/0x18
> [<004296d4>] vpanic+0xd4/0x300
> [<00429924>] panic+0x24/0x30
> [<00f284d4>] switch_to_pc+0x960/0x96c
> [<00f284fc>] schedule+0x1c/0x180
> [<00f2f730>] schedule_timeout+0x70/0x100
> [<00f290e8>] wait_for_completion_timeout+0x48/0x120
> [<10058ec8>] usb_start_wait_urb+0x68/0x140 [usbcore]
> [<10059054>] usb_control_msg+0xb4/0x120 [usbcore]
> [<1004b760>] hub_power_on+0x60/0x180 [usbcore]
> [<1004c2e8>] hub_activate+0x7a8/0x960 [usbcore]
> [<10053d60>] hub_probe+0xf60/0xfc0 [usbcore]
> [<1005e33c>] usb_probe_interface+0xdc/0x300 [usbcore]
> [<00baf07c>] really_probe+0x25c/0x400
> [<00baf2ac>] __driver_probe_device+0x8c/0x160
> [<00baf468>] driver_probe_device+0x28/0x100
> Press Stop-A (L1-A) frim sun keyboard or send break
> twice on console to return to the boot prom

This issue is already known and tracked here [1].

It's a recent regression. Bugs come faster than we can hunt them down.

Adrian

> [1] https://github.com/sparclinux/issues/issues/14

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913