Re: next boot: 21 passed 12 failed (next/next-20140522)

On Thu, May 22, 2014 at 3:04 PM, Stephen Warren swarren@wwwdotorg.org wrote:

On 05/22/2014 05:50 AM, Olof's autobooter wrote:

...

Failed boards:

beaver       tegra_defconfig               :      FAILED  1:26.98
cubie2       multi_v7_defconfig            :      FAILED  1:26.94
cubie2       multi_lpae_defconfig          :      FAILED  1:24.51
dalmore      tegra_defconfig               :      FAILED  1:32.02
hummingboard imx_v6_v7_defconfig           :      FAILED  0:29.85
hummingboard multi_v7_defconfig            :      FAILED  0:24.91
panda        multi_v7_defconfig            :      FAILED  1:25.65
snowball     multi_v7_defconfig            :      FAILED  1:10.25
trimslice    tegra_defconfig               :      FAILED  1:29.62
trimslice    multi_v7_defconfig            :      FAILED  1:30.16
wandboard    imx_v6_v7_defconfig           :      FAILED  2:57.05
wandboard    multi_v7_defconfig            :      FAILED  0:24.98

There are at least 2 problems affecting Tegra:

1. There's some core issue in DMA allocations which causes many drivers

to fail to probe. It looks like this affects Panda too. I haven't investigated this yet.

Thanks, I had forgotten to look at the results from last night.

I'll kick off a bisect, but not on panda since it still has stability issues on multi_v7. I'll do it with the hummingboard instead.

-Olof