https://bugzilla.kernel.org/show_bug.cgi?id=215389
--- Comment #37 from Erhard F. (erhar...@mailbox.org) --- Created attachment 304308 --> https://bugzilla.kernel.org/attachment.cgi?id=304308&action=edit dmesg (6.3.3, KCSAN, PowerMac G4 DP) Thanks for taking another look into this Christophe! Applied the patches on top of 6.3.3 and these are my findings so far: 1. KCSAN works fine on my G4 and passes self tests. 2. It does not generate any additional output when I hit the "pagealloc: memory corruption". 3. When setting CONFIG_KCSAN_WEAK_MEMORY=y my G4 won't finish booting. Early boot works, the screen shows some dmesg but booting gets stuck there never reaching console. I also don't get any netconsole output with CONFIG_KCSAN_WEAK_MEMORY=y. 4. As soon as I set CONFIG_KCSAN_EARLY_ENABLE=y dmesg shows plenty of data races! netconsole output and kernel .config attached. To provoke the memory corruption 'stress' is a good tool. stress -m2 --vm-bytes 915M provokes the corruption easily and --vm-bytes 915M is small enough to not provoke the OOM killer on my G4 DP with its' 2 CPUs and 2 GiB RAM. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
