dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107784] [AMD tahiti XT] displayport broken
Date: Wed, 05 Sep 2018 17:44:25 +0000	[thread overview]
Message-ID: <bug-107784-502-JPkE2F2FKE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107784-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1199 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107784

--- Comment #10 from Felix Schwarz <felix.schwarz@oss.schwarz.eu> ---
(In reply to Sylvain BERTRAND from comment #9)
> Ok, I got it. Since my git knowledge is quite limited, this "merge" commit is
> opening a vast sea of new commits to test. 
> 
> I'll dive into bisection using bisect (which actually deals with those merge
> commits). I am a bit scared of the amount of commits, may take hours/days.

Don't worry: If your problem is immediately obvious after booting this should
be not too bad. You can also use the versions you build manually to "seed" the
git bisection process. That way you reduce the number of bisection steps a bit.

If you encounter non-bootable kernels please use "git bisect skip" - this is
important! DO NOT mark as "good"/"bad" in these cases.

> Please, in the foreseable futur, do not make amd-staging-drm-next lag that
> much.

I think the "drm-next" thing was mandated by Linus so there is not much which
can be done at this point. But anyway if you have an easily reproducible
problem bisection is not too bad.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2140 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-09-05 17:44 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 [this message]
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
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=bug-107784-502-JPkE2F2FKE@http.bugs.freedesktop.org/ \
    --to=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