From: Andrew Morton <akpm@linux-foundation.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>,
Tomas Carnecky <tom@dbservice.com>,
linux-acpi@vger.kernel.org
Subject: Re: suspend to RAM failure on t61p
Date: Tue, 11 Dec 2007 01:57:51 -0800 [thread overview]
Message-ID: <20071211015751.3a786fb4.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071210225858.f9746533.akpm@linux-foundation.org>
On Mon, 10 Dec 2007 22:58:58 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> On Mon, 10 Dec 2007 22:21:56 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > However reverting 9cd9a0058dd35268b24fa16795a92c800f4086d4 does not fix the
> > machine-reboots-after-resume-from-disk regression.
> >
> > It gets to here:
> >
> > Attempting manual resume
> > swsusp: Marking nosave pages: 000000000009d000 - 0000000000100000
> > swsusp: Basic memory bitmaps created
> > Freezing user space processes ... (elapsed 0.00 seconds) done.
> > Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
> > Loading image data pages (52207 pages) ... done
> > Read 208828 kbytes in 5.40 seconds (38.67 MB/s)
> > Suspending console(s)
> >
> > then everything stops for five seconds then wham.
> >
> > This bug is present in 2.6.24-rc1 but I'm basically unable to bisect it
> > because every bisection point (tried about four so far) hits fatal runtime
> > errors: cant-find-/dev/root, an oops in ipv6, an oops in netfilter, etc.
> >
> > This is just a basic boot-it-on-fc8 test with RH's config and nothing
> > works. The quality of code which people have been checking into the tree
> > is just appalling and here we see the costs of that.
> >
> > I think I'll see if it's present in the last 2.6.23 -mm lineup: I know I
> > can bisect that. Probably it won't be, given the way in which people like
> > to jam vast amounts of new code into the merge window.
> >
>
> Under 2.6.23-mm1 on the t61p,
>
> echo disk >/sys/power/state
>
> makes the screen go black then nothing at all happens for ten seconds and
> then the display comes back and it says:
>
> t61p:/home/akpm# echo disk >/sys/power/state
> echo: write error: device or resource busy
>
> So I have to bisect that first.
>
This was caused by freezer-use-wait-queue-instead-of-busy-looping.patch
which we blessedly dropped.
After dropped that patch from 2.6.23-mm1, bisection shows that
hibernation-use-temporary-page-tables-for-kernel-text-mapping-on-x86_64.patch
is causing the t61p's reboot-after-resuming-from-disk regression.
Reverting that patch from current Linus mainline fixes this regression.
Now let me see what caused the keystrokes-no-longer-trigger-resume-from-RAM
regression.
next prev parent reply other threads:[~2007-12-11 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 9:19 suspend to RAM failure on t61p Andrew Morton
2007-12-09 12:40 ` Tomas Carnecky
2007-12-09 13:53 ` Rafael J. Wysocki
2007-12-10 0:40 ` Andrew Morton
2007-12-10 1:04 ` Rafael J. Wysocki
2007-12-10 7:25 ` Andrew Morton
2007-12-10 11:06 ` Rafael J. Wysocki
2007-12-11 6:21 ` Andrew Morton
2007-12-11 6:58 ` Andrew Morton
2007-12-11 9:57 ` Andrew Morton [this message]
2007-12-11 10:31 ` Andrew Morton
2007-12-11 21:50 ` Rafael J. Wysocki
2007-12-09 23:48 ` Volker Braun
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=20071211015751.3a786fb4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tom@dbservice.com \
/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