From: Ingo Molnar <mingo@elte.hu>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
Tejun Heo <tj@kernel.org>, Arjan van de Ven <arjan@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
xen-devel@lists.xensource.com,
Jeremy Fitzhardinge <jeremy@xensource.com>,
linux-kernel@vger.kernel.org, Mike Travis <travis@sgi.com>,
Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org, Yinghai Lu <yhlu.kernel@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: 2.6.29 git, resume from ram broken on thinkpad
Date: Fri, 3 Apr 2009 19:32:56 +0200 [thread overview]
Message-ID: <20090403173256.GA6295@elte.hu> (raw)
In-Reply-To: <200904030847.19674.a.miskiewicz@gmail.com>
* Arkadiusz Miskiewicz <a.miskiewicz@gmail.com> wrote:
> On Friday 03 of April 2009, Chris Wright wrote:
> > * Arkadiusz Miskiewicz (a.miskiewicz@gmail.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
aha!!
> Disabling stackprotector makes problem go away (and my build of
> final 2.6.29 had it disabled while later builds got it enabled at
> some moment).
Thanks a ton for that info. Could you try:
http://people.redhat.com/mingo/tip.git/README
with stack-protector re-enabled please? This fix:
1f23b77: x86: disable stack-protector for __restore_processor_state()
might do the trick!
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
Tejun Heo <tj@kernel.org>, Arjan van de Ven <arjan@infradead.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, Mike Travis <travis@sgi.com>,
Jeremy Fitzhardinge <jeremy@xensource.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
virtualization@lists.osdl.org, xen-devel@lists.xensource.com,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: 2.6.29 git, resume from ram broken on thinkpad
Date: Fri, 3 Apr 2009 19:32:56 +0200 [thread overview]
Message-ID: <20090403173256.GA6295@elte.hu> (raw)
In-Reply-To: <200904030847.19674.a.miskiewicz@gmail.com>
* Arkadiusz Miskiewicz <a.miskiewicz@gmail.com> wrote:
> On Friday 03 of April 2009, Chris Wright wrote:
> > * Arkadiusz Miskiewicz (a.miskiewicz@gmail.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
aha!!
> Disabling stackprotector makes problem go away (and my build of
> final 2.6.29 had it disabled while later builds got it enabled at
> some moment).
Thanks a ton for that info. Could you try:
http://people.redhat.com/mingo/tip.git/README
with stack-protector re-enabled please? This fix:
1f23b77: x86: disable stack-protector for __restore_processor_state()
might do the trick!
Ingo
next prev parent reply other threads:[~2009-04-03 17:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 9:55 2.6.29 git, resume from ram broken on thinkpad Arkadiusz Miskiewicz
2009-04-01 21:00 ` Chris Wright
2009-04-01 21:00 ` Chris Wright
2009-04-02 20:12 ` Arkadiusz Miskiewicz
2009-04-01 21:29 ` Rafael J. Wysocki
2009-04-01 21:37 ` Chris Wright
2009-04-01 21:37 ` Chris Wright
2009-04-01 21:49 ` Rafael J. Wysocki
2009-04-01 22:14 ` Chris Wright
2009-04-01 22:23 ` Rafael J. Wysocki
2009-04-01 23:06 ` Chris Wright
2009-04-01 23:06 ` Chris Wright
2009-04-02 21:00 ` Rafael J. Wysocki
2009-04-02 21:04 ` Ingo Molnar
2009-04-02 21:04 ` Ingo Molnar
2009-04-02 21:28 ` Rafael J. Wysocki
2009-04-03 0:22 ` Arkadiusz Miskiewicz
2009-04-03 0:35 ` Chris Wright
2009-04-03 0:35 ` Chris Wright
2009-04-03 6:47 ` Arkadiusz Miskiewicz
2009-04-03 17:32 ` Ingo Molnar [this message]
2009-04-03 17:32 ` Ingo Molnar
2009-04-03 17:36 ` Chris Wright
2009-04-03 17:39 ` Ingo Molnar
2009-04-03 17:39 ` Ingo Molnar
2009-04-03 17:39 ` Ingo Molnar
2009-04-03 17:45 ` Chris Wright
2009-04-07 8:54 ` Arkadiusz Miskiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090403173256.GA6295@elte.hu \
--to=mingo@elte.hu \
--cc=a.miskiewicz@gmail.com \
--cc=arjan@infradead.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@xensource.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tj@kernel.org \
--cc=travis@sgi.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.