From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (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 F326643F0AA for ; Mon, 24 Aug 2026 15:29:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787585384; cv=none; b=Ojy3y8jps0oJNCFmTxncjbfSRE2nT2jWtWptWN9Ii+TP3vEPP+k42JavOfQd7dBeJ3vXyu2dz2vsASwIHGvZQBGLeseEJp8dpbVHXQQ+LVj6SP5Yp1WS0BdaD2dTrojPoMgI/Tbp9nJKp7yrW9u9uAaD3KxXsXHGIxiP1FAuQrs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787585384; c=relaxed/simple; bh=HWI3e9E0H1RApk6fXstUQ5pzjk2rBkbElJqKtYRiNH4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=gyYE4NGJ8cv5pQ9785PC8c4G5kVq3Zj6OIOLQCLGAk+dUZKYTUCHhC8EL/7fbyvXWvcswM8Ghp56wpPNr7ZxtTRrGlvaBjWoh9joAuujLF8CUEy0g6nQjKqGc5FKvsYBqVXG23LSs61p7erENfwWAkKgelwlE+R52CiFOU2Ohjg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=dWHpnMI9; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b=qA1GIWBD; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="dWHpnMI9"; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b="qA1GIWBD" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1787585380; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=/goNprm3vb+vqF+2+ZaUSBOvzdh+ZGsOcB6bvYFMahs=; b=dWHpnMI9KLnxCUbUwoz/Qb/oJXKZzWvjL60pzC6v2rIE0fLTeU087rD+KNHjZip6Yuz6/i r+tXrumCl7ZHRYiQUDx0eSyaa/R3OEC5tBnAM5Efl3G+bX+DOxnwWD/J5dT56nAZ0iw4by WXKvc1gLtQrQeWfAgqQjUEyHNr58+1s= Received: from mail-qv1-f70.google.com (mail-qv1-f70.google.com [209.85.219.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-665--hdf3zn7NUiaIl8hDxNmZw-1; Mon, 24 Aug 2026 11:29:38 -0400 X-MC-Unique: -hdf3zn7NUiaIl8hDxNmZw-1 X-Mimecast-MFC-AGG-ID: -hdf3zn7NUiaIl8hDxNmZw_1787585378 Received: by mail-qv1-f70.google.com with SMTP id 6a1803df08f44-907ca5abf1bso20715836d6.0 for ; Mon, 24 Aug 2026 08:29:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=google; t=1787585378; x=1788190178; darn=vger.kernel.org; h=user-agent:in-reply-to:content-disposition:content-type :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to:content-type; bh=/goNprm3vb+vqF+2+ZaUSBOvzdh+ZGsOcB6bvYFMahs=; b=qA1GIWBDtQ0UFIf02rgCnPNQqvvbVnBb9qQQ4OXOVwSIyWnUk9x3RjDdISLXLvMSJc 5p6BknkwRcfQBcAZgrvAEU9xRFUOC6V0ZqsgkLzaG+Lc86AIaL7JKO2w7R/M8W9uq1xj lqOtfAEYkhYvPBi0GRN1t3zZ0GlUMxW0/t0Wg1fuG9fBQLJV4PirDWUwoFFzxm4j9yDQ WuTSX5a1JFs/PG9D6NZDhyI5zxFzR9SCQfEmFZ60vJwW6j7i8B2i8bkBrG/Bgf2C0wJH vWmbf1641oP858Mh+uY4Dp31AxKBTTMgMevdEq/L/+avOWt4RnXk/Bb3oFxDVifgtCjq ES3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1787585378; x=1788190178; h=user-agent:in-reply-to:content-disposition:content-type :mime-version:references:message-id:subject:cc:to:from:date:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=/goNprm3vb+vqF+2+ZaUSBOvzdh+ZGsOcB6bvYFMahs=; b=Xq68Clp0UUyxxZWZ7U+n/NEWjxo91JrJY7lGQSSdFxWC/H8WzM1Lj11yvE/1y/4otK fCKNlwUQTnHSzQHiCzSMTotCq2WsKFsXDvjgzoQh3z2o3B+xBGHjUqFFiGE6Zfu3Oj1V O+UM8r0U4fHSNu3o9lhC3WAqKtJ6nkQqZ532UDjjYjhIg0KOMvirsBVQ8tA1P7Ah/tSr 928MmbvbPxjGFzpakJZfq35Q8vVO4XeFji4uGskA8s23kzctVU3AWsnvztOfWFS5/Wzq L9RFgm/MoDq146b9UiqfXJTD6Mzm0vEFEYcbNSuncyWKO9DpQo/isFJlAtbAq/iiYprR S2Kw== X-Forwarded-Encrypted: i=1; AHgh+Rqqjz9+RrdvfUY+FTOPDUkFaiaOe3/ffCTYibggJEf0tMtWs4Pxn0c1bRrkSyZ3j9tKyyHEIq68XidKBL8=@vger.kernel.org X-Gm-Message-State: AFuF++kWLGXRjZFppbgtBSa8G5MOp4FLBzP6+WBxyaex7Dpaxx+hVerQ bKZmRqU7JVKNN8fINwokkoJ8NpohB8zKX9azZwo/sdIS6GOhGO+fJbDxSGhw9G/Tq7dORsxspfk /PJHgICgLGI4P9/J+oiAsbXuHGeb8vQ/yl10s5p4g2wAIvaKcvNcMfkmx+3zn60RuCA== X-Gm-Gg: AR+sD10KzWX9AGoj2x4TYKBOAHscFw+4wZQlNfDDuKWqes6lIc6LwF76WbVPd4gcDws Sb0wcxGrtshVDylNj2CEFR29Q/nR6OQvNFkALqDaIRxMkXkjpytKKCGkPp6B26TiBZvnTdY5ZDz 5d9FPwM5+zzJh6ga35nCwKQg5PcWHux61Wj/id8LFXY5z71LZSv099itAfjaF6gy5dVqkZly2mu 8LHGMzMMYd5SWFMKpr07I2MoJ1nzzNUPN63oZUA8DlFkRVhUmwsEYC9lpeNW2zx93so73/Tv59q tz22edpkObTI6ROo+L0ooaqzgkUOJjiPa1UVqxWeajS3Qw3rmTg09EnfEjbF777E5GumqIQ77z1 LP9JEnuoycZitbIY2VtbB6zTYZ6Gr/S+C6+M= X-Received: by 2002:a05:6214:212d:b0:8c4:edb4:a44a with SMTP id 6a1803df08f44-90c80f9357fmr293301106d6.23.1787585377978; Mon, 24 Aug 2026 08:29:37 -0700 (PDT) X-Received: by 2002:a05:6214:212d:b0:8c4:edb4:a44a with SMTP id 6a1803df08f44-90c80f9357fmr293300306d6.23.1787585377513; Mon, 24 Aug 2026 08:29:37 -0700 (PDT) Received: from redhat.com (c-73-183-53-213.hsd1.pa.comcast.net. [73.183.53.213]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-90c936183d0sm65105676d6.22.2026.08.24.08.29.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 24 Aug 2026 08:29:36 -0700 (PDT) Date: Mon, 24 Aug 2026 11:29:35 -0400 From: Brian Masney To: Lucas Tanure Cc: Neil Armstrong , Jerome Brunet , Michael Turquette , Stephen Boyd , Kevin Hilman , Jian Hu , Martin Blumenstingl , linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [RFC] clk: meson: t7: Intermittent boot instability and memory corruption on VIM4 Message-ID: References: <3930906f-783b-4d72-9260-ba25cc8081cb@linux.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3930906f-783b-4d72-9260-ba25cc8081cb@linux.com> User-Agent: Mutt/2.4.0 (2026-06-19) Hi Lucas, On Sun, Aug 23, 2026 at 04:40:42PM +0100, Lucas Tanure wrote: > While testing mainline Linux on the Khadas VIM4 (Amlogic A311D2 / T7), I am > hitting intermittent system instability, storage loss, and memory corruption > during boot, unless I append clk_ignore_unused to the kernel command line. > > Because the failure is intermittent, I am running 100-reboot test campaigns > to bisect the remaining clocks and isolate which clocks are critical and > cannot be safely disabled. > > As testing takes significant time over serial console, I wanted to check if > Amlogic or the maintainers could shed light on this: > > Are there specific T7 clocks or hardware domains that must remain > critical/protected even without an explicit in-kernel consumer? > > Current clocks being disabled that don't kill the board on a test run: > > [ 0.380313] clk: Disabling unused clocks > [ 0.380413] clk: Disabled unused clock: rtc_dualdiv > [ 0.380718] clk: Disabled unused clock: rtc_duandiv_in > [ 0.381377] clk: Unprepared unused clock: a73_div16 > [ 0.381972] clk: Unprepared unused clock: cpu_div16 > [ 0.382605] clk: Unprepared unused clock: f50m > [ 0.383174] clk: Unprepared unused clock: fixed_pll_dco > [ 0.383786] clk: Unprepared unused clock: hdmi_pll_osc > [ 0.384416] clk: Unprepared unused clock: sys1_pll_osc > [ 0.385056] clk: Unprepared unused clock: earc_osc > [ 0.385652] clk: Unprepared unused clock: pcie_refclk_osc > [ 0.386323] clk: Unprepared unused clock: eth_pll_osc > [ 0.386961] clk: Unprepared unused clock: pcie_osc > [ 0.387548] clk: Unprepared unused clock: mclk_pll_osc > [ 0.388187] clk: Unprepared unused clock: usb_pll1_osc > [ 0.388826] clk: Unprepared unused clock: usb_pll0_osc > [ 0.389465] clk: Unprepared unused clock: tcon_pll_osc > [ 0.390105] clk: Unprepared unused clock: top_pll_osc > [ 0.390738] clk: Unprepared unused clock: aud_pll_osc > [ 0.391361] clk: Unprepared unused clock: ddr_pll_osc > > I am not forcing any clock to be disabled; I am forcing all clocks to stay > on and letting them be disabled if unused one by one. > > Any guidance or hints on required platform clocks would be greatly > appreciated. I have an outstanding series that disables unused clocks via the sync_state callback: https://lore.kernel.org/linux-clk/20260626-clk-sync-state-v1-0-4156d8196dc8@redhat.com/ Be sure to not have clk_ignore_unused in your kernel command line. I suggest comparing the list of which clocks are disabled with that series against your list of clocks above. Brian