On 13.03.2024 17:39, Christoph Lameter (Ampere) wrote: > On Wed, 13 Mar 2024, Marek Szyprowski wrote: > >>> I did try to trigger this on FVP by adding OPPs + some hacks to add >>> dummy >>> clock provider to successfully probe this driver. I couldn't hit the >>> issue >>> reported 🙁. It could be that with the hardware clock/regulator >>> drivers, it >>> take a different path in OPP core. >> >> I can fully reproduce this issue on Khadas VIM3 and Odroid-N2 boards. >> Both Meson A311D SoC based. > > Hmm... Would it trigger on Orangepi5plus? With some effort I can get > that board up at home. > > Could you reboot with some memory diagnostics so that we are sure that > nothing gets corrupted? > > F.e. specify a command line parameter "slub_debug" to enable > redzoning. That way we may see potential memory corruption. I've added CONFIG_SLUB_DEBUG_ON=y to my .config, but I got no reports for any potential memory corruption. Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland
