Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp267155imw; Fri, 8 Jul 2022 02:35:26 -0700 (PDT) X-Google-Smtp-Source: AGRyM1seY5J/Rxo4z7zwd14L0dz1Y+30Xvg3XkvrgkwofZyzPOuWzeQQDQIDcGOvs3PP/dACOH+L X-Received: by 2002:a17:90b:1c09:b0:1ef:f82c:174b with SMTP id oc9-20020a17090b1c0900b001eff82c174bmr439879pjb.88.1657272926299; Fri, 08 Jul 2022 02:35:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657272926; cv=none; d=google.com; s=arc-20160816; b=Jxbsxj76kGBwGDu5l6A34ih+nqEfeUVqJ3bHyC3aUfNy1Dt1XF75P15dru90jYdlQZ WJJMMFO8ZWDGITqcHyosSRjKA3RgO+pLRr2kGfQMn454xM25GRGgCeJ2PsvNGfWehXqq xO6AnmCUvEosmGKONWnqKjO1tks1aUa5gDO8RDfD/+wRsjIubJW1e3A0Y3a/pkHDze+S h0VhndUQh408kkuIVR52NGsMGMRkkZRVz7KsBMsAdVERUwC2/Ip0p2vj17HRKJxH7Xag z4Q+V+DGam5LVBKil2EbAX58AycWn9C89gbnzFulGTW3GjXjdbaDt7P3cnSdvy7ezjrR fUKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=Y0gFTgEw8o/sZzcpqT/zqeJVyFwXwGnVGICet2zwIx0=; b=VX55qCbV/3j2Bby2cU1Lk2D6qiZO7nl47qMu4EivTTxnP9PQRL0GMtU5XA801svUIT g2EU49t8ml10LJE7jB4tto92P817BIIgWjJbZ1AxSvSAobvw6mxSxPjhBd0rxWjRqMMp fSLCSNZocW6RG8JKqOFjx0q1NEyH2nhF+lmOQEdhUTxLX76GT4IYw3zrqT/LRvG4mdvX I6GVpmjmpqsqZjtH3RpA54LEB3ahlWDxro3d0nqQVntHp1OrGA4MY7imaXdeOagr2+4z 9+vGRjM575+2oujIsKTxS1OT2bMO9ZtXcWJicu+Dh8CENJetnubC6dzs0L8DhaFKs55r jaSw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@fortu-net.20210112.gappssmtp.com header.s=20210112 header.b=sBE6RD34; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id f18-20020a056a00229200b0052840d91b55si2771658pfe.133.2022.07.08.02.35.13; Fri, 08 Jul 2022 02:35:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@fortu-net.20210112.gappssmtp.com header.s=20210112 header.b=sBE6RD34; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237298AbiGHJWx (ORCPT + 99 others); Fri, 8 Jul 2022 05:22:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43536 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237662AbiGHJWv (ORCPT ); Fri, 8 Jul 2022 05:22:51 -0400 Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A6C1830F58 for ; Fri, 8 Jul 2022 02:22:49 -0700 (PDT) Received: by mail-pl1-x633.google.com with SMTP id f11so3329429plr.4 for ; Fri, 08 Jul 2022 02:22:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fortu-net.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Y0gFTgEw8o/sZzcpqT/zqeJVyFwXwGnVGICet2zwIx0=; b=sBE6RD34qzqgs778DVxBQqGSxgy5SBH9j19gPIGTpGn01WSwkFlOGZ+0RiCGEdX9mW BCWm4cukAIrNz3heoRcLqTnzf6Fb79D91vPm7Lul7XyT1jL0ol+sPsszXJGakic9tb/8 gfR1UWNSuMBmeFIxDl4gwFfphGhhWoH3sPlGZpW4bMJlQCmRA5UcpHxESPODbmJXEAr4 kdFbbvX83cDRmE7PQ+GWVqwtNaCR1AulbaGNQ/KsDJNhiwS4zGei/rWMUrMhN939PioD uBXBidrjE5H0VGsKmPBH6sczfM+gMgRxw7aC42HHLotuLdaGJ16/YLJvLW1aDXSceD/L GKFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Y0gFTgEw8o/sZzcpqT/zqeJVyFwXwGnVGICet2zwIx0=; b=c7EW0jit0X8bAeZeDbAprLH24P7AlqAxCrMbHRwi5JZj3rKvrG0nQS3IU3qowGqYJw UarHbq3gwbk6iVOTsXX6qxDm4IE9KRZc0aPW2hRnAzPJ8UkURUboRkLocMmIYth+HFGe SOmskXcWv9RfMCSLGob/qXl/99zDhE/TBrlwq81Ayaq1rSpEFAnYn3RrRvnb048px3t3 RFFeERnvUrjXDkNcwa71XDVPSoJiZ8XZ5GsseDcrZsr1ao/E7ZO6tFQKyH3mSSWzmjII 25IOfIFsVBm9+e6b3ylGhaUWcCX8zpiCpSuMBMrT8b+xpAf4R7v8m9ihSOoBxPrAnrAL PTvA== X-Gm-Message-State: AJIora90plTvQQYiSXWw2JuRJGbDcKTqMijLJXC6K1kkMBANdSwuyu+K 2IEXvD1osMcN0EC8SpAtSMGQZxciiVxEcnoU0m3P X-Received: by 2002:a17:90b:1b07:b0:1ec:c617:a314 with SMTP id nu7-20020a17090b1b0700b001ecc617a314mr2890719pjb.214.1657272169161; Fri, 08 Jul 2022 02:22:49 -0700 (PDT) MIME-Version: 1.0 References: <20220328111828.1554086-1-sashal@kernel.org> <20220328111828.1554086-42-sashal@kernel.org> <872f2a21-7bf7-0cc3-298f-f817429f6997@fortu.net> In-Reply-To: From: Tom Crossland Date: Fri, 8 Jul 2022 11:22:38 +0200 Message-ID: Subject: Re: [PATCH AUTOSEL 5.17 42/43] Revert "ACPI: Pass the same capabilities to the _OSC regardless of the query flag" To: "Limonciello, Mario" Cc: Sasha Levin , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , "Rafael J. Wysocki" , "Huang, Ray" , Mika Westerberg , "rafael@kernel.org" , "linux-acpi@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I can confirm that the ACPI BIOS Errors no longer appear in the kernel log using mainline 5.19.0-rc5 with the patch applied. Many thanks On Thu, Jul 7, 2022 at 11:36 PM Limonciello, Mario wrote: > > [Public] > > > > > -----Original Message----- > > From: Tom Crossland > > Sent: Thursday, July 7, 2022 16:31 > > To: Sasha Levin ; linux-kernel@vger.kernel.org; > > stable@vger.kernel.org > > Cc: Rafael J. Wysocki ; Limonciello, Mario > > ; Huang, Ray ; Mika > > Westerberg ; rafael@kernel.org; linux- > > acpi@vger.kernel.org > > Subject: Re: [PATCH AUTOSEL 5.17 42/43] Revert "ACPI: Pass the same > > capabilities to the _OSC regardless of the query flag" > > > > Hi, I'm observing the issue described here which I think is due to a > > recent regression: > > > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c > > om%2Fintel%2Flinux-intel- > > lts%2Fissues%2F22&data=05%7C01%7CMario.Limonciello%40amd.com%7 > > C77419b612f9540e333ff08da606002ee%7C3dd8961fe4884e608e11a82d994e18 > > 3d%7C0%7C0%7C637928263354159054%7CUnknown%7CTWFpbGZsb3d8eyJWI > > joiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300 > > 0%7C%7C%7C&sdata=X%2FEAU9GbRD%2FfYxCMUmnWI1cJ8dk8sICk0iYu > > %2BKGqtl4%3D&reserved=0 > > > > sudo dmesg -t -l err > > > > ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], > > AE_NOT_FOUND (20211217/psargs-330) > > ACPI Error: Aborting method \_PR.PR01._CPC due to previous error > > (AE_NOT_FOUND) (20211217/psparse-529) > > ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], > > AE_NOT_FOUND (20211217/psargs-330) > > ACPI Error: Aborting method \_PR.PR02._CPC due to previous error > > (AE_NOT_FOUND) (20211217/psparse-529) > > ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], > > AE_NOT_FOUND (20211217/psargs-330) > > ACPI Error: Aborting method \_PR.PR03._CPC due to previous error > > (AE_NOT_FOUND) (20211217/psparse-529) > > > > System: > > Kernel: 5.18.9-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 12.1.0 > > parameters: initrd=\intel-ucode.img initrd=\initramfs-linux.img > > root=xxx intel_iommu=on iommu=pt > > Machine: > > Type: Desktop Mobo: Intel model: NUC7i5BNB v: J31144-304 serial: > > UEFI: Intel v: BNKBL357.86A.0088.2022.0125.1102 date: 01/25/2022 > > > > I hope this is the correct forum to report the issue. Apologies if not. > > > > This is the fix for it: > > https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=7feec7430edddb87c24b0a86b08a03d0b496a755 > > > > On 28/03/2022 13.18, Sasha Levin wrote: > > > From: "Rafael J. Wysocki" > > > > > > [ Upstream commit 2ca8e6285250c07a2e5a22ecbfd59b5a4ef73484 ] > > > > > > Revert commit 159d8c274fd9 ("ACPI: Pass the same capabilities to the > > > _OSC regardless of the query flag") which caused legitimate usage > > > scenarios (when the platform firmware does not want the OS to control > > > certain platform features controlled by the system bus scope _OSC) to > > > break and was misguided by some misleading language in the _OSC > > > definition in the ACPI specification (in particular, Section 6.2.11.1.3 > > > "Sequence of _OSC Calls" that contradicts other perts of the _OSC > > > definition). > > > > > > Link: > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.ker > > nel.org%2Flinux- > > acpi%2FCAJZ5v0iStA0JmO0H3z%2BVgQsVuQONVjKPpw0F5HKfiq%3DGb6B5yw% > > 40mail.gmail.com&data=05%7C01%7CMario.Limonciello%40amd.com%7C > > 77419b612f9540e333ff08da606002ee%7C3dd8961fe4884e608e11a82d994e183 > > d%7C0%7C0%7C637928263354159054%7CUnknown%7CTWFpbGZsb3d8eyJWIj > > oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300 > > 0%7C%7C%7C&sdata=Te3BK%2B0q2QmrqqoG5mbV%2FNguoMgiwzILNHl > > %2BhUMLFlY%3D&reserved=0 > > > Reported-by: Mario Limonciello > > > Signed-off-by: Rafael J. Wysocki > > > Tested-by: Mario Limonciello > > > Acked-by: Huang Rui > > > Reviewed-by: Mika Westerberg > > > Signed-off-by: Sasha Levin > > > --- > > > drivers/acpi/bus.c | 27 +++++++++++++++++++-------- > > > 1 file changed, 19 insertions(+), 8 deletions(-) > > > > > > diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c > > > index 07f604832fd6..079b952ab59f 100644 > > > --- a/drivers/acpi/bus.c > > > +++ b/drivers/acpi/bus.c > > > @@ -332,21 +332,32 @@ static void > > acpi_bus_osc_negotiate_platform_control(void) > > > if (ACPI_FAILURE(acpi_run_osc(handle, &context))) > > > return; > > > > > > - kfree(context.ret.pointer); > > > + capbuf_ret = context.ret.pointer; > > > + if (context.ret.length <= OSC_SUPPORT_DWORD) { > > > + kfree(context.ret.pointer); > > > + return; > > > + } > > > > > > - /* Now run _OSC again with query flag clear */ > > > + /* > > > + * Now run _OSC again with query flag clear and with the caps > > > + * supported by both the OS and the platform. > > > + */ > > > capbuf[OSC_QUERY_DWORD] = 0; > > > + capbuf[OSC_SUPPORT_DWORD] = > > capbuf_ret[OSC_SUPPORT_DWORD]; > > > + kfree(context.ret.pointer); > > > > > > if (ACPI_FAILURE(acpi_run_osc(handle, &context))) > > > return; > > > > > > capbuf_ret = context.ret.pointer; > > > - osc_sb_apei_support_acked = > > > - capbuf_ret[OSC_SUPPORT_DWORD] & > > OSC_SB_APEI_SUPPORT; > > > - osc_pc_lpi_support_confirmed = > > > - capbuf_ret[OSC_SUPPORT_DWORD] & > > OSC_SB_PCLPI_SUPPORT; > > > - osc_sb_native_usb4_support_confirmed = > > > - capbuf_ret[OSC_SUPPORT_DWORD] & > > OSC_SB_NATIVE_USB4_SUPPORT; > > > + if (context.ret.length > OSC_SUPPORT_DWORD) { > > > + osc_sb_apei_support_acked = > > > + capbuf_ret[OSC_SUPPORT_DWORD] & > > OSC_SB_APEI_SUPPORT; > > > + osc_pc_lpi_support_confirmed = > > > + capbuf_ret[OSC_SUPPORT_DWORD] & > > OSC_SB_PCLPI_SUPPORT; > > > + osc_sb_native_usb4_support_confirmed = > > > + capbuf_ret[OSC_SUPPORT_DWORD] & > > OSC_SB_NATIVE_USB4_SUPPORT; > > > + } > > > > > > kfree(context.ret.pointer); > > > }