On Mon, 12 Dec 2022 14:31:35 +1000 "Nicholas Piggin" <npiggin@xxxxxxxxx> wrote: > Have you run memtest on the system? Are the messages related to a > kernel upgrade? This and your KASAN bugs look possibly like random > corruption. Found out that 'stress -m2 --vm-bytes 965M' and 'memtester 1930M' run fine for hours as long I have VMAP_STACK disabled when using SMP=y. So I can use either SMP=y or VMAP_STACK=y and everything is fine. But when I use both at the same time I get this kind of memory corruption. Probably this has something to do with (or is?) the issue I originally reported as https://bugzilla.kernel.org/show_bug.cgi?id=215389 only that I now found out to provoke the issue much faster and more reliable with stress and memtester instead of a full glibc test build on the G4... Any hints for further testing? Could do a bisect again with a more minimalistic kernel and see if I get the same result as in the old bug if that would be helpful. Regards, Erhard
