lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250205233817.GA949434@bhelgaas>
Date: Wed, 5 Feb 2025 17:38:17 -0600
From: Bjorn Helgaas <helgaas@...nel.org>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
	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 Wed, Feb 05, 2025 at 10:48:24PM +0100, Paul Menzel wrote:
> Thank you for your instant reply.
> 
> Am 05.02.25 um 09:44 schrieb Ilpo Järvinen:
> > On Tue, 4 Feb 2025, Paul Menzel wrote:
> > 
> > > #regzbot introduced: b46c89c08f41..aa22f4da2a46
> 
> > > On the Intel Kaby Lake laptop Dell XPS 13 9360, at least Linux
> > > 6.13.0-07632-gaa22f4da2a46 logs the new warnings:
> 
> (Just a side note, these are actually logged with level error.)
> 
> > >      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.
> ...

> > Please try if this fix helps:
> > 
> > https://lore.kernel.org/linux-pci/20250131152913.2507-1-ilpo.jarvinen@linux.intel.com/
> 
> Yes, after applying the patch these errors were *not* logged in three ACPI
> S3 suspend/resume cycles.

Thanks, I added your Reported-by to the patch, which should appear in
v6.14-rc2.  Happy to also add your Tested-by if you feel confident
enough.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ