From: sylvain.bertrand@gmail.com
To: bugzilla-daemon@freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Bug 107784] [AMD tahiti XT] displayport broken
Date: Thu, 6 Sep 2018 12:31:49 +0000 [thread overview]
Message-ID: <20180906123149.GA427@freedom> (raw)
In-Reply-To: <bug-107784-502-eBEUAMV9yK@http.bugs.freedesktop.org/>
On Thu, Sep 06, 2018 at 10:04:53AM +0000, bugzilla-daemon@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=107784
>
> --- Comment #14 from Michel Dänzer <michel@daenzer.net> ---
> That's not consistent with the merge commit you identified earlier. So I'm
> afraid it's likely that you incorrectly classified some commits as good or bad.
> Maybe the problem doesn't occur 100% consistently even with bad commits, so try
> testing longer / more times before declaring a commit as good.
Not consistent? Could you be more specific? Some git magic I forgot again?
This time I used git bisect to go through "merge" commits properly.
I did test countless times those commits: that would mean this TSC code would
"side-effect" an ultra-rare bad condition into an nearly-all-the-time bad
condition. That amount of bad luck?
Whatever, I'll update amd-staging-drm-next, and go through a full bisection
again. I'll need probably days (lucky: I don't work).
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-06 12:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 17:22 [Bug 107784] [AMD tahiti XT] displayport broken bugzilla-daemon
2018-09-02 17:28 ` bugzilla-daemon
2018-09-03 9:17 ` bugzilla-daemon
2018-09-03 10:30 ` bugzilla-daemon
2018-09-03 14:55 ` bugzilla-daemon
2018-09-05 7:19 ` bugzilla-daemon
2018-09-05 11:50 ` bugzilla-daemon
2018-09-05 12:28 ` bugzilla-daemon
2018-09-05 12:33 ` bugzilla-daemon
2018-09-05 13:38 ` sylvain.bertrand
2018-09-05 13:38 ` bugzilla-daemon
2018-09-05 17:44 ` bugzilla-daemon
2018-09-05 21:48 ` sylvain.bertrand
2018-09-05 21:48 ` bugzilla-daemon
2018-09-05 21:52 ` bugzilla-daemon
2018-09-05 21:54 ` bugzilla-daemon
2018-09-06 10:04 ` bugzilla-daemon
2018-09-06 12:31 ` sylvain.bertrand [this message]
2018-09-06 12:31 ` bugzilla-daemon
2018-09-06 14:22 ` bugzilla-daemon
2018-09-06 16:20 ` sylvain.bertrand
2018-09-06 16:20 ` bugzilla-daemon
2018-09-06 21:10 ` sylvain.bertrand
2018-09-07 21:48 ` sylvain.bertrand
2018-09-06 21:10 ` bugzilla-daemon
2018-09-07 21:48 ` bugzilla-daemon
2018-09-09 3:45 ` sylvain.bertrand
2018-09-09 3:46 ` bugzilla-daemon
2018-09-09 5:57 ` bugzilla-daemon
2018-09-09 13:05 ` bugzilla-daemon
2018-09-09 13:11 ` bugzilla-daemon
2018-09-09 14:59 ` sylvain.bertrand
2018-09-09 14:59 ` bugzilla-daemon
2018-09-10 5:20 ` bugzilla-daemon
2018-09-10 9:15 ` bugzilla-daemon
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=20180906123149.GA427@freedom \
--to=sylvain.bertrand@gmail.com \
--cc=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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