[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090403174540.GB27148@sequoia.sous-sol.org>
Date: Fri, 3 Apr 2009 10:45:40 -0700
From: Chris Wright <chrisw@...s-sol.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Chris Wright <chrisw@...s-sol.org>,
Arkadiusz Miskiewicz <a.miskiewicz@...il.com>,
"Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org,
Mike Travis <travis@....com>,
Jeremy Fitzhardinge <jeremy@...source.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
virtualization@...ts.osdl.org, xen-devel@...ts.xensource.com,
Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: 2.6.29 git, resume from ram broken on thinkpad
* Ingo Molnar (mingo@...e.hu) wrote:
>
> * Chris Wright <chrisw@...s-sol.org> wrote:
>
> > * Arkadiusz Miskiewicz (a.miskiewicz@...il.com) wrote:
> > > On Friday 03 of April 2009, Chris Wright wrote:
> > > > * Arkadiusz Miskiewicz (a.miskiewicz@...il.com) wrote:
> > > > > What about 9ea09af3bd3090e8349ca2899ca2011bd94cda85 ?
> > > > >
> > > > > stop_machine: introduce stop_machine_create/destroy.
> > > >
> > > > That is later fixed in a0e280e0f33f6c859a235fb69a875ed8f3420388.
> > > >
> > > > Can you please verify if 2.6.29 works for you?
> > >
> > > I think that the guilty part is
> > > CONFIG_CC_STACKPROTECTOR_ALL=y
> > > CONFIG_CC_STACKPROTECTOR=y
> >
> > Indeed, I think you're right. In fact...this should fix it:
>
> Note that i had to do a manual merge of the patch (it had 3 separate
> patch corruptions) - the non-damaged version i applied is the one
> below.
Indeed, I just discovered that ;-)
And, for the record...yes, that fixes it on my laptop.
Tested-by: Chris Wright <chrisw@...s-sol.org>
--
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