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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200609022147.05503.rjw@sisk.pl>
Date:	Sat, 2 Sep 2006 21:47:05 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Dave Jones <davej@...hat.com>
Cc:	Nigel Cunningham <ncunningham@...uxmail.org>,
	Jeff Chua <jeff.chua.linux@...il.com>,
	Jens Axboe <axboe@...nel.dk>, Sreenivas.Bagalkote@...l.com,
	Sumant.Patro@...l.com, jeff@...zik.org,
	lkml <linux-kernel@...r.kernel.org>, Pavel Machek <pavel@....cz>
Subject: Re: megaraid_sas suspend ok, resume oops

On Saturday 02 September 2006 15:30, Dave Jones wrote:
> On Wed, Aug 30, 2006 at 10:54:56AM +0200, Rafael J. Wysocki wrote:
> 
>  > > > But without 64 bit support, my notebook will suspend/resume many times
>  > > > without failing (with the 5 ahci patches from Pavel Machek)....
>  > > 
>  > > Neither swsusp (as far as I know) or suspend2 support CONFIG_HIGHMEM64G
>  > > at the moment, I'm afraid.
>  > > 
>  > > It's not impossible, we just haven't seen it as a priority worth putting
>  > > time into.
>  > 
>  > It looks like the Fedora default config has HIGHMEM64G set, so I'll be looking
>  > at it shortly.
> 
> There is no 'Fedora default config'. We ship a number of different kernels,
> some of which enable PAE, some disable it.
> 
> For FC5, the installer installs a PAE kernel if you have >4GB, or SMP.

Ah, that's why people get hit by it if they have less than 4GB. ;-)

> For FC6, it'll only install one if you have >4GB.
> (or possibly if you have an NX capable CPU, I forget if we enabled that
>  magick in the installer)
> 
> Precluding NX support + swsusp kinda sucks, but I guess it's a tiny subset of users.

Well, I think the majority of NX-capable CPUs are also x86_64, in which case
I'd recommend using a 64-bit kernel anyway.

Thanks for the clarification.

I was afraid the issue would be urgent, but it doesn't seem so now.  I'd like to
postpone fixing it until we can create suspend images larger that 350 meg on
i386 boxes with highmem (the patch is ready to go to -mm after 2.6.19-rc1 as
2.6.20 material).

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

-- 
VGER BF report: H 0.00668657
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ