From: Pavel Machek <pavel@denx.de>
Sent: 19 March 2020 21:24

Hi!

From: cip-dev <cip-dev-bounces@lists.cip-project.org> On Behalf Of Chris
Paterson
Sent: 19 March 2020 11:23

Hello Pavel,

From: Pavel Machek <pavel@denx.de>
Sent: 19 March 2020 11:05

[...]

like tests are unreliable (and even my basic assumptions may be worth
re-testing).

Can you help? I'll be away from console for a few hours now.

I'll get bisecting.

Last 'good' patch is: 2089f853a8c3 ("drm/i915: disable tracing on
-RT")
The first 'bad' path is: c82fe0af5e58 ("drm/i915: skip
DRM_I915_LOW_LEVEL_TRACEPOINTS with NOTRACE")

Don't ask me why c82fe0af5e58 causes a boot issue on the de0-nano
board but at least it's a starting point for you.

[...]

When bisection finds a commit touching code that you're not even
building, the answer should not be "don't ask me why" but "this is not
a reproducible bug".

That's my job, I guess. I asked for bisect and got bisect
(thanks!). And yes, I have to agree:

In the meantime:

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/478548891
https://lava.ciplatform.org/scheduler/job/13037

So yes, it seems this is not reproducible. Is it easy to make the test
run .. say 5 times?

I'm starting to suspect

pick fc9f4631a290 irqwork: push most work into softirq context

Best regards,
                                                              Pavel
--
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany