linux-kernel - Re: Workqueue regression

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]

Date: Fri, 2 Feb 2024 08:40:44 -1000
From: Tejun Heo <tj@...nel.org>
To: Konrad Dybcio <konrad.dybcio@...aro.org>
Cc: Konrad Dybcio <konradybcio@...nel.org>, linux-kernel@...r.kernel.org,
	Naohiro.Aota@....com, kernel-team@...a.com,
	Bjorn Andersson <andersson@...nel.org>
Subject: Re: Workqueue regression

Hello,

On Fri, Feb 02, 2024 at 01:31:01PM +0100, Konrad Dybcio wrote:
> > If the system doesn't become live enough after suspend/resume cycle to get
> > more info, the following might help:
> 
> Looks like it's too far gone indeed..
> 
> > 
> > $ echo test_resume > /sys/power/disk
> > $ echo disk > /sys/power/state
> 
> Sadly, hibernation is not a thing on this platform.. Without going into much
> detail of how messy the power management stuff is, you can either have
> "on", "off" or "power collapsed" (bound to s2idle).. Trying to trigger this
> sequence makes the thing lock up and die due to unclocked accesses with or
> without the WQ regression.

I see, so, if you enable CONFIG_PM_DEBUG, CONFIG_PM_ADVANCED_DEBUG and
CONFIG_PM_SLEEP_DEBUG, there will be /sys/power/pm_test file which allows to
select the stage at which suspend is going to abort. Can you please play
with it and see whether you can reproduce the issue while maintaining the
console output?

Can you also make sure that the system is actually dead, not just the
console? e.g. by pinging from network?

Thanks.

-- 
tejun