[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Sun Ultra 45: Kernel Panic (corrupted stack end detected inside scheduler) with 5.19



I'm also experiencing this problem with the debian-12.0.0-sparc64-NETINST-1.iso from 2023-05-16 on a SPARC T4-2 (sun4v). Logs are as below; a Debian 11 image from last year works fine (unfortunately with an unknown burn date).

> Loading ...
>
> [    2.259595] niu 0001:0a:00.0: can't ioremap BAR 0: [mem size 0x01000000 64bit]
> [    2.273835] niu 0001:0a:00.0: Cannot map device registers, aborting
> [    2.288904] Kernel panic - not syncing: corrupted stack end detected inside scheduler > [    2.304269] CPU: 0 PID: 92 Comm: (udev-worker) Not tainted 6.1.0-9-sparc64 #1  Debian 6.1.27-1
> [    2.321462] Call Trace:
> [    2.326321] [<0000000000caaf50>] dump_stack+0x8/0x18
> [    2.336221] [<0000000000ca0dd8>] panic+0xec/0x344
> [    2.345591] [<0000000000cacdc4>] switch_to_pc+0x4ac/0x4c8
> [    2.356363] [<0000000000cad0f4>] __cond_resched+0x34/0x60
> [    2.367134] [<00000000006914a8>] __kmem_cache_alloc_node+0x468/0x520
> [    2.379801] [<0000000000635660>] kmalloc_trace+0x20/0xa0
> [    2.390401] [<00000000100f48e4>] usb_control_msg+0x24/0x120 [usbcore]
> [    2.403257] [<00000000100e7304>] hub_power_on+0x64/0x180 [usbcore]
> [    2.415582] [<00000000100e7e8c>] hub_activate+0x7ac/0x920 [usbcore]
> [    2.428078] [<00000000100ef500>] hub_probe+0xf60/0xfc0 [usbcore]
> [    2.440062] [<00000000100f994c>] usb_probe_interface+0x14c/0x340 [usbcore]
> [    2.453789] [<0000000000994190>] really_probe+0x290/0x440
> [    2.464542] [<00000000009943cc>] __driver_probe_device+0x8c/0x180
> [    2.476697] [<00000000009944e8>] driver_probe_device+0x28/0xe0
> [    2.488340] [<0000000000994c98>] __device_attach_driver+0x98/0x120
> [    2.500665] [<000000000099188c>] bus_for_each_drv+0x6c/0xc0
> [    2.511894] Press Stop-A (L1-A) from sun keyboard or send break
> [    2.511894] twice on console to return to the boot prom
> [    2.534001] ---[ end Kernel panic - not syncing: corrupted stack end detected inside scheduler ]---



Reply to: