[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080304215852.GA14318@hjernemadsen.org>
Date: Tue, 4 Mar 2008 22:58:52 +0100
From: "Klaus S. Madsen" <ksm@...rnemadsen.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Pavel Machek <pavel@....cz>,
Suspend-devel list <suspend-devel@...ts.sourceforge.net>,
"H. Peter Anvin" <hpa@...or.com>,
LKML <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Thomas Gleixner <tglx@...utronix.de>,
Matthew Garrett <mjg59@...f.ucam.org>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Arjan van de Ven <arjan@...radead.org>
Subject: Re: Regression in 2.6.25-rc3: s2ram segfaults before suspending
On Tue, Mar 04, 2008 at 13:36:02 +0100, Ingo Molnar wrote:
> my guess would be that it's this commit that causes it:
>
> | commit 6c3866558213ff706d8331053386915371ad63ec
> | Author: Jeremy Fitzhardinge <jeremy@...p.org>
> | Date: Wed Jan 30 13:32:55 2008 +0100
> |
> | x86: move all asm/pgtable constants into one place
All right. I just tried the following:
git checkout 82bc03fc158e28c90d7ed9919410776039cb4e14
make clean && make -j3 && sudo make install modules_install
And the resulting kernel works OK. However if I checkout commit
6c3866558213ff706d8331053386915371ad63ec, and compile it using the
previous commandline, s2ram fails so it seems you're right.
> > But I'm a bit puzzled by the fact that I'm aparently the only one how
> > have encountered the problem? Maybe it's only a problem if one also
> > uses PAE? (Thats just a wild guess to explain why I'm the only one
> > seeing this).
>
> PAE activates NX on 32-bit. So we probably had an NX regression that got
> fixed by the side-effects of one of the unifications. Does it start
> working if you disable NX via the noexec=off boot option?
If I boot with noexec=off, s2ram starts working again.
--
Kind regards
Klaus S. Madsen
--
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