From: Tony Lindgren <tony@atomide.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: pavel@suse.cz, Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: swsusp on x86-64 w/ nforce3
Date: Wed, 8 Sep 2004 13:42:49 -0700 [thread overview]
Message-ID: <20040908204249.GG8142@atomide.com> (raw)
In-Reply-To: <200409062123.08476.rjw@sisk.pl>
* Rafael J. Wysocki <rjw@sisk.pl> [040906 12:31]:
> On Monday 06 of September 2004 18:36, Rafael J. Wysocki wrote:
> > Pavel,
> >
> > Can you tell me, please, if swsusp, as in the 2.6.9-rc1-bk12 kernel, is
> > supposed to work on x86-64-based systems (specifically, with the nforce3
> > chipset)?
>
> Anyway, on such a system (.config and the output of dmesg are attached), I get
> the following:
>
> Stopping tasks:
> ==============================================================|
> Freeing
> memory: ............................................................................................................|
> Suspending devices... /critical section: counting pages to copy..[nosave pfn
> 0x59b]..................................................)
> Alloc pagedir
> ..[nosave pfn
> 0x59b]................................................................................critical
> section/: done (40890 pa)
> APIC error on CPU0: 80(08)
>
Just FYI, swsusp works nicely here on my m6805 laptop :)
Tony
next prev parent reply other threads:[~2004-09-08 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 16:36 swsusp on x86-64 w/ nforce3 Rafael J. Wysocki
2004-09-06 19:23 ` Rafael J. Wysocki
2004-09-06 20:32 ` Pavel Machek
2004-09-06 23:10 ` Rafael J. Wysocki
2004-09-08 20:42 ` Tony Lindgren [this message]
2004-09-08 20:52 ` Rafael J. Wysocki
2004-09-09 1:18 ` Tony Lindgren
2004-09-09 7:06 ` Rafael J. Wysocki
2004-09-09 10:19 ` Rafael J. Wysocki
2004-09-09 22:28 ` Tony Lindgren
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=20040908204249.GG8142@atomide.com \
--to=tony@atomide.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.