Re: 5.10.0-4-sparc64-smp #1 Debian 5.10.19-1 crashes on T2000

2022-01-17 Thread Riccardo Mottola
Hi Adrian, John Paul Adrian Glaubitz wrote: > Did you forget to create an initrd? After installing the kernel, run: > > $ update-initramfs -k KERNEL_VERSION -c I did not run it this way, will do. I had it however, of a very big size: 316M Jan 14 17:15 initrd.img-5.9.0-rc1+ which filled up my

Re: 5.10.0-4-sparc64-smp #1 Debian 5.10.19-1 crashes on T2000

2022-01-17 Thread John Paul Adrian Glaubitz
Hi! On 1/17/22 14:41, Riccardo Mottola wrote: >>> The good news is that latest kernel installed seems to boot and takes >>> all CPUs online. How stable it is I don't know, it needs to be tested. >> >> Please run some stress tests such as stress-ng and report back. > > Not nice. I started

Re: 5.10.0-4-sparc64-smp #1 Debian 5.10.19-1 crashes on T2000

2022-01-17 Thread Riccardo Mottola
I reply to myself. I did run the old 5.9 kernel from debian - which has proven quite stable. I did run the same tests... and I found once error in the console indeed. [ 380.918996] Unable to handle kernel NULL pointer dereference [ 380.919198] tsk->{mm,active_mm}->context = 057d [

Re: 5.10.0-4-sparc64-smp #1 Debian 5.10.19-1 crashes on T2000

2022-01-17 Thread Riccardo Mottola
Hi, Riccardo Mottola wrote: > John Paul Adrian Glaubitz wrote: >>> Not nice. I started compiling some stuff and the box froze, I connected >>> serial console and could not resume due to Fast Data Access MMU miss" >> So, this crash occurs with the latest 5.15 kernel on your T2000? > exactly

Re: 5.10.0-4-sparc64-smp #1 Debian 5.10.19-1 crashes on T2000

2022-01-17 Thread Riccardo Mottola
Hi, John Paul Adrian Glaubitz wrote: >> Not nice. I started compiling some stuff and the box froze, I connected >> serial console and could not resume due to Fast Data Access MMU miss" > So, this crash occurs with the latest 5.15 kernel on your T2000? exactly latest kernel. I will retest it