From: Pavel Machek <pavel@denx.de>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] realtime on de0-nano bisection
Date: Thu, 19 Mar 2020 22:23:58 +0100 [thread overview]
Message-ID: <20200319212357.GA28591@duo.ucw.cz> (raw)
In-Reply-To: <5f2a3e394d6a5e9bc8b9e05df0b17c758c9c46fb.camel@codethink.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1593 bytes --]
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
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev
next prev parent reply other threads:[~2020-03-19 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 11:05 [cip-dev] realtime on de0-nano bisection Pavel Machek
2020-03-19 11:23 ` Chris Paterson
2020-03-19 11:34 ` Chris Paterson
2020-03-19 16:13 ` Chris Paterson
2020-03-19 21:07 ` Ben Hutchings
2020-03-19 21:23 ` Pavel Machek [this message]
2020-03-20 9:56 ` Chris Paterson
2020-03-23 22:17 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200319212357.GA28591@duo.ucw.cz \
--to=pavel@denx.de \
--cc=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).