Hello Rene, On Tue, 2024-09-03 at 11:09 +0200, René Rebe wrote: > > according to these posts [1][2] by Iggi, you figured out the stability problem > > No, we are just sometimes lucky it run that long stable. I was only made aware > recently that sun4u was not 100% and my fasted UltraSPARC until some year ago > was only a 360MHz Ultra5 until I was donated a Sun Blade 1000 recently. I see > some MM corruption that I wanted to hunt next. Hmm, ok. I was under the impression that you made some changes that made the kernel on Iggi's machine stable. Currently, the kernel crashes randomly on older SPARCs such as reported by Iggi: > https://x.com/Iggi76123640/status/1827658841581896152 > > with newer kernels on older SPARC machines. There has been a regression on older > > SPARCs since around kernel 4.19.x which I haven't gotten around to bisecting yet. > > Happy to bi-sect. I guess you mean random memory corruption I see or anything > else? Not sure what the underlying issue is, but the kernel just crashes completely. > If you have issues to bi-sect just let us know for any arch. Given T2’s cross-compile > support and I have most hardware in my museum now, I can usually bisect issues > within a day or two. I don't have issues with bisecting, I'm just rather time-constrained at the moment, so I'm always happy when someone else can step in and help. Would be great to get this issue fixed upstream. > > If you've found and fixed the bug in question, it would be great if you could share > > your fix with the community and maybe whip up a kernel patch to fix the bug upstream. > > > Of course - all patches are always nicely sorted in our public and nicely readable > SVN tree in any case. > > https://t2linux.com Is there a web view available? I'm not really a big fan of SVN, to be honest. > > Newer SPARCs are not affected by this bug, although there are other issues. > > You mean sun4v? I found a cheap T4-1 some month ago, and T2/Linux appears > to run stable on that. Any list of issues w/ sun4v I should be aware of? Linux runs mostly stable on sun4v, but there are filesystem corruption issues when you run Linux inside an LDOM on Solaris 11.3 and 11.4 even with the latest SRU of Solaris. These happen rarely, but they do occur and they are quite annoying as they mandate rebooting the LDOM as the root filesystem is mounted read-only and the filesystems as errors afterwards. It seems to be a bug in the LDOM vdisk driver (drivers/block/sunvdc.c). Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
