From: Alexander Graf <agraf@suse.de>
To: Anton Blanchard <anton@samba.org>
Cc: ulrich.weigand@de.ibm.com, paulus@samba.org,
Scott Wood <scottwood@freescale.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3] powerpc: Don't use local named register variable in current_thread_info
Date: Wed, 17 Dec 2014 10:27:33 +0100 [thread overview]
Message-ID: <54914C85.30107@suse.de> (raw)
In-Reply-To: <20141217144459.09701a76@kryten>
On 17.12.14 04:44, Anton Blanchard wrote:
> Hi Alex,
>
>> Git bisect managed to point me to this commit as the offender for
>> OOPSes on e5500 and e6500 (and maybe the G4 as well, not sure).
>>
>> Doing a git revert of this commit on top of linus/master makes things
>> work fine for me again.
>
> Ouch, sorry for that, I'll work to reproduce. What gcc version are you
> using?
I'm running
gcc (SUSE Linux) 4.7.2 20130108 [gcc-4_7-branch revision 195012]
which is basically the one from openSUSE 12.3 for ppc64.
I've also uploaded 2 builds, one with the patch applied (broken) and one
without (works):
http://csgraf.de/agraf/current_thread_info/vmlinux.broken.xz
http://csgraf.de/agraf/current_thread_info/vmlinux.works.xz
Interestingly enough I did not see this on IBM POWER systems, but maybe
that's because most of them compile their own kernels with local,
different compilers in my test runs and the only one that does base on
the same compiler doesn't run on nfsroot.
My iBook G4 target is affected by this as well and reverting this patch
also makes it work again. Maybe we're just running over some stack?
Alex
next prev parent reply other threads:[~2014-12-17 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1414727247-31838-1-git-send-email-anton__19440.5086375356$1414727300$gmane$org@samba.org>
2014-12-17 1:16 ` [PATCH 1/3] powerpc: Don't use local named register variable in current_thread_info Alexander Graf
2014-12-17 3:44 ` Anton Blanchard
2014-12-17 9:27 ` Alexander Graf [this message]
2014-12-22 6:49 ` Michael Ellerman
2014-12-18 5:11 ` Michael Ellerman
2014-12-18 6:25 ` Anton Blanchard
2014-12-18 15:02 ` Alexander Graf
2014-12-31 12:24 ` Alan Modra
2015-01-07 5:12 ` Anton Blanchard
2015-01-07 17:59 ` Scott Wood
2015-01-08 6:36 ` Alan Modra
2014-12-18 14:56 ` Alexander Graf
2014-10-31 3:47 Anton Blanchard
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=54914C85.30107@suse.de \
--to=agraf@suse.de \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=ulrich.weigand@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).