From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from gentwo.org (gentwo.org [62.72.0.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 02A934DA05; Wed, 13 Mar 2024 16:39:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=62.72.0.81 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710347971; cv=none; b=KDMovb7BwjLXeAXtGFcwhf0xuQPoSebOw9sUpOdIc0lA6Icf/9BBc4+dumhUX34F1F6we1mLf9ljpsJMaBhcSEnGrdNfZCbA812GoJMaxLbR8eljYqVPlEufEK5cy59v3y4W7FhtOLVRfqWQds0lLYmALoZjhGnF55by3iGmW3s= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710347971; c=relaxed/simple; bh=W6R8O4M25dj7O1UDjRAq3AUKBrOJQ+XGzWoFoLCvgPs=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=DkbxXeJ0Gq7DiUVvCwWHoOOUVZfqnHIyU/VaObOcXW7n3cDkubXyEdRDmSVKMAJI+O50Y1SHDgiCYtJzBJnCOSlgh4eH3SdkSAU1gylnzq2Kz4Aq1bMJz+OgtlCBNDqYtyi0uD6BeNgT2vNkwE52c2aNpW2W/M+2FfMCd2hqsXE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.com; spf=fail smtp.mailfrom=linux.com; arc=none smtp.client-ip=62.72.0.81 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.com Authentication-Results: smtp.subspace.kernel.org; spf=fail smtp.mailfrom=linux.com Received: by gentwo.org (Postfix, from userid 1003) id CA6CD40A9B; Wed, 13 Mar 2024 09:39:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by gentwo.org (Postfix) with ESMTP id C9A8340941; Wed, 13 Mar 2024 09:39:21 -0700 (PDT) Date: Wed, 13 Mar 2024 09:39:21 -0700 (PDT) From: "Christoph Lameter (Ampere)" To: Marek Szyprowski cc: Sudeep Holla , Catalin Marinas , Mark Rutland , "linux-pm@vger.kernel.org" , "Rafael J. Wysocki" , Viresh Kumar , Will Deacon , Jonathan.Cameron@huawei.com, Matteo.Carlini@arm.com, Valentin.Schneider@arm.com, akpm@linux-foundation.org, anshuman.khandual@arm.com, Eric Mackay , dave.kleikamp@oracle.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux@armlinux.org.uk, robin.murphy@arm.com, vanshikonda@os.amperecomputing.com, yang@os.amperecomputing.com, Nishanth Menon , Stephen Boyd Subject: Re: [PATCH v3] ARM64: Dynamically allocate cpumasks and increase supported CPUs to 512 In-Reply-To: <432c1980-b00f-4b07-9e24-0bec52ccb5d6@samsung.com> Message-ID: <173078dd-3743-2d39-a9ea-015ea5be48f8@linux.com> References: <37099a57-b655-3b3a-56d0-5f7fbd49d7db@gentwo.org> <9352f410-9dad-ac89-181a-b3cfc86176b8@linux.com> <432c1980-b00f-4b07-9e24-0bec52ccb5d6@samsung.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-2114933744-1710347961=:1414196" This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-2114933744-1710347961=:1414196 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT 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. --8323329-2114933744-1710347961=:1414196--