From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-pm@lists.osdl.org, Jiri Slaby <jirislaby@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.21-rc4-mm1
Date: Tue, 20 Mar 2007 21:58:48 +0100 [thread overview]
Message-ID: <200703202158.50063.rjw@sisk.pl> (raw)
In-Reply-To: <20070320202141.GA3604@elf.ucw.cz>
On Tuesday, 20 March 2007 21:21, Pavel Machek wrote:
> Hi!
>
> > >>>> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing
> > >>>> which will simply do a freeze/unfreeze cycle. Then we can apply various
> > >>>> workloads to the machine while madly stressing the freezer code.
> > >>> echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is
> > >>> pretty much what you want.
> > >> Ok, I'll try this.
> > >
> > > It will not help you -- probably -- it is equivalent to just running
> > > s2ram. But it should make "successful" testing easier, because you no
> > > longer need machine with working suspend to test refrigerator.
> >
> > Aha, I didn't read it carefully. Suspend is working, but not in this kernel.
> > I haven't tried s2ram in this version. Should I (I'm away from it) -- would
> > it show something?
>
> No, probably not. git bisect would help, but I guess it is easier to
> let Rafael sort it out.
Actually, the problem is 100% reproducible on my system too and I doubt it's
caused by the recent freezer patches.
Investigating.
Rafael
next prev parent reply other threads:[~2007-03-20 20:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070319205623.299d0378.akpm@linux-foundation.org>
2007-03-20 14:31 ` 2.6.21-rc4-mm1 Jiri Slaby
2007-03-20 16:09 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-20 18:38 ` 2.6.21-rc4-mm1 Pavel Machek
2007-03-20 19:40 ` 2.6.21-rc4-mm1 Jiri Slaby
2007-03-20 19:56 ` 2.6.21-rc4-mm1 Pavel Machek
2007-03-20 20:13 ` 2.6.21-rc4-mm1 Jiri Slaby
2007-03-20 20:21 ` 2.6.21-rc4-mm1 Pavel Machek
2007-03-20 20:58 ` Rafael J. Wysocki [this message]
2007-03-20 20:58 ` 2.6.21-rc4-mm1 Jiri Slaby
2007-03-20 21:06 ` 2.6.21-rc4-mm1 Rafael J. Wysocki
2007-03-21 0:49 ` 2.6.21-rc4-mm1: freezing of processes broken Rafael J. Wysocki
2007-03-21 1:23 ` Eric W. Biederman
2007-03-21 2:47 ` sukadev
2007-03-21 3:13 ` Nigel Cunningham
2007-03-21 14:23 ` Oleg Nesterov
2007-03-21 14:45 ` Rafael J. Wysocki
2007-03-21 16:20 ` Andrew Morton
2007-03-21 16:55 ` Oleg Nesterov
2007-03-21 17:08 ` Andrew Morton
2007-03-21 18:07 ` [linux-pm] " sukadev
2007-03-21 18:16 ` Eric W. Biederman
2007-03-21 18:23 ` sukadev
2007-03-21 17:15 ` Oleg Nesterov
2007-03-21 12:08 ` Rafael J. Wysocki
2007-03-20 20:12 ` 2.6.21-rc4-mm1 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=200703202158.50063.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
/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