public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: David Lazar <dlazar@gmail.com>,
	stable@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
	Mark Pearson <mpearson-lenovo@squebb.ca>
Subject: Re: [PATCH 6.1.y] platform/x86: Add s2idle quirk for more Lenovo laptops
Date: Tue, 31 Oct 2023 12:05:18 +0100	[thread overview]
Message-ID: <2023103108-transpire-implosive-a7b2@gregkh> (raw)
In-Reply-To: <bb006649-bdf0-4dbf-bab6-45b06ecfdb10@amd.com>

On Mon, Oct 30, 2023 at 04:29:53PM -0500, Mario Limonciello wrote:
> On 10/30/2023 16:11, David Lazar wrote:
> > commit 3bde7ec13c971445faade32172cb0b4370b841d9 upstream.
> > 
> > When suspending to idle and resuming on some Lenovo laptops using the
> > Mendocino APU, multiple NVME IOMMU page faults occur, showing up in
> > dmesg as repeated errors:
> > 
> > nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000b
> > address=0xb6674000 flags=0x0000]
> > 
> > The system is unstable afterwards.
> > 
> > Applying the s2idle quirk introduced by commit 455cd867b85b ("platform/x86:
> > thinkpad_acpi: Add a s2idle resume quirk for a number of laptops")
> > allows these systems to work with the IOMMU enabled and s2idle
> > resume to work.
> > 
> > Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218024
> > Suggested-by: Mario Limonciello <mario.limonciello@amd.com>
> > Suggested-by: Mark Pearson <mpearson-lenovo@squebb.ca>
> > Signed-off-by: David Lazar <dlazar@gmail.com>
> > Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
> > Reviewed-by: Mark Pearson <mpearson-lenovo@squebb.ca>
> > Link: https://lore.kernel.org/r/ZTlsyOaFucF2pWrL@localhost
> > Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> > ---
> 
> As this is changed from the original commit in 6.6, you should add what you
> changed in why below the commit.  Something like:
> 
> Moved quirks into drivers/platform/x86/thinkpad_acpi.c since kernel 6.1
> doesn't include the refactor that moved it to AMD PMC driver.

No need, I can take this as-is.

thanks,

greg k-h

      reply	other threads:[~2023-10-31 11:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 21:11 [PATCH 6.1.y] platform/x86: Add s2idle quirk for more Lenovo laptops David Lazar
2023-10-30 21:29 ` Mario Limonciello
2023-10-31 11:05   ` Greg KH [this message]

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=2023103108-transpire-implosive-a7b2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dlazar@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=mario.limonciello@amd.com \
    --cc=mpearson-lenovo@squebb.ca \
    --cc=stable@vger.kernel.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