public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Jacopo Labardi <jacopolabardi@gmail.com>
Cc: linux-nvme@lists.infradead.org, linux-pci@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [BUG] Lenovo 83JL / WD SN7100S: intermittent loss of secondary NVMe after s2idle resume, root port 00:02.1 retraining fails
Date: Thu, 9 Apr 2026 14:05:15 -0500	[thread overview]
Message-ID: <20260409190515.GA407093@bhelgaas> (raw)
In-Reply-To: <CANrGBMBDftu58R71jvEcZ94D8vJB2Y_dHG=BbNSsNMOS=3k0+g@mail.gmail.com>

On Thu, Apr 09, 2026 at 04:52:20PM +0200, Jacopo Labardi wrote:
> Hello,
> 
> I am reporting an intermittent suspend/resume failure on a Lenovo IdeaPad Pro 5
> 14AKP10 (machine type 83JL) where the secondary NVMe drive can become unusable
> after s2idle resume on Linux.
> ...

> I collected a local bundle containing:
> - full kernel log from the reproducer boot
> - systemd suspend log
> - lspci -nnvv for 0000:00:02.1 and 0000:bf:00.0
> - sysfs power-state snapshots
> - dmidecode output
> 
> The raw bundle contains machine serial/UUID, so I am not attaching it publicly
> as-is. I can provide redacted logs or specific files immediately if requested.

Providing the complete logs with private information redacted would be
a good first step.

  reply	other threads:[~2026-04-09 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 14:52 [BUG] Lenovo 83JL / WD SN7100S: intermittent loss of secondary NVMe after s2idle resume, root port 00:02.1 retraining fails Jacopo Labardi
2026-04-09 19:05 ` Bjorn Helgaas [this message]
2026-04-09 19:18   ` Jacopo Labardi

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=20260409190515.GA407093@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=jacopolabardi@gmail.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@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