From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Michael Schmitz <schmitz@opal•biophys.uni-duesseldorf.de>
Cc: Michael Schmitz <schmitz@zirkon•biophys.uni-duesseldorf.de>,
Pavel Machek <pavel@ucw•cz>, Hugang <hugang@soulinfo•com>,
Patrick Mochel <mochel@digitalimplant•org>,
Nigel Cunningham <ncunningham@users•sourceforge.net>,
ncunningham@clear•net.nz,
linuxppc-dev list <linuxppc-dev@lists•linuxppc.org>
Subject: Re: pmdisk working on ppc (WAS: Help port swsusp to ppc)
Date: Thu, 29 Jan 2004 23:10:09 +1100 [thread overview]
Message-ID: <1075378209.1241.34.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0401291029360.2221-100000@opal.biophys.uni-duesseldorf.de>
On Thu, 2004-01-29 at 20:30, Michael Schmitz wrote:
> > > OK. I put a mdelay(100) between the PMU_SYSTEM_READY request and the
> > > pmu_suspend() call in pmu_sys_resume and it seems to work so far. Side
> > > note: if you are saving a large system and have multiple swap files, play
> > > with swap priorities to make sure the pages are swapped out to the file
> > > _not_ used for suspend.
> >
> > Hrm... Remove the PMU_SYSTEM_READY, it's a bug to call it on a 101...
> > And it's not needed anyway.
>
> I'm trying a if (pmu_kind != 3) around that call - should it rather be <= 3 ?
Just remove it for you tests. Only KEYLARGO based PMUs have this call
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-29 12:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1075154452.6191.91.camel@gaston>
2004-01-27 10:34 ` pmdisk working on ppc (WAS: Help port swsusp to ppc) Michael Schmitz
2004-01-27 10:37 ` Benjamin Herrenschmidt
2004-01-27 14:32 ` Michael Schmitz
2004-01-27 21:40 ` Benjamin Herrenschmidt
2004-01-28 16:09 ` Michael Schmitz
2004-01-28 17:02 ` Hugang
2004-01-28 17:03 ` Colin Leroy
2004-01-29 9:17 ` Michael Schmitz
2004-01-28 18:00 ` Michael Schmitz
2004-01-28 21:56 ` Benjamin Herrenschmidt
2004-01-28 21:55 ` Benjamin Herrenschmidt
2004-01-29 9:30 ` Michael Schmitz
2004-01-29 12:10 ` Benjamin Herrenschmidt [this message]
2004-01-28 21:55 ` Benjamin Herrenschmidt
2004-01-28 23:35 ` Pavel Machek
2004-01-29 8:11 ` Michael Schmitz
2004-01-27 10:47 ` Pavel Machek
2004-01-27 10:56 ` Benjamin Herrenschmidt
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=1075378209.1241.34.camel@gaston \
--to=benh@kernel$(echo .)crashing.org \
--cc=hugang@soulinfo$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=mochel@digitalimplant$(echo .)org \
--cc=ncunningham@clear$(echo .)net.nz \
--cc=ncunningham@users$(echo .)sourceforge.net \
--cc=pavel@ucw$(echo .)cz \
--cc=schmitz@opal$(echo .)biophys.uni-duesseldorf.de \
--cc=schmitz@zirkon$(echo .)biophys.uni-duesseldorf.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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