public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux NVMe <linux-nvme@lists.infradead.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Chaitanya Kulkarni <kch@nvidia.com>,
	Christoph Hellwig <hch@lst.de>,
	gloriouseggroll@gmail.com, Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: Fwd: Regression: Kernel 6.4 rc1 and higher causes Steam Deck to fail to wake from suspend (bisected)
Date: Tue, 18 Jun 2024 11:19:52 -0500	[thread overview]
Message-ID: <20240618161952.GA1258613@bhelgaas> (raw)
In-Reply-To: <b4d09ffc-a8e4-4e9f-9032-7c8583ca6abd@leemhuis.info>

On Tue, Jun 18, 2024 at 08:42:07AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> Hi Bjorn!
> 
> On 08.05.24 17:49, Bjorn Helgaas wrote:
> > On Tue, Oct 31, 2023 at 03:21:20PM +0700, Bagas Sanjaya wrote:
> >>
> >> I notice a regression report on Bugzilla [1]. Quoting from it:
> >> 
> >>> On Kernel 6.4 rc1 and higher if you put the Steam Deck into suspend then press the power button again it will not wake up. 
> >>>
> >>> I don't have a clue as to -why- this commit breaks wake from suspend on steam deck, but it does. Bisected to:
> >>>
> >>> ```
> >>> 1ad11eafc63ac16e667853bee4273879226d2d1b is the first bad commit
> >>> commit 1ad11eafc63ac16e667853bee4273879226d2d1b
> >>> Author: Bjorn Helgaas <bhelgaas@google.com>
> >>> Date:   Tue Mar 7 14:32:43 2023 -0600
> >>>
> >>>     nvme-pci: drop redundant pci_enable_pcie_error_reporting()
> >>>     
> >>>     pci_enable_pcie_error_reporting() enables the device to send ERR_*
> >>>     Messages.  Since f26e58bf6f54 ("PCI/AER: Enable error reporting when AER is
> >>>     native"), the PCI core does this for all devices during enumeration, so the
> >>>     driver doesn't need to do it itself.
> >>> [...]
> >>>
> >>> Reverting that commit by itself on top of 6.5.9 (stable) allows it to wake from suspend properly.
> >>
> >>> https://bugzilla.kernel.org/show_bug.cgi?id=218090
> >>
> > I don't think regzbot picked this up [...]
> 
> This is still open and it seems nothing happened for a few weeks now
> (sorry, should have sent a reminder earlier, but such old regressions
> have a lower priority here). Did it fall through the cracks or is this
> some good reason why giving up on this one might be the right thing to do?

Thanks for the reminder.  Will work on it today.

Bjorn


      reply	other threads:[~2024-06-18 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31  8:21 Fwd: Regression: Kernel 6.4 rc1 and higher causes Steam Deck to fail to wake from suspend (bisected) Bagas Sanjaya
2023-11-01 11:45 ` Bjorn Helgaas
2024-03-30 13:46   ` Bjorn Helgaas
2024-04-10  6:20     ` Kai-Heng Feng
2024-04-10 20:59       ` Bjorn Helgaas
2024-05-08 15:49 ` Bjorn Helgaas
2024-06-18  6:42   ` Linux regression tracking (Thorsten Leemhuis)
2024-06-18 16:19     ` Bjorn Helgaas [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=20240618161952.GA1258613@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bagasdotme@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=gloriouseggroll@gmail.com \
    --cc=hch@lst.de \
    --cc=kch@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=regressions@lists.linux.dev \
    /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