Re: 5.10.0-4-sparc64-smp #1 Debian 5.10.19-1 crashes on T2000
Hi Riccardo, Adrian,
so I did some testing yesterday and also see your problem on my T1000.
Because of some kernel command line misconfiguration, my machine at
first couldn't find its root FS as it tried to use a non-existent NIC.
This lead to a lot of kernel oopses (I assume at least one per hardware
thread) that looked very similar to the ones you see. And this happens
even with "working" kernels (tested 4.19.x and 5.9.x). So the actual
result of that problem in 5.10.x seems to be that the kernel can't find
its root FS.
On 11.03.21 23:43, Frank Scheiner wrote:
On 11.03.21 23:03, Riccardo Mottola wrote:
I suppose the Niagara CPU gives the kernel issue
From [1] I assume T2 CPUs are not affected, but yeah, the issue could
be that selective that it only affects the very first generation.
[1]: https://lists.debian.org/debian-sparc/2021/03/msg00010.html
I can also indeed confirm that this problem only affects the T1 CPU, as
my T5220 with T2 CPU works w/o problems with kernel 5.10.x.
I didn't get any further yesterday as it took a lot of time to update
the root FSes of my T1000 and my X4270 - my intended machine for cross
compilation, not sure if it will be "fast" enough*. In addition cloning
Linus's linux tree alone took a lot of time (about an hour).
* it will:
```
## with config of Debian's 5.9.0-5 kernel as `.config`
$ make ARCH=sparc64 CROSS_COMPILE=sparc64-linux-gnu- olddefconfig
[...]
## with lsmod output from T1000
$ make ARCH=sparc64 CROSS_COMPILE=sparc64-linux-gnu-
LSMOD=$HOME/t1000-lsmod localmodconfig
[...]
$ time make -j16 ARCH=sparc64 CROSS_COMPILE=sparc64-linux-gnu- all
[...]
kernel: arch/sparc/boot/zImage is ready
real 3m12.264s
user 42m5.325s
sys 3m27.843s
```
@Adrian:
After a first cross compile run, I can confirm that 5.10-rc1 is also
broken on my T1000. I'll take this version (parent commit:
33def8498fdde180023444b08e12b72a9efed41d) as "bad". But taking v5.9 as
good means more than 5000 commits in between. Linus's tree doesn't
contain v5.9.16 or at least I didn't find it there. How can I get "good"
closer to "bad"? I don't want to check too many good versions if I know
that v5.9.16 most likely will be good, as v5.9.15 (5.9.0-5 on Debian) is
good? Should I switch to the stable kernel sources from GKH?
Cheers,
Frank
Reply to: