mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
	linux-kernel@vger.kernel.org, Naohiro.Aota@wdc.com,
	kernel-team@meta.com, Bjorn Andersson <andersson@kernel.org>
Subject: Re: Workqueue regression
Date: Fri, 2 Feb 2024 08:40:44 -1000	[thread overview]
Message-ID: <Zb03LDPmMcBU0-Gj@slm.duckdns.org> (raw)
In-Reply-To: <17cae1aa-98a8-48f4-adf3-2ddfc451bef6@linaro.org>

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

  reply	other threads:[~2024-02-02 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 20:57 Konrad Dybcio
2024-02-02  1:52 ` Tejun Heo
2024-02-02 12:31   ` Konrad Dybcio
2024-02-02 18:40     ` Tejun Heo [this message]
2024-02-04 21:19       ` Tejun Heo
2024-02-05 11:43         ` Konrad Dybcio

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=Zb03LDPmMcBU0-Gj@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=Naohiro.Aota@wdc.com \
    --cc=andersson@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome