public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.13 000/443] 6.13.3-rc1 review
Date: Fri, 14 Feb 2025 09:42:17 +0100	[thread overview]
Message-ID: <2025021459-guise-graph-edb3@gregkh> (raw)
In-Reply-To: <e7096ec2-68db-fc3e-9c48-f20d3e80df72@applied-asynchrony.com>

On Fri, Feb 14, 2025 at 09:32:06AM +0100, Holger Hoffstätte wrote:
> On 2025-02-13 15:22, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.13.3 release.
> > There are 443 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> 
> Builds & runs fine BUT fails to suspend to RAM 99.99% of the time (basically
> one success but never again). Display powers down but fans stay on.
> 
> Tested on multiple systems, all x64. I first suspected amdgpu because why not :)
> but it also fails on a system without amdgpu, so that's not it.
> 
> Reverting to 6.13.2 immediately fixes everything.
> 
> Common symptom on all machines seems to be
> 
> [  +0.000134] Disabling non-boot CPUs ...
> [  +0.000072] Error taking CPU15 down: -16
> [  +0.000002] Non-boot CPUs are not disabled
> 
> "Error taking down CPUX" is always the highest number of CPU, i.e.
> 15 on my 16-core Zen2 laptop, 3 on my 4-core Sandybridge etc.
> 
> I started to revert suspects but no luck so far:
> - acpi parsing order
> - amdgpu backlight quirks
> - timers/hrtimers
> 
> Suggestions for other suspects are welcome.

Can you run 'git bisect' to try to find the offending change?

thanks,

greg k-h

  reply	other threads:[~2025-02-14  8:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 14:22 [PATCH 6.13 000/443] 6.13.3-rc1 review Greg Kroah-Hartman
2025-02-13 14:22 ` [PATCH 6.13 006/443] arm64/mm: Ensure adequate HUGE_MAX_HSTATE Greg Kroah-Hartman
2025-02-13 19:55 ` [PATCH 6.13 000/443] 6.13.3-rc1 review Pavel Machek
2025-02-13 20:04 ` Florian Fainelli
2025-02-13 20:52 ` Takeshi Ogasawara
2025-02-13 22:57 ` Justin Forbes
2025-02-13 23:59 ` Mark Brown
2025-02-14  0:58 ` [PATCH 6.13 000/619] " Hardik Garg
2025-02-14  3:52 ` [PATCH 6.13 000/443] " Peter Schneider
2025-02-14  6:09 ` Ron Economos
2025-02-14  6:42 ` Luna Jernberg
2025-02-14 10:16   ` Luna Jernberg
2025-02-14  8:32 ` Holger Hoffstätte
2025-02-14  8:42   ` Greg Kroah-Hartman [this message]
2025-02-14  9:06     ` Holger Hoffstätte
2025-02-14 10:12     ` Holger Hoffstätte
2025-02-14 13:07       ` Greg Kroah-Hartman
2025-02-14  9:45 ` Jon Hunter
  -- strict thread matches above, loose matches on Subject: below --
2025-02-13 17:06 Ronald Warsow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2025021459-guise-graph-edb3@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=holger@applied-asynchrony.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox