From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: Pavel Machek <pavel@ucw.cz>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>, Andrew Morton <akpm@osdl.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Jens Axboe <axboe@suse.de>
Subject: Re: Strange IO behaviour on wakeup from sleep
Date: Wed, 27 Oct 2004 22:06:29 +1000 [thread overview]
Message-ID: <1098878790.9478.11.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.53.0410271308360.9839@gockel.physik3.uni-rostock.de>
On Wed, 2004-10-27 at 13:20 +0200, Tim Schmielau wrote:
> On Wed, 27 Oct 2004, Benjamin Herrenschmidt wrote:
>
> > Not much datas at this point yet, but paulus and I noticed that current
> > bk (happened already last saturday or so) has a very strange problem
> > when waking up from sleep (suspend to ram) on our laptops.
>
> It's a shot in the dark, but I am concerned whether timers continue to
> work correctly after suspend with the following patch from Linus' bk tree.
> I think jiffies may not be set behind the back of the timer subsystem, but
> maybe it works if we can guarantee there are no timers scheduled.
>
> It might be worth backing out and retesting.
The problem has been observed on ppc, while this patch only affects
i386...
Ben.
next prev parent reply other threads:[~2004-10-27 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 2:56 Strange IO behaviour on wakeup from sleep Benjamin Herrenschmidt
2004-10-27 6:24 ` Jens Axboe
2004-10-27 11:20 ` Tim Schmielau
2004-10-27 12:06 ` Benjamin Herrenschmidt [this message]
2004-10-27 12:13 ` Tim Schmielau
2004-10-27 13:01 ` Nigel Cunningham
2004-10-27 13:08 ` Benjamin Herrenschmidt
2004-10-27 13:20 ` Nigel Cunningham
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 14:18 Zachary Amsden
2004-10-27 22:40 ` Benjamin Herrenschmidt
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=1098878790.9478.11.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=pavel@ucw.cz \
--cc=tim@physik3.uni-rostock.de \
/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