[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201102061404.24146.rjw@sisk.pl>
Date: Sun, 6 Feb 2011 14:04:23 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Marc Koschewski <marc@...nowledge.org>
Cc: Dave Airlie <airlied@...il.com>, Takashi Iwai <tiwai@...e.de>,
Jeff Chua <jeff.chua.linux@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Chris Wilson <chris@...is-wilson.co.uk>,
Len Brown <lenb@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Commit 500f7147cf5bafd139056d521536b10c2bc2e154 breaks _resume_
On Sunday, February 06, 2011, Marc Koschewski wrote:
> I've the NX stuff disabled, so to say DEBUG_RODATA=n and it doesn't resume... so
> what's next?
Did you actually try to revert the NX commits or go back to the version of the
kernel where they aren't present?
Also, what's the last known working kernel?
> I use an i7 with 32bit code as I think 64bit is a) useless for me
You're most probably wrong, because memory management is mush simpler in the
64-bit mode. Basically, if your machine supports 64-bitness, you should use
it.
> and b) I just plugged my old HDD into my new machine.
Well, that's a good reason to stay backwards-compatible.
Thanks,
Rafael
> > >> I reverted the specified commit and my box still suffers the
> > >> resume-turns-into-cold-boot behavior. Retried two times with the commit reverted
> > >> on top of HEAD...
> > >
> > > The cold-boot problem is very likely irrelevant with i915 patches.
> > > I've got the same issue with and without the i915 fix patches on test
> > > machines here.
> > >
> > Yeah its the 32-bit NX stuff most likely if you are using 32-bit kernels.
--
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