Messages in this thread | | | Date | Wed, 13 Mar 2024 09:39:21 -0700 (PDT) | From | "Christoph Lameter (Ampere)" <> | Subject | Re: [PATCH v3] ARM64: Dynamically allocate cpumasks and increase supported CPUs to 512 |
| |
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.
| |