All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Yazen Ghannam <yazen.ghannam@amd.com>,
	Andreas Radke <andreas.radke@mailbox.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Subject: Re: [regression] x86/amd_nb in 6.9.6/6.6.35/6.1.95
Date: Fri, 21 Jun 2024 18:49:18 -0500	[thread overview]
Message-ID: <fe2a917e-754c-4990-9c3e-796412b47466@amd.com> (raw)
In-Reply-To: <20240621215656.GA20274@yaz-khff2.amd.com>

On 6/21/2024 16:56, Yazen Ghannam wrote:
> On Fri, Jun 21, 2024 at 11:29:11PM +0200, Andreas Radke wrote:
>> Am Fri, 21 Jun 2024 14:59:20 +0200
>> schrieb Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
>>
>>> I'm announcing the release of the 6.9.6 kernel.
>>>
>>> All users of the 6.9 kernel series must upgrade.
>>>
>>> The updated 6.9.y git tree can be found at:
>>> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>>> linux-6.9.y and can be browsed at the normal kernel.org git web
>>> browser: https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>>>
>>> thanks,
>>>
>>> greg k-h
>>
>> Subject: x86/amd_nb: Check for invalid SMN reads
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/patch/?id=348008f0043cd5ba915cfde44027c59bdb8a6791
>>
>> This commit is breaking lid close system suspend
>> and opening won't bring the laptop back and no input is possible anymore
>> here. I have to hard reboot the laptop. It's a Lenovo Thinkpad T14 Gen1.
>> There's nothing in the journal.
>>
>> Reverting this commit on top of 6.6.35 allows proper suspend/resume
>> again.
>>
> 
> Thanks Andy for the report.
> 
> Mario,
> Any ideas? Maybe something with the platform drivers?
> 
> Thanks,
> Yazen

Interesting; I've tested this patch in my own tree for a few weeks now 
and never hit this.

Can you please share a dmesg log from bootup?  Is there an "error 
reading" message from amd-pmc?

Separately can you please add a debug statement to amd-pmc around the 
two calls for:
	err = amd_smn_read(0, AMD_PMC_BASE_ADDR_LO, &val);
	err = amd_smn_read(0, AMD_PMC_BASE_ADDR_HI, &val);

Both with and without the patch?  I'm guessing one of them is (~0ULL) 
which is exactly what this patch is actually looking for now.


  reply	other threads:[~2024-06-21 23:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 12:59 Linux 6.9.6 Greg Kroah-Hartman
2024-06-21 12:59 ` Greg Kroah-Hartman
2024-06-21 21:29 ` [regression] x86/amd_nb in 6.9.6/6.6.35/6.1.95 Andreas Radke
2024-06-21 21:56   ` Yazen Ghannam
2024-06-21 23:49     ` Mario Limonciello [this message]
2024-06-23 17:03   ` Andreas Radke

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=fe2a917e-754c-4990-9c3e-796412b47466@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=andreas.radke@mailbox.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=yazen.ghannam@amd.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.