From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
Linux PM <linux-pm@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dmitry Vyukov <dvyukov@google.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v4] kernel/hung_task.c: disable on suspend
Date: Fri, 26 Oct 2018 11:23:34 +0200 [thread overview]
Message-ID: <1827523.RqSiaKuRRv@aspire.rjw.lan> (raw)
In-Reply-To: <CAJZ5v0iJmn4x+zqNhQ4zfYCucnZhYb2hK3o096xPX6Ju2zV2oQ@mail.gmail.com>
On Thursday, October 18, 2018 9:32:42 AM CEST Rafael J. Wysocki wrote:
> On Wed, Oct 17, 2018 at 1:24 PM Vitaly Kuznetsov <vkuznets@redhat.com> wrote:
> >
> > It is possible to observe hung_task complaints when system goes to
> > suspend-to-idle state:
> >
> > # echo freeze > /sys/power/state
> >
> > PM: Syncing filesystems ... done.
> > Freezing user space processes ... (elapsed 0.001 seconds) done.
> > OOM killer disabled.
> > Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
> > sd 0:0:0:0: [sda] Synchronizing SCSI cache
> > INFO: task bash:1569 blocked for more than 120 seconds.
> > Not tainted 4.19.0-rc3_+ #687
> > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > bash D 0 1569 604 0x00000000
> > Call Trace:
> > ? __schedule+0x1fe/0x7e0
> > schedule+0x28/0x80
> > suspend_devices_and_enter+0x4ac/0x750
> > pm_suspend+0x2c0/0x310
> >
> > Register a PM notifier to disable the detector on suspend and re-enable
> > back on wakeup.
> >
> > Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>
> Thanks for your patience with this!
>
> Are there any objections or concerns regarding this patch?
Seeing none, so applied.
Thanks,
Rafael
prev parent reply other threads:[~2018-10-26 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 11:23 Vitaly Kuznetsov
2018-10-18 7:32 ` Rafael J. Wysocki
2018-10-26 9:23 ` Rafael J. Wysocki [this message]
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=1827523.RqSiaKuRRv@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=vkuznets@redhat.com \
/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
all inboxes | Powered by JetHome®