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 18:10:22 +0100 [thread overview]
Message-ID: <20080201171022.GC2159@elte.hu> (raw)
In-Reply-To: <b647ffbd0802010711q744f5023mdbfccd9540556b70@mail.gmail.com>
* Dmitry Adamushko <dmitry.adamushko@gmail.com> wrote:
> On 01/02/2008, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>
> > ---
> > - restore the old wakeup mechanism
>
> and how does it change behavior, logically-wise?
>
> do we somehow miss a 'wake-up' from kthread_stop() so that its caller
> gets blocked until watchdog's msleep_interruptible(10000) timeouts? On
> average, it would take +-5 sec. and might explain the first
> observation of Ravael -- "...adds a 5 - 10 sec delay..." (although,
> lately he reported up to +30 sec. delays).
>
> (/me goint to also try reproducing it later today)
thanks - i cannot reproduce it on my usual suspend/resume testbox
because e1000 broke on it, and this is a pretty annoying regression.
We'll have to undo the hung-tasks detection feature if it's not fixed
quickly. (there's no point in debugging features that _add_ bugs)
Ingo
next prev parent reply other threads:[~2008-02-01 17:11 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 [this message]
2008-02-01 21:54 ` Dmitry Adamushko
2008-02-01 22:44 ` Dmitry Adamushko
2008-02-01 22:48 ` Ingo Molnar
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=20080201171022.GC2159@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