From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from hognose1.porkbun.com (hognose1.porkbun.com [35.82.102.206]) (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 2AEAB3A4F32 for ; Fri, 21 Aug 2026 08:27:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=35.82.102.206 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787300853; cv=none; b=p9+QXR6lMJa3/kOAgcqTjJjM7QrrCDTWnEJypSqK4blbZMbE6/pHjzeVjzmyrOJysnhihW+bCbBIIrx4mWb6UB7G3/1tteo15vqOVCcghP7AP6miSvRGJn1DlcMvv/RKZvzkjvZh+XM3UuYwOl5e4JCGYzrw8aYDFl+ojZU80Pc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787300853; c=relaxed/simple; bh=Yk/uXQe7FEtVR0QMATjLf5bWi30rS3k9Y/+owy9juNE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=VRw1QQUOyGgCVNBEwHemj3C2otg4a+fwHIIW3TTHZAX6/z/UDyuNUlaQTZ+WM7dnpn2GcdZZN4/tD7w4+y7hPwmLauYb1Q1ObP501yktVXpwSoO4tvtTBP/BiAjmOYFgA9URSZ07P1apDzoe/VE/OnRzwsXBflxJrPV0jO27pYo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=holtechnik.com; spf=pass smtp.mailfrom=holtechnik.com; dkim=pass (1024-bit key) header.d=holtechnik.com header.i=@holtechnik.com header.b=JKyOfB2C; arc=none smtp.client-ip=35.82.102.206 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=holtechnik.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=holtechnik.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=holtechnik.com header.i=@holtechnik.com header.b="JKyOfB2C" Received: from localhost.localdomain (192-184-175-24.fiber.dynamic.sonic.net [192.184.175.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: phollinsky@holtechnik.com) by hognose1.porkbun.com (Postfix) with ESMTPSA id F10AE47DBA7; Fri, 21 Aug 2026 08:27:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=holtechnik.com; s=default; t=1787300851; bh=BeYDma4yqixg754zEJEPNG4NaT8r182s7Wc6Lq+Vgxs=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=JKyOfB2Chooz4/QDYnCC/6rW4ERTSqQcZTP3iU7lfzHM2lrIqJFzySI3h9SiwTlWT pEhfLUeJqXpdOcHJm7NHTOb7mUpvjTIbK80+NQRWDN0/eWMGOZE3V9eoSeeKsFdArK AkueiCrdo+beqd9tMd06ge2mINe9kklnsZ8h6hOk= From: Paul Hollinsky To: Thorsten Leemhuis , Konrad Dybcio Cc: Sumit Garg , Bjorn Andersson , Mathieu Poirier , Rob Clark , Dmitry Baryshkov , Abhinav Kumar , Akhil P Oommen , Konrad Dybcio , Mukesh Ojha , cros-qcom-dts-watchers@chromium.org, linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org, regressions@lists.linux.dev Subject: Re: [REGRESSION] qcom PAS TZ API migration breaks GPU and modem on TrustZone without PAS (sc7180 trogdor) Date: Fri, 21 Aug 2026 01:27:30 -0700 Message-ID: <20260821082730.89413-1-phollinsky@holtechnik.com> X-Mailer: git-send-email 2.55.0 In-Reply-To: <943d1db3-f117-4e9c-94db-7221b47d9d29@leemhuis.info> References: <943d1db3-f117-4e9c-94db-7221b47d9d29@leemhuis.info> Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit On 8/21/26 08:33, Thorsten Leemhuis wrote: > Just wondering: who will submit the proper fix to ideally fix this > before the culprit hits mainline I have now. I sent them as two separate patches, because the two culprits are in different places: drm/msm/adreno: Only check for PAS when a zap shader is present https://lore.kernel.org/r/20260821081325.89088-1-phollinsky@holtechnik.com 0be72be03ca7 has in fact already reached mainline, in this merge window, via the soc-drivers-7.3 pull (Linus' merge 368cf60c36a3). So this one is based on Linus' tree rather than on msm-fixes, which still predates the culprit - it went in through the qcom tree, not through msm. It is addressed to the msm maintainers, but it can just as easily go back through the tree the culprit came from. remoteproc: qcom_q6v5_mss: Don't require PAS for memory protection https://lore.kernel.org/r/20260821081540.89137-1-phollinsky@holtechnik.com f3b1357673dd is still only in remoteproc/rproc-next, so this one is based on that branch and would ideally be picked up there before it is sent on. Both are exactly the shapes Konrad agreed with in this thread, and both are tested on the affected machine (Lenovo IdeaPad Duet 3, sc7180-trogdor-wormdingler). #regzbot monitor: https://lore.kernel.org/r/20260821081325.89088-1-phollinsky@holtechnik.com #regzbot monitor: https://lore.kernel.org/r/20260821081540.89137-1-phollinsky@holtechnik.com All the best, Paul Hollinsky