mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Craig Kulesa <ckulesa@as.arizona.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix compile warnings in suspend.c, 2.5.28
Date: Fri, 26 Jul 2002 11:57:22 +0200	[thread overview]
Message-ID: <20020726095721.GA220@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0207251501320.18430-100000@loke.as.arizona.edu>

Hi!

> > Does it work for you? I get reboot after S4 on 2.5.28. Can you mail me
> > diff between clean and your tree?
> 
> Isn't the 'reboot after S4' due to #define TEST_SWSUSP 1?   I set it 
> to 0 and it shuts down properly for me.  I'm not sure why rebooting should 
> be the default behavior, actually -- it seems a bit strange.

Actually, I get two reboots. One expected after suspend and one
unexpected after resume.

TEST_SWSUSP is one so I can test it properly. I want to be Linus's
swsusp same as mine for 2.5. TEST_SWSUSP is going to be 0 at 2.6.

> My laptop's at home, but I applied the following patches from:
> 	http://loke.as.arizona.edu/~ckulesa/kernel/rmap-vm/2.5.28/
> 
> I applied the 2 rmap-related patches in order, then the remaining patches 
> (which are trivial cleanups and compile-fixes) in no special order.  
> 2.5.28-swsusp is the patch in this thread.  This won't change the "reboot 
> after S4" behavior without the additional change to TEST_SWSUSP,
> above. 

Can you do multiple S4 enters/leaves? Good test is to make bzImage
while doing while true; do echo 4 > /proc/acpi/sleep; sleep 30; done.

> Side note:
> The only change to suspend.c that I made which isn't covered by 
> the patch in this thread, is the try_to_free_pages() line -- 
> but this is specific to the "full rmap-VM for 2.5".  The big rmap patch 
> (2.5.28-rmap-1-rmap13b) makes this single alteration.

Okay.

> Second side note:
> For the vanilla 2.5 classzone VM, I don't honestly understand why we're 
> only looking at &contig_page_data.node_zones[ZONE_HIGHMEM] in
> try_to_free_pages().  On the other hand, I don't see how it would break
> swsusp.

I don't understand that line, either. Andrea told me to write it like
that, IIRC ;-).

> And a note of appreciation: :)
> This was the very first time I tried ACPI and swsusp! I had been using 
> APM before, but had no hibernation capability (my BIOS only worked 
> properly with suspend to RAM in Linux).  This is really a nice feature!
> 
> But now I have to figure out how to teach acpid to do useful stuff, like 
> throttle the CPU and try to S4 on lid close and such. :)

Throttling the CPU should be pretty easy [see
/proc/acpi/processor/0/*], and it should already enter sleep modes for
you.

								Pavel
-- 
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?

  reply	other threads:[~2002-07-26  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25 12:40 [PATCH] Fix complile " Craig Kulesa
2002-07-25 21:53 ` Pavel Machek
2002-07-25 22:49   ` [PATCH] Fix compile " Craig Kulesa
2002-07-26  9:57     ` Pavel Machek [this message]
2002-07-26 10:31       ` Craig Kulesa

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=20020726095721.GA220@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=ckulesa@as.arizona.edu \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®