All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460
Date: Fri, 03 Feb 2017 20:05:58 +0000	[thread overview]
Message-ID: <bug-99275-502-j4LSUPIW4u@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99275-502@http.bugs.freedesktop.org/>


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

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

--- Comment #18 from Reimar Imhof <tuxuser@quantentunnel.de> ---
That firmware kills kde / plasma5 and freezes the machine!

What I've done:
Copied the firmware files to /lib/firmware/amdgpu/
ran dracut to build new initrd
reboot

graphical login comes up
after logging in to kde plasma 5 the machine freezes

After a hard power of I logged into icewm.
That desktop came up. I opened an console. Ok. 
Started dolphin. Machine has frozen immediately. Even the clock in the desktop
toolbar stopped working.

Before starting dolphin I had a look at dmesg. I couldn't find any new error
messages. Unfortunately I do not have these messages around any more.
I also had a look at the /var/log/Xorg.<i>.log
There was no log written from the kde session freezing the machine.

Could you please test that firmware with a kde plasma 5 desktop? Please!

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

[-- Attachment #1.2: Type: text/html, Size: 1815 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:[~2017-02-03 20:05 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 19:25 [Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460 bugzilla-daemon
2017-01-04 19:34 ` bugzilla-daemon
2017-01-04 21:17 ` bugzilla-daemon
2017-01-04 21:17 ` bugzilla-daemon
2017-01-04 21:18 ` bugzilla-daemon
2017-01-04 21:24 ` bugzilla-daemon
2017-01-04 21:35 ` bugzilla-daemon
2017-01-05  9:56 ` bugzilla-daemon
2017-01-05 18:09 ` bugzilla-daemon
2017-01-05 18:36 ` bugzilla-daemon
2017-01-16 20:55 ` bugzilla-daemon
2017-01-29 19:03 ` bugzilla-daemon
2017-01-29 19:04 ` bugzilla-daemon
2017-01-29 19:11 ` bugzilla-daemon
2017-01-29 19:13 ` bugzilla-daemon
2017-01-31  6:42 ` bugzilla-daemon
2017-02-01 21:08 ` bugzilla-daemon
2017-02-01 22:10 ` bugzilla-daemon
2017-02-03 20:05 ` bugzilla-daemon [this message]
2017-02-03 20:11 ` bugzilla-daemon
2017-02-03 20:46 ` bugzilla-daemon
2017-02-12 16:12 ` bugzilla-daemon
2017-02-12 16:17 ` bugzilla-daemon
2017-02-12 16:30 ` bugzilla-daemon
2017-02-12 19:21 ` bugzilla-daemon
2017-02-13  3:10 ` bugzilla-daemon
2017-02-13 18:55 ` bugzilla-daemon
2017-02-14  2:10 ` bugzilla-daemon
2017-02-14 11:55 ` bugzilla-daemon
2017-02-14 11:57 ` bugzilla-daemon
2017-02-14 12:02 ` bugzilla-daemon
2017-02-14 14:05 ` bugzilla-daemon
2017-02-14 15:29 ` bugzilla-daemon
2017-02-14 19:32 ` bugzilla-daemon
2017-02-22 21:25 ` bugzilla-daemon
2017-02-22 21:26 ` bugzilla-daemon
2018-03-24 11:20 ` bugzilla-daemon
2018-12-19 20:07 ` bugzilla-daemon
2019-11-19  8:12 ` 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-99275-502-j4LSUPIW4u@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.