From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Jeff Chua <jeff.chua.linux@gmail.com>,
Jens Axboe <axboe@kernel.dk>,
Sreenivas.Bagalkote@lsil.com, Sumant.Patro@lsil.com,
jeff@garzik.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Fedora vs. swsusp (was Re: megaraid_sas suspend ok, resume oops)
Date: Thu, 31 Aug 2006 19:05:30 +0200 [thread overview]
Message-ID: <200608311905.30462.rjw@sisk.pl> (raw)
In-Reply-To: <20060829203951.GA5065@ucw.cz>
On Tuesday 29 August 2006 22:39, Pavel Machek wrote:
> Hi!
>
> > Another point ... on IBM x60s notebook, setting ...
> >
> > High Memory Support (64GB)
> > CONFIG_HIGHMEM64G=y
> > CONFIG_RESOURCES_64BIT=y
> > CONFIG_X86_PAE=y
>
> >
> > will cause resume to "REBOOT" sometimes (may be 6 out of
> > 10).
>
> Okay, I guess that explains 'swsusp br0ken on Fedora' reports I was
> seening.
>
> I wonder if swsusp *ever* worked reliably with highmem64...
>
> ...wait a moment, higmem64 implies PAE implies we can no longer use
> swsusp's trick with copying initial pgdir, and we'll need to use
> x86-64-like code, no?
I think so.
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
next prev parent reply other threads:[~2006-08-31 17:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 17:04 megaraid_sas suspend ok, resume oops Jeff Chua
2006-08-28 21:55 ` Pavel Machek
2006-08-29 8:15 ` Jens Axboe
2006-08-29 12:22 ` Jeff Chua
2006-08-29 20:39 ` Fedora vs. swsusp (was Re: megaraid_sas suspend ok, resume oops) Pavel Machek
2006-08-31 17:05 ` Rafael J. Wysocki [this message]
2006-08-29 23:45 ` megaraid_sas suspend ok, resume oops Nigel Cunningham
2006-08-30 1:45 ` Jeff Chua
2006-08-30 2:30 ` Nigel Cunningham
2006-08-30 8:41 ` Jeff Chua
2006-08-30 8:54 ` Rafael J. Wysocki
2006-09-02 13:30 ` Dave Jones
2006-09-02 19:47 ` Rafael J. Wysocki
2006-09-02 20:10 ` Dave Jones
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=200608311905.30462.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Sreenivas.Bagalkote@lsil.com \
--cc=Sumant.Patro@lsil.com \
--cc=axboe@kernel.dk \
--cc=jeff.chua.linux@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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®