From: Ingo Molnar <mingo@elte.hu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Chris Friedhoff <chris@friedhoff.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.24-rc2 STD with s2disk fails to activate suspended system after loading - now 2.6.24-rc3
Date: Tue, 20 Nov 2007 06:55:19 +0100 [thread overview]
Message-ID: <20071120055519.GD20436@elte.hu> (raw)
In-Reply-To: <200711200058.29663.rjw@sisk.pl>
* Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > increasing CONFIG_BLK_DEV_RAM_SIZE from 7777 to 131072 hasn't
> > changed the non-functioning of 2.6.24-rc3
> >
> > s2disk works with 2.6.23.8 ; I tested 4 cycles in a row, 2 from
> > console and 2 from within X
>
> I've attached a patch to the bugzilla entry, please test it.
[...]
> --- linux-2.6.orig/init/do_mounts_initrd.c
> +++ linux-2.6/init/do_mounts_initrd.c
> @@ -55,6 +55,8 @@ static void __init handle_initrd(void)
> sys_mount(".", "/", NULL, MS_MOVE, NULL);
> sys_chroot(".");
>
> + current->flags |= PF_NOFREEZE;
> +
> pid = kernel_thread(do_linuxrc, "/linuxrc", SIGCHLD);
> if (pid > 0)
> while (pid != sys_wait4(-1, NULL, 0, NULL)) {
this is not the first time (and not the last time) that a missing
PF_NOFREEZE is causing hard to debug suspend problems. I think we should
be more robust about this and at minimum include some debug mechanism
that determines when a PF_NOFREEZE annotation is missing. (or at least
detect the condition somehow and report it) This bug took 10 days to
track down.
Ingo
next prev parent reply other threads:[~2007-11-20 5:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 21:16 2.6.24-rc2 STD with s2disk fails to activate suspended system after loading Chris Friedhoff
2007-11-11 18:45 ` Rafael J. Wysocki
2007-11-11 22:09 ` Chris Friedhoff
2007-11-19 13:42 ` 2.6.24-rc2 STD with s2disk fails to activate suspended system after loading - now 2.6.24-rc3 Chris Friedhoff
2007-11-19 18:58 ` Rafael J. Wysocki
2007-11-19 19:22 ` Rafael J. Wysocki
2007-11-19 22:43 ` Chris Friedhoff
2007-11-19 23:58 ` Rafael J. Wysocki
2007-11-20 5:55 ` Ingo Molnar [this message]
2007-11-21 0:46 ` Rafael J. Wysocki
2007-11-20 10:39 ` Chris Friedhoff
2007-11-20 21:54 ` Chris Friedhoff
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=20071120055519.GD20436@elte.hu \
--to=mingo@elte.hu \
--cc=chris@friedhoff.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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