I have a Fire T2000 which has been stable for my usage for months.
Now I upgraded kernel (and userland) in debian to:
Yesterday, when hooking up a serial console, i was getting asked for
root password and dropped into maintenance mode.
Today I hooked up better through a console with minicom to be able to
copy the error, but I get these errors again and again:
[ 17.134833] OOPS: RPC [000000000042ce10]0
[ 17.134843] OOPS: RPC <arch_cpu_idle+0x70/0xc0>
[ 17.134875] OOPS: Fault was to vaddr[bc0]
[ 17.134885] CPU: 25 PID: 0 Comm: swapper/25 Tainted: G D
6.4.0-1-sparc64-smp #1 Debian 6.4.4-2
[ 17.134908] Call Trace:
[ 17.134915] [<0000000000de9614>] dump_stack+0x8/0x18
[ 17.134948] [<0000000000df547c>] do_sparc64_fault+0x4bc/0xb0
[ 17.134979] [<0000000000407714>] sparc64_realfault_common+0x10/0x20 [ 17.135017] [<0000000000000bc0>] 0xbc00
[ 17.135034] [<0000000000dea050>] default_idle_call+0x30/0x12
[ 17.135067] [<00000000004c32f8>] do_idle+0xd8/0x1a0
[ 17.135095] [<00000000004c3684>] cpu_startup_entry+0x24/0x40
[ 17.135123] [<0000000000440f28>] smp_callin+0xe8/0x120
[ 17.135145] [<00000000010d8c14>] 0x10d8c14
[ 17.135162] [<0000000000000000>] 0x0
[ 17.135179] Unable to handle kernel NULL pointer dereference
[ 17.135187] tsk->{mm,active_mm}->context = 0000000000000041
[ 17.135197] tsk->{mm,active_mm}->pgd = ffff800017270000
[ 17.135207] \|/ ____ \|/
[ 17.135207] "@'/ .. \`@"
[ 17.135207] /_| \__/ |_\
[ 17.135207] \__U_/
[ 17.135216] swapper/25(0): Oops [#49]
[ 17.135230] CPU: 25 PID: 0 Comm: swapper/25 Tainted: G D
6.4.0-1-sparc64-smp #1 Debian 6.4.4-2
[ 17.135253] TSTATE: 0000004411001605
so something worsened! darn! this looks as back when all kernels failed
to boot on the Niagara.
I set up minicom to log to a file and see see if I can catch something before the crashes.
[1] http://vger.kernel.org/vger-lists.html#sparclinux
Kernel regressions should be reported to the sparclinux kernel mailing list [1].
Also, a bisect would be helpful to determine which commit broke the kernel.
On Jul 31, 2023, at 2:46 PM, Riccardo Mottola <riccardo.mottola@libero.it> wrote:
after several reboots, I could not reproduce "that" looping crash anymore, but I always got into maintenance mode.
Is that a kernel issue too?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 297 |
Nodes: | 16 (2 / 14) |
Uptime: | 19:50:54 |
Calls: | 6,667 |
Calls today: | 1 |
Files: | 12,216 |
Messages: | 5,337,043 |