Re: [PATCH 1/3] powerpc: Don't use local named register variable in current_thread_info
From: Alexander Graf <hidden>
Date: 2014-12-17 09:27:39
Possibly related (same subject, not in this thread)
- 2014-10-31 · [PATCH 1/3] powerpc: Don't use local named register variable in current_thread_info · Anton Blanchard <hidden>
On 17.12.14 04:44, Anton Blanchard wrote:
Hi Alex,quoted
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