On Mon, Dec 19, 2011 at 11:05 AM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
2011/12/18 Michael Hope michael.hope@linaro.org:
2011/12/18 Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org:
On 17 December 2011 06:30, Zach Pfeffer zach.pfeffer@linaro.org wrote:
2011/12/17 Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org:
Hi, I've verified that toolchain 11.12 compiles our userland ok, the only problem is w/ the kernel. A build using the 11.12 toolchain for userland and an older toolchain for the kernel is ok.
Is is possible to create an android-build with this configuration?
Yes, I already did: https://android-build.linaro.org/builds/~berolinux/panda-toolchain-test/#bui...
Those sound good. Ricardo have you compiled and booted a kernel with the generic 11.12 arm-eabi- toolchain?
Or with any other 11.12 toolchain for that matter? We currently build arm-eabi- and arm-linux-androideabi- toolchains, so arm-linux-gnueabi- is untested on our side. But that's likely what you're using. I don't think there's enough of a difference between arm-linux-androideabi- and arm-linux-gnueabi- to make the theory that one boots while the other doesn't plausible.
Maybe John Rigby can help. I saw the failure at boot, do you still see the same behavior?
Yes
If so I think John has a JTAG that he could trace with.
That would definitely be useful
+1 to that. I wonder if the kernel guys have any hints for tracking this type of problem down? Early printk() or similar?
Michael, is there anything else we can do or check?
Nothing that I know of, sorry. I've looked through the commits and the most likely problem is unaligned loads and stores which could have exposed a latent bug in the kernel or compiler. The -mno-unaligned-access flag will turn this code off and should help point the finger.
-- Michael