public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Wolf <wwolf@vt.edu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: AMD64 Swsusp on 2.6.9-rc4-mm1
Date: Tue, 16 Nov 2004 01:19:14 -0600	[thread overview]
Message-ID: <1100589554.7496.2.camel@Xnix> (raw)
In-Reply-To: <200410162252.33347.rjw@sisk.pl>

Is this supposedly something new in rc4-mm1?  I have been having the
same problems since around 2.6.8.1, though i havent gone through every
single -mm patch, i have tried at least one in every -rcx candidate, and
they have all done this same thing.

On Sat, 2004-10-16 at 22:52 +0200, Rafael J. Wysocki wrote:
> On Saturday 16 of October 2004 22:47, William Wolf wrote:
> > Hey, Im running 2.6.9-rc4-mm1, and when i run either a echo 4 > 
> > /proc/acpi/sleep or echo disk > /sys/power/state  I get the following 
> > messages:
> > 
> > 
> > Stopping tasks: =================|
> > Freeing memory... done (0 pages freed)
> > PM: Attempting to suspend to disk.
> > PM: snapshotting memory.
> > ACPI: PCI interrupt 0000:00:02.7[C] -> GSI 18 (level, low) -> IRQ 18
> > Restarting tasks... done
> > 
> > 
> > 
> > It basically just stops everything, then starts it all back up again 
> > immediately.  Any idea whats going on here?  This was done right after 
> > booting and just logging in with no X running.
> 
> IIRC, on 2.6.9-rc4-mm1 swsusp cannot free memory because of some unfinished VM 
> patches that are in there, so it won't work (Andrew, please correct if I'm 
> wrong).
> 
> Greets,
> RJW
> 


  reply	other threads:[~2004-10-17  0:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-16 20:47 AMD64 Swsusp on 2.6.9-rc4-mm1 William Wolf
2004-10-16 20:52 ` Rafael J. Wysocki
2004-11-16  7:19   ` William Wolf [this message]
2004-10-17 10:24     ` Rafael J. Wysocki
2004-11-16 18:43       ` William Wolf

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=1100589554.7496.2.camel@Xnix \
    --to=wwolf@vt.edu \
    --cc=akpm@osdl.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