All of 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: Mon, 03 Sep 2018 10:30:34 +0000	[thread overview]
Message-ID: <bug-107784-502-kyVGcF0WS8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107784-502@http.bugs.freedesktop.org/>


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

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

--- Comment #3 from Sylvain BERTRAND <sylvain.bertrand@gmail.com> ---
On Mon, Sep 03, 2018 at 09:17:30AM +0000, bugzilla-daemon@freedesktop.org
wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=107784
> 
> --- Comment #2 from Michel Dänzer <michel@daenzer.net> ---
> Can you bisect?

I don't think it is reasonable because something bad happens between the 4.18
to 4.19 jump, then I would have to bisect on thousands of commits.
Additionnaly, I had to remove my git repo of 4.18 and clone again 4.19 because
git was unable to perform the pull, even with reset and force (I probably don't
know some git magic here): lost the last working 4.18 commit.

I would need to know what drm/amdgpu related commits where added from
4.18->4.19, the person who did this has this knowledge.

I'll try to fool around with git to see if I can manage something in the mean
time (with dates and targetting drm/amdgpu directories).

> P.S. Please enable CONFIG_UNWINDER_ORC in your kernel build, to make the
> backtraces in dmesg more useful.

ORC breaks linux build. Only guess compile (actually kbuild and kconfig are
quite broken in this 4.19), but it's an optimized build without symbols.

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

[-- Attachment #1.2: Type: text/html, Size: 2474 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-03 10:30 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 [this message]
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
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-kyVGcF0WS8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.