Received-SPF: pass (google.com: domain of linux-kernel+bounces-96260-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Sender: Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com>
Date: Thu, 7 Mar 2024 22:32:46 +0100
From: Salvatore Bonaccorso <carnil@debian.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux x86 Platform Drivers <platform-driver-x86@vger.kernel.org>,
	Linux Stable <stable@vger.kernel.org>
Subject: Re: Fwd: Continuous ACPI errors resulting in high CPU usage by
 journald
Message-ID: <ZeoyfjOdHECxn6ck@eldamar.lan>
References: <Zd2bsV8VsFJMlbFW@archie.me>
 <f7f6bcf7-c919-4077-88f6-bfffe112ba72@leemhuis.info>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f7f6bcf7-c919-4077-88f6-bfffe112ba72@leemhuis.info>

Hi,

On Thu, Feb 29, 2024 at 09:49:08AM +0100, Linux regression tracking #adding (Thorsten Leemhuis) wrote:
> [TLDR: I'm adding this report to the list of tracked Linux kernel
> regressions; the text you find below is based on a few templates
> paragraphs you might have encountered already in similar form.
> See link in footer if these mails annoy you.]
> 
> On 27.02.24 09:22, Bagas Sanjaya wrote:
> 
> > On Bugzilla, danilrybakov249@gmail.com reported stable-specific, ACPI error
> > regression that led into high CPU temperature [1]. He wrote:
> > [...]
> 
> #regzbot ^introduced 847e1eb30e269a094da046c08273abe3f3361cf2
> #regzbot duplicate: https://bugzilla.kernel.org/show_bug.cgi?id=218531
> #regzbot title platform/x86: p2sb: Continuous ACPI errors resulting in
> high CPU usage by journald
> #regzbot ignore-activity
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> That page also explains what to do if mails like this annoy you.

The fix for this issue seems to have landed in mainline:

aec7d25b497c ("platform/x86: p2sb: On Goldmont only cache P2SB and SPI devfn BAR")

Regards,
Salvatore