[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <954f0b86-dd9e-4d84-8d67-fba7e80bc94e@5challer.de>
Date: Fri, 5 Jan 2024 12:18:32 +0100
From: Michael Schaller <michael@...aller.de>
To: Kai-Heng Feng <kai.heng.feng@...onical.com>
Cc: Bjorn Helgaas <helgaas@...nel.org>, bhelgaas@...gle.com,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
regressions@...ts.linux.dev, macro@...am.me.uk, ajayagarwal@...gle.com,
sathyanarayanan.kuppuswamy@...ux.intel.com, gregkh@...uxfoundation.org,
hkallweit1@...il.com, michael.a.bottini@...ux.intel.com,
johan+linaro@...nel.org
Subject: Re: [Regression] [PCI/ASPM] [ASUS PN51] Reboot on resume attempt
(bisect done; commit found)
On 05.01.24 04:25, Kai-Heng Feng wrote:
> Just wondering, does `echo 0 > /sys/power/pm_asysnc` help?
Yes, `echo 0 | sudo tee /sys/power/pm_async` does indeed also result in
a working resume. I've tested this on kernel 6.6.9 (which still has
commit 08d0cc5f3426). I've also attached the relevant dmesg output of
the suspend/resume cycle in case this helps.
Furthermore does this mean that commit 08d0cc5f3426 isn't at fault but
rather that we are dealing with a timing issue?
Michael
View attachment "dmesg-with-pm-async-disabled.txt" of type "text/plain" (10164 bytes)
Powered by blists - more mailing lists