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

Re: What is wrong with kernels 5.X on sparc64 ?



Hi Miroslav!

On 3/29/20 8:16 PM, Miroslav Zubcic wrote:
> I've managed to get some things with mmap MAP_FIXED on sparc64 fixed by
> lxc people ( https://github.com/lxc/lxc/issues/3262 ) and successfuly
> created first test containers today!

Cool, thanks for your contribution for Linux on SPARC.

> The blues usually goes like this (OBP on serial):
> 
> Processing triggers for libc-bin (2.31-0+sparc64) ...
> Processing triggers for systemd (245.2-1) ...
> 
> varnava login: [12438.966956] Unable to handle kernel paging request in
> mna handler
> [12438.966960]  at virtual address 2a70e013abac6164
> [12439.095778] current->{active_,}mm->context = 00000000000000cb
> [12439.164784] current->{active_,}mm->pgd = fff0001375fcc000
> [12439.229899] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00000009
> [12439.321907] Press Stop-A (L1-A) from sun keyboard or send break
> [12439.321907] twice on console to return to the boot prom
> [12439.321938] kernel BUG at kernel/cpu.c:941!
> 
> ... or this:
> 
> (Reading database ... 56196 files and directories currently installed.)
> Removing exim4-daemon-light (4.93-10) ...
> Removing exim4-base (4.93-10) ...
> 
> 
> varnava login: [ 4888.989100] Unable to handle kernel NULL pointer
> dereference
> [ 4889.057151] tsk->{mm,active_mm}->context = 00000000000000ce
> [ 4889.124099] tsk->{mm,active_mm}->pgd = fff0001375888000
> [ 4889.187349] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00000009
> [ 4889.279315] Press Stop-A (L1-A) from sun keyboard or send break
> [ 4889.279315] twice on console to return to the boot prom
> [ 4889.279345] kernel BUG at kernel/cpu.c:941!
>
> (...)
> Does anybody have some information or experience with this phenomenon?

I think I have seen instability issues on the one IIIi machine we have
as well as this machine is running 4.19 for that reason. Other machines
such as the T2 or later models don't show any issues.

So, I think this issue needs to be bisected and reported to the SPARC
Linux kernel mailing list [1]. I'm CC'ing Meelis Roos who has been doing
a lot of kernel regression testing on sparc64 in the past and might have
already found the problematic commit.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


Reply to: