Re: Fedora vs. swsusp (was Re: megaraid_sas suspend ok, resume oops)

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • megaraid_sas suspend ok, resume oops
    • From: "Jeff Chua" <[email protected]>
  • Re: megaraid_sas suspend ok, resume oops
    • From: "Jeff Chua" <[email protected]>
  • Fedora vs. swsusp (was Re: megaraid_sas suspend ok, resume oops)
    • From: Pavel Machek <[email protected]>

• Prev by Date: Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes
• Next by Date: RE: one more ACPI Error (utglobal-0125): Unknown exception code:0xFFFFFFEA [Re: 2.6.18-rc4-mm3]
• Previous by thread: Fedora vs. swsusp (was Re: megaraid_sas suspend ok, resume oops)
• Next by thread: RBP save and restore on x86-64 system calls
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]