From: Ingo Molnar <mingo@elte.hu>
To: Dmitry Adamushko <dmitry.adamushko@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Steven Rostedt <srostedt@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Regression] 2.6.24-git3: Major annoyance during suspend/hibernation on x86-64 (bisected)
Date: Fri, 1 Feb 2008 23:48:52 +0100 [thread overview]
Message-ID: <20080201224852.GA16700@elte.hu> (raw)
In-Reply-To: <b647ffbd0802011444n366c1537m7fb44acf0b848941@mail.gmail.com>
* Dmitry Adamushko <dmitry.adamushko@gmail.com> wrote:
> > I've observed delays from ~3 s. up to ~8 s. (out of ~20 tests) so
> > the 10s. delay of msleep_interruptible() might be related but I'm
> > still looking for the reason why this fix helps (and what goes wrong
> > with the current code).
>
> heh... it's pretty obvious indeed. What's msleep_interruptible() is
> all about? :-)
>
> "sleep waiting for signals"
>
> so the 'watchdog' thread gets woken up
>
> [ as a result of cpu_callback(action = CPU_DEAD) --> kthread_stop() ]
>
> just to be immediately scheduled out again for as long as the
> remaining timeout > 0.
>
> So it should work if we substitute msleep_interruptible() with
> schedule_timeout_interruptible().
Doh. Could someone with ths problem please test the patch below, does it
do the trick?
Ingo
---
kernel/softlockup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/kernel/softlockup.c
===================================================================
--- linux.orig/kernel/softlockup.c
+++ linux/kernel/softlockup.c
@@ -228,7 +228,7 @@ static int watchdog(void *__bind_cpu)
*/
while (!kthread_should_stop()) {
touch_softlockup_watchdog();
- msleep_interruptible(10000);
+ schedule_timeout_interruptible(10*HZ);
if (this_cpu != check_cpu)
continue;
next prev parent reply other threads:[~2008-02-01 22:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 21:29 [Regression] 2.6.24-git3: Major annoyance during suspend/hibernation on x86-64 (bisected) Rafael J. Wysocki
2008-01-27 21:59 ` Ingo Molnar
2008-01-28 1:26 ` Rafael J. Wysocki
2008-01-28 1:40 ` Steven Rostedt
2008-01-28 11:31 ` Rafael J. Wysocki
2008-01-28 16:31 ` Rafael J. Wysocki
2008-01-28 16:46 ` Steven Rostedt
2008-01-29 0:08 ` Rafael J. Wysocki
2008-01-28 8:56 ` Dmitry Adamushko
2008-01-28 11:32 ` Rafael J. Wysocki
2008-01-28 16:08 ` Rafael J. Wysocki
2008-01-31 15:58 ` Peter Zijlstra
2008-01-31 20:54 ` Rafael J. Wysocki
2008-02-01 12:04 ` Peter Zijlstra
2008-02-01 12:47 ` Ingo Molnar
2008-02-01 14:42 ` Rafael J. Wysocki
2008-02-01 23:19 ` Rafael J. Wysocki
2008-02-01 23:24 ` Ingo Molnar
2008-02-01 15:11 ` Dmitry Adamushko
2008-02-01 17:10 ` Ingo Molnar
2008-02-01 21:54 ` Dmitry Adamushko
2008-02-01 22:44 ` Dmitry Adamushko
2008-02-01 22:48 ` Ingo Molnar [this message]
2008-02-01 23:22 ` Dmitry Adamushko
2008-02-01 23:25 ` Ingo Molnar
2008-02-02 0:03 ` Dmitry Adamushko
2008-02-01 23:26 ` Rafael J. Wysocki
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=20080201224852.GA16700@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=srostedt@redhat.com \
--cc=torvalds@linux-foundation.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