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: Thu, 26 Apr 2018 14:02:06 +0000	[thread overview]
Message-ID: <bug-106159-502-RNgSahtfbh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106159-502@http.bugs.freedesktop.org/>


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

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

--- Comment #15 from Joel Sass <sass.joel@gmail.com> ---
Created attachment 139132
  --> https://bugs.freedesktop.org/attachment.cgi?id=139132&action=edit
This is the dmesg from an ssh session after attaching a monitor to my MST hub

root@nope:~/errors# uname -a
Linux nope 4.16.0-rc7+ #2 SMP Thu Apr 26 08:45:00 EDT 2018 x86_64 x86_64 x86_64
GNU/Linux

Kernel git acquired here:
https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-fixes-4.17

Key message from dmesg:

[  526.900234] Call Trace:
[  526.900280]  dm_dp_mst_get_modes+0xce/0x120 [amdgpu]
[  526.900288]  drm_helper_probe_single_connector_modes+0x199/0x6c0
[drm_kms_helper]
[  526.900294]  ? jbd2_journal_stop+0xf3/0x3e0
[  526.900297]  ? __ext4_journal_stop+0x37/0xa0
[  526.900309]  drm_mode_getconnector+0x2c4/0x300 [drm]
[  526.900314]  ? _cond_resched+0x16/0x40
[  526.900324]  ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm]
[  526.900333]  drm_ioctl_kernel+0x67/0xb0 [drm]
[  526.900342]  drm_ioctl+0x2a9/0x350 [drm]
[  526.900352]  ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm]
[  526.900381]  amdgpu_drm_ioctl+0x46/0x80 [amdgpu]
[  526.900385]  do_vfs_ioctl+0xa2/0x5f0
[  526.900389]  ? vfs_write+0x162/0x1a0
[  526.900391]  SyS_ioctl+0x74/0x80
[  526.900395]  do_syscall_64+0x60/0x110
[  526.900399]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

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

[-- Attachment #1.2: Type: text/html, Size: 2742 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-26 14:02 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
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 [this message]
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-RNgSahtfbh@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