[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <027efc9e-bc70-49af-7d48-fb474533993d@linux.intel.com>
Date: Wed, 5 Feb 2025 10:44:31 +0200 (EET)
From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To: Paul Menzel <pmenzel@...gen.mpg.de>
cc: Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org,
linux-pm@...r.kernel.org, regressions@...ts.linux.dev,
Ulf Hansson <ulf.hansson@...aro.org>, linux-mmc@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>, Hans de Goede <hdegoede@...hat.com>
Subject: Re: Linux warns `rtsx_pci 0000:3b:00.0: PM: dpm_run_callback():
pci_pm_resume returns -110`
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.
Powered by blists - more mailing lists