On Mon, Apr 07, 2014 at 07:15:34AM -0700, Olof Johansson wrote:
On Mon, Apr 7, 2014 at 2:10 AM, Russell King - ARM Linux linux@arm.linux.org.uk wrote:
On Sun, Apr 06, 2014 at 11:12:51PM -0700, Olof's autobooter wrote:
Failed boards:
cubie multi_v7_defconfig : FAILED 1:05.77 cubie2 sunxi_defconfig : FAILED 1:21.41 cubie2 multi_v7_defconfig : FAILED 1:09.94 cubie2 multi_lpae_defconfig : FAILED 0:59.68 hummingboard multi_v7_defconfig : FAILED 1:04.69 panda multi_v7_defconfig : FAILED 1:36.35 snow exynos_defconfig : FAILED 2:24.53 snowball multi_v7_defconfig : FAILED 1:07.90 wandboard multi_v7_defconfig : FAILED 1:05.66So do we have any clues what's causing these to fail?
I'm pretty sure these will be fixed by:
"arm: pj4: check cpu id for pj4 cp0 access"
That I don't see in -next yet. Adding Chao on this thread, since we've already requested the patch to be sent to the patch tracker...
I haven't applied anything from the patch system for the last month or more as I've been soo bogged down with the l2c and fec changes.
A good question at this point is what change introduced this regression, and why did that change go through a different tree to that which is being asked to carry the fixes?