From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Subject: Re: Fedora vs. swsusp (was Re: megaraid_sas suspend ok, resume oops)
Date: Thu, 31 Aug 2006 19:05:30 +0200
User-Agent: KMail/1.9.3
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>
References: <b6a2187b0608281004g30706834r96d5d24f85e82cc9@mail.gmail.com> <b6a2187b0608290522vea22930y54ac39bfce3127f2@mail.gmail.com> <20060829203951.GA5065@ucw.cz>
In-Reply-To: <20060829203951.GA5065@ucw.cz>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200608311905.30462.rjw@sisk.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1021
Lines: 36

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/