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 107213] [amdgpu/DisplayPort] KDE Wayland session is segfaulting right after login
Date: Fri, 13 Jul 2018 14:12:53 +0000	[thread overview]
Message-ID: <bug-107213-502-bUZhQSveyv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107213-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Shmerl <shtetldik@gmail.com> ---
Created attachment 140624
  --> https://bugs.freedesktop.org/attachment.cgi?id=140624&action=edit
dmesg output

See attached dmesg output. Once thing to note, I consistently get a black
screen after boot (the monitor goes into a sleep mode). I need to turn monitor
off, turn it back on, switch to tty1 (then monitor turns on), then log in there
and restart sddm. Only then sddm appears on tty7. After that, Wayland session
log-in fails (I tried a couple of times which is reflected in dmesg).

First try didn't result in segfault in dmesg, just in *ERROR* REG_WAIT, but
second attempt also added as segfault.

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

[-- Attachment #1.2: Type: text/html, Size: 1749 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-07-13 14:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13  1:46 [Bug 107213] [amdgpu/DisplayPort] KDE Wayland session is segfaulting right after login bugzilla-daemon
2018-07-13  7:55 ` bugzilla-daemon
2018-07-13 14:12 ` bugzilla-daemon [this message]
2018-08-27  3:11 ` bugzilla-daemon
2018-08-29  4:27 ` bugzilla-daemon
2018-09-03  1:51 ` bugzilla-daemon
2018-09-03  1:53 ` bugzilla-daemon
2018-09-03  2:00 ` bugzilla-daemon
2018-09-04  9:17 ` bugzilla-daemon
2018-09-04 11:45   ` sylvain.bertrand
2018-09-04  9:19 ` bugzilla-daemon
2018-09-04 11:45 ` bugzilla-daemon
2018-09-04 12:32 ` bugzilla-daemon
2018-09-04 18:12   ` sylvain.bertrand
2018-09-04 18:12 ` bugzilla-daemon
2018-09-05 12:52 ` bugzilla-daemon
2018-09-05 13:03 ` bugzilla-daemon
2018-09-14 13:12 ` bugzilla-daemon
2018-09-14 14:27 ` bugzilla-daemon
2018-09-14 14:35 ` bugzilla-daemon
2018-09-14 15:10 ` bugzilla-daemon
2018-09-19  7:04 ` bugzilla-daemon
2018-09-26  3:20 ` bugzilla-daemon
2018-10-03 15:37 ` bugzilla-daemon
2018-10-11 16:34 ` bugzilla-daemon
2019-11-19  8:43 ` 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-107213-502-bUZhQSveyv@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