On 08/11/17 15:19, Guillaume Tucker wrote:
...
After a few more automated bisection attempts and a bug fix in LAVA, I've now found at least one potentially breaking commit:
commit d89e2378a97fafdc74cbf997e7c88af75b81610a Author: Robin Murphy robin.murphy@arm.com Date: Thu Oct 12 16:56:14 2017 +0100
drivers: flag buses which demand DMA configuration
I've run some boot tests manually with this revision and then also after reverting it in-place, these respectively failed and passed:
* d89e2378, failed: https://lava.collabora.co.uk/scheduler/job/978968
* d89e2378 reverted, passed: https://lava.collabora.co.uk/scheduler/job/978969
I then went on and tried the same but on top of next-20171108 and found that they both failed
* next-20171108, failed: https://lava.collabora.co.uk/scheduler/job/979063
* next-20171108 with d89e2378 reverted, failed as well: https://lava.collabora.co.uk/scheduler/job/979167
So this shows there is almost certainly another offending commit in -next. The errors in both cases are not quite the same, the last one is triggered by a BUG whereas the first one is a NULL pointer (I haven't looked any further). Also I don't think there's any fix for d89e2378a97fafdc74cbf997e7c88af75b81610a which is currently still in next.
This crash is a known issue [0] and we have been discussing this. Can you try applying [1]?
Cheers Jon
[0] https://lkml.org/lkml/2017/9/19/306 [1] https://patchwork.kernel.org/patch/9974835/