On 09/11/17 09:55, Jon Hunter wrote:
On 08/11/17 16:42, Guillaume Tucker wrote:
On 08/11/17 15:57, Jon Hunter wrote:
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@xxxxxxx>
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]?
So with next-20171108 + d89e2378a9 reverted + [1] applied:
https://lava.collabora.co.uk/scheduler/job/979173
No visible kernel crash in the log but it hangs.
I also tried next-20171108 + [1] applied only:
https://lava.collabora.co.uk/scheduler/job/979179
which also appears to hang.
Thanks for the update. I am wondering if it is one of the kernel modules
that is getting loaded because booting multi_v7_defconfig and loading no
modules does not hang for me. I will take a look but I might not get to
it until next week.
I actually built these kernel revisions with module support
disabled to speed up the builds, and no modules are being
downloaded in the LAVA job.
If you have a public URL with your known working kernel zImage
and dtb, let me know so I could re-run the same test LAVA boot
test to see if I get the same results as you (i.e. no hang).
Guillaume
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
