From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-pm@vger.kernel.org,
regressions@lists.linux.dev,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: Linux warns `rtsx_pci 0000:3b:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110`
Date: Wed, 5 Feb 2025 10:44:31 +0200 (EET) [thread overview]
Message-ID: <027efc9e-bc70-49af-7d48-fb474533993d@linux.intel.com> (raw)
In-Reply-To: <d7246feb-4f3f-4d0c-bb64-89566b170671@molgen.mpg.de>
On Tue, 4 Feb 2025, Paul Menzel wrote:
> #regzbot introduced: b46c89c08f41..aa22f4da2a46
>
> Dear Linux folks,
>
>
> On the Intel Kaby Lake laptop Dell XPS 13 9360, at least Linux
> 6.13.0-07632-gaa22f4da2a46 logs the new warnings:
>
> rtsx_pci 0000:3b:00.0: Unable to change power state from D0 to D3hot,
> device inaccessible
> rtsx_pci 0000:3b:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110
> rtsx_pci 0000:3b:00.0: PM: failed to resume async: error -110
>
> These were not present up to including Linux 6.13.0-07078-gb46c89c08f41.
>
> It looks like the first warning is not always logged:
>
> $ sudo dmesg | grep rtsx
> [ 8.612537] rtsx_pci 0000:3b:00.0: enabling device (0000 -> 0002)
> [ 2010.081170] rtsx_pci 0000:3b:00.0: Unable to change power state from D0
> to D3hot, device inaccessible
> [ 2010.236503] rtsx_pci 0000:3b:00.0: PM: dpm_run_callback():
> pci_pm_resume returns -110
> [ 2010.236525] rtsx_pci 0000:3b:00.0: PM: failed to resume async: error
> -110
> [ 4115.541202] rtsx_pci 0000:3b:00.0: PM: dpm_run_callback():
> pci_pm_resume returns -110
> [ 4115.541216] rtsx_pci 0000:3b:00.0: PM: failed to resume async: error
> -110
>
> Logs from Linux 6.14-rc1 are attached. Bisection is only possible after next
> Sunday.
Please try if this fix helps:
https://lore.kernel.org/linux-pci/20250131152913.2507-1-ilpo.jarvinen@linux.intel.com/
--
i.
next prev parent reply other threads:[~2025-02-05 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 21:55 Linux warns `rtsx_pci 0000:3b:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110` Paul Menzel
2025-02-05 8:44 ` Ilpo Järvinen [this message]
2025-02-05 21:48 ` Paul Menzel
2025-02-05 23:38 ` Bjorn Helgaas
2025-02-06 7:43 ` Paul Menzel
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=027efc9e-bc70-49af-7d48-fb474533993d@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
--cc=ulf.hansson@linaro.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 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.