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 106159] When connecting or disconnecting a displayport to a DP hub with 4.16.2+ kernel, hard freeze with frozen video output
Date: Wed, 25 Apr 2018 20:58:11 +0000	[thread overview]
Message-ID: <bug-106159-502-NEmQT8E0ys@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106159-502@http.bugs.freedesktop.org/>


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

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

--- Comment #11 from Joel Sass <sass.joel@gmail.com> ---
It appears that the patch I manually created isn't working out so hot. During
compiling, I'm seeing this error for amdgpu_dm_mst_types.c

drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c: In
function ‘dm_dp_mst_dc_sink_create’:
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:205:2:
error: ‘dc_sink’ undeclared (first use in this function)
  dc_sink = dc_link_add_remote_sink(
  ^
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:205:2:
note: each undeclared identifier is reported only once for each function it
appears in
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:209:4:
error: ‘init_params’ undeclared (first use in this function)
   &init_params);
    ^
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c: In
function ‘dm_dp_mst_get_modes’:
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:232:28:
warning: unused variable ‘init_params’ [-Wunused-variable]
   struct dc_sink_init_data init_params = {
                            ^
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:231:19:
warning: unused variable ‘dc_sink’ [-Wunused-variable]
   struct dc_sink *dc_sink;
                   ^
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:251:5:
error: request for member ‘sink_signal’ in something not a structure or union
     .sink_signal = SIGNAL_TYPE_DISPLAY_PORT_MST };
     ^
scripts/Makefile.build:332: recipe for target
'drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.o' failed
make[4]: ***
[drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.o] Error 1
scripts/Makefile.build:606: recipe for target 'drivers/gpu/drm/amd/amdgpu'
failed
make[3]: *** [drivers/gpu/drm/amd/amdgpu] Error 2
scripts/Makefile.build:606: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:606: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....

Could someone take a look at the file I've attached please?

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

[-- Attachment #1.2: Type: text/html, Size: 3313 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-04-25 20:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 18:51 [Bug 106159] When connecting or disconnecting a displayport to a DP hub with 4.16.2+ kernel, hard freeze with frozen video output bugzilla-daemon
2018-04-20 18:52 ` bugzilla-daemon
2018-04-20 18:52 ` bugzilla-daemon
2018-04-20 18:53 ` bugzilla-daemon
2018-04-24 19:30 ` bugzilla-daemon
2018-04-24 19:31 ` bugzilla-daemon
2018-04-24 20:34 ` bugzilla-daemon
2018-04-24 21:37 ` bugzilla-daemon
2018-04-25 15:23 ` bugzilla-daemon
2018-04-25 15:24 ` bugzilla-daemon
2018-04-25 15:25 ` bugzilla-daemon
2018-04-25 20:58 ` bugzilla-daemon [this message]
2018-04-25 21:01 ` bugzilla-daemon
2018-04-25 21:15 ` bugzilla-daemon
2018-04-26 13:57 ` bugzilla-daemon
2018-04-26 14:02 ` bugzilla-daemon
2018-04-26 14:06 ` bugzilla-daemon
2018-06-27 15:25 ` bugzilla-daemon
2019-11-19  8:35 ` 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-106159-502-NEmQT8E0ys@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