linux-kernel - Fedora vs. swsusp (was Re: megaraid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060829203951.GA5065@ucw.cz>
Date:	Tue, 29 Aug 2006 20:39:52 +0000
From:	Pavel Machek <pavel@....cz>
To:	Jeff Chua <jeff.chua.linux@...il.com>
Cc:	Jens Axboe <axboe@...nel.dk>, Sreenivas.Bagalkote@...l.com,
	Sumant.Patro@...l.com, jeff@...zik.org,
	lkml <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Fedora vs. swsusp (was Re: megaraid_sas suspend ok, resume oops)

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