Re: Regression in 2.6.25-rc3: s2ram segfaults before suspending

Klaus S. Madsen
2008-03-04T21:59:07Z

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@goop.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