From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101478] Display not working after a certain commit
Date: Sat, 17 Jun 2017 07:01:48 +0000 [thread overview]
Message-ID: <bug-101478-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1285 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101478
Bug ID: 101478
Summary: Display not working after a certain commit
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: john.ettedgui@gmail.com
Created attachment 132016
--> https://bugs.freedesktop.org/attachment.cgi?id=132016&action=edit
dmesg
Hello,
I've been using Alex's linux amd-staging-4.11 tree for a bit, but a certain
commit makes it unusable for me:
commit 70b696cc1961fca375f4eeb649df90d17016fc52
drm/amdgpu: Add module param to control SI support
With this commit, the display stops getting updated during boot, and based on
dmesg sddm crashes. The system is still responsive and seems to work fine apart
from the display when I tried using it from SSH.
I've attached the dmesg.
I am using a 280X so SI.
I'm on Arch Linux 64b, up to date.
Maybe my configuration needs to change after this commit, I'm happy to try
anything.
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2677 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 reply other threads:[~2017-06-17 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 7:01 bugzilla-daemon [this message]
2017-06-19 2:31 ` [Bug 101478] Display not working after a certain commit bugzilla-daemon
2017-06-19 3:39 ` bugzilla-daemon
2018-07-20 9:23 ` 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-101478-502@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.