All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94530] AMD R9 Nano reset problem
Date: Sun, 24 Apr 2016 11:27:25 +0000	[thread overview]
Message-ID: <bug-94530-502-ZLv7jBL1uF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94530-502@http.bugs.freedesktop.org/>


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

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

spam@madsitenet.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |spam@madsitenet.de

--- Comment #1 from spam@madsitenet.de ---
Hi,

I'am experiencing the same problem with my 'R9 Fury' (also Fiji), but I'm
unable to install AMD Crimson drivers for a few weeks now. Last working version
was 16.3.1 (I think). 
Now, when the installer is trying to update/install the display driver, my
screen goes blank, and the HOST (as well as the VM) hangs. Only a power off can
help.

Until 16.3.1 the screen went blank also (and the GPU fans started to spin at
max speed), but the VM/HOST did NOT hang.

If more info is required, I am glad to provide them :)

See you,
Michael

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

[-- Attachment #1.2: Type: text/html, Size: 2119 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

  reply	other threads:[~2016-04-24 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14  9:55 [Bug 94530] AMD R9 Nano reset problem bugzilla-daemon
2016-04-24 11:27 ` bugzilla-daemon [this message]
2016-10-28  9:56 ` bugzilla-daemon
2016-10-28 15:45 ` bugzilla-daemon
2016-10-28 20:21 ` bugzilla-daemon
2019-11-19  8:07 ` 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-94530-502-ZLv7jBL1uF@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.