From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105018] Kernel panic when waking up after screen goes blank.
Date: Tue, 01 May 2018 13:37:14 +0000 [thread overview]
Message-ID: <bug-105018-502-KYcDeqAe1S@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105018-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 938 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #33 from Öyvind Saether <oyvinds@everdot.org> ---
In my case the problem was not having xorg-x11-drv-amdgpu installed (how
embarrassing) which made xorg use xorg-x11-drv-ati. Yes, really. I assumed
Fedora 28 beta installed it along with all the other drives and didn't realize
until comparing the X logs on a box which didn't have a problem with one that
did. I did file the Fedora bug kindly asking xorg-x11-drv-amdgpu to be
installed as a default.
Simply installing xorg-x11-drv-amdgpu solved this error and amdgpu kernel
crash:
[12743.692030] kernel BUG at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4708!
I realize the immensity of my stupidity not realizing xorg-x11-drv-amdgpu will
make you laugh but it's not like the kernel panic message warned me.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1731 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
next prev parent reply other threads:[~2018-05-01 13:37 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 1:13 [Bug 105018] Kernel panic when waking up after screen goes blank bugzilla-daemon
2018-02-09 1:16 ` bugzilla-daemon
2018-02-09 9:21 ` bugzilla-daemon
2018-02-10 17:25 ` bugzilla-daemon
2018-02-10 17:31 ` bugzilla-daemon
2018-02-11 0:32 ` bugzilla-daemon
2018-02-12 15:55 ` bugzilla-daemon
2018-02-13 3:30 ` bugzilla-daemon
2018-02-13 3:38 ` bugzilla-daemon
2018-02-13 16:13 ` bugzilla-daemon
2018-02-13 16:13 ` bugzilla-daemon
2018-02-13 16:13 ` bugzilla-daemon
2018-02-13 16:14 ` bugzilla-daemon
2018-02-13 16:14 ` bugzilla-daemon
2018-02-13 18:40 ` bugzilla-daemon
2018-02-14 5:55 ` bugzilla-daemon
2018-02-14 6:14 ` bugzilla-daemon
2018-02-14 6:52 ` bugzilla-daemon
2018-02-14 14:35 ` bugzilla-daemon
2018-02-14 16:13 ` bugzilla-daemon
2018-02-15 20:59 ` bugzilla-daemon
2018-02-23 23:23 ` bugzilla-daemon
2018-02-27 5:23 ` bugzilla-daemon
2018-03-16 0:40 ` bugzilla-daemon
2018-03-20 0:55 ` bugzilla-daemon
2018-03-22 0:09 ` bugzilla-daemon
2018-03-24 12:49 ` bugzilla-daemon
2018-03-24 12:58 ` bugzilla-daemon
2018-03-26 1:25 ` bugzilla-daemon
2018-04-12 0:41 ` bugzilla-daemon
2018-04-12 4:19 ` bugzilla-daemon
2018-04-13 0:25 ` bugzilla-daemon
2018-04-30 14:10 ` bugzilla-daemon
2018-04-30 14:55 ` bugzilla-daemon
2018-05-01 13:37 ` bugzilla-daemon [this message]
2018-05-01 13:56 ` bugzilla-daemon
2018-06-23 13:26 ` bugzilla-daemon
2018-06-27 18:51 ` bugzilla-daemon
2018-07-05 5:56 ` bugzilla-daemon
2018-07-05 6:03 ` bugzilla-daemon
2018-09-06 18:12 ` bugzilla-daemon
2018-09-07 7:40 ` bugzilla-daemon
2018-09-07 22:35 ` bugzilla-daemon
2018-12-10 14:47 ` 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-105018-502-KYcDeqAe1S@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.