dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105733] Amdgpu randomly hangs and only ssh works. Mouse cursor moves sometimes but does nothing. Keyboard stops working.
Date: Wed, 23 Jan 2019 19:46:34 +0000	[thread overview]
Message-ID: <bug-105733-502-ETNXjJR8ER@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105733-502@http.bugs.freedesktop.org/>


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

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

--- Comment #58 from krutoileshii@gmail.com ---
The corruption suggestion is interesting. My RX580 does this and now it
won't even boot on windows anymore, just crashes.

On Wed, Jan 23, 2019, 12:44 PM <bugzilla-daemon@freedesktop.org wrote:

> las@protonmail.ch changed bug 105733
> <https://bugs.freedesktop.org/show_bug.cgi?id=105733>
> What Removed Added
> CC   las@protonmail.ch
>
> *Comment # 57 <https://bugs.freedesktop.org/show_bug.cgi?id=105733#c57> on
> bug 105733 <https://bugs.freedesktop.org/show_bug.cgi?id=105733> from
> las@protonmail.ch <las@protonmail.ch> *
>
> Created attachment 143206 <https://bugs.freedesktop.org/attachment.cgi?id=143206> [details] <https://bugs.freedesktop.org/attachment.cgi?id=143206&action=edit>
> I get these errors when attempting to boot after a normal GPU hang and KMS
> happens
>
> Recently I've been getting another type of hang somehow. After a normal hang
> happens, where my screen gets garbled output, I can't even get past KMS in the
> next couple of boots. I can fix this by flipping my VBIOS switch, which heavily
> leads me to believe that amdgpu somehow corrupts the GPU's firmware. I have
> attached the error I get when KMS happens at boot, which happens after I get a
> hang while using the system normally. The monitor doesn't display anything when
> this happens, but I can still control caps lock, etc., however I can not shut
> it off normally. I have not tested whether SSH and such still work.
>
> This honestly makes me doubt whether what I am experiencing is the same bug; is
> it simply a faulty GPU? I am using a Sapphire RX 580 4GB, which I bought used
> from a windows user. It *did* work for him, so obviously it isn't entirely
> broken at least.
>
> ------------------------------
> You are receiving this mail because:
>
>    - You are on the CC list for the bug.
>
>

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

[-- Attachment #1.2: Type: text/html, Size: 5122 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:[~2019-01-23 19:46 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-25  4:47 [Bug 105733] Amdgpu randomly hangs and only ssh works. Mouse cursor moves sometimes but does nothing. Keyboard stops working bugzilla-daemon
2018-03-25  4:49 ` bugzilla-daemon
2018-03-25 16:52 ` bugzilla-daemon
2018-03-27  3:02 ` bugzilla-daemon
2018-03-27 11:52 ` bugzilla-daemon
2018-03-28 15:34 ` bugzilla-daemon
2018-04-01 14:15 ` bugzilla-daemon
2018-04-04 20:49 ` bugzilla-daemon
2018-04-09  1:19 ` bugzilla-daemon
2018-04-09  1:22 ` bugzilla-daemon
2018-04-11  9:31 ` bugzilla-daemon
2018-04-27 11:26 ` bugzilla-daemon
2018-04-27 12:41 ` bugzilla-daemon
2018-05-02  7:51 ` bugzilla-daemon
2018-05-08  7:38 ` bugzilla-daemon
2018-07-08 12:11 ` bugzilla-daemon
2018-07-26  8:20 ` bugzilla-daemon
2018-07-26  8:26 ` bugzilla-daemon
2018-07-26  8:27 ` bugzilla-daemon
2018-07-26  8:31 ` bugzilla-daemon
2018-07-26  8:32 ` bugzilla-daemon
2018-07-26  9:09 ` bugzilla-daemon
2018-07-26  9:19 ` bugzilla-daemon
2018-08-13  2:24 ` bugzilla-daemon
2018-08-13  2:25 ` bugzilla-daemon
2018-08-14 19:46 ` bugzilla-daemon
2018-08-14 20:32 ` bugzilla-daemon
2018-08-15  7:11 ` bugzilla-daemon
2018-08-23 19:10 ` bugzilla-daemon
2018-08-23 19:33 ` bugzilla-daemon
2018-08-24 12:35 ` bugzilla-daemon
2018-08-26 11:18 ` bugzilla-daemon
2018-08-26 22:02 ` bugzilla-daemon
2018-08-27 21:55 ` bugzilla-daemon
2018-08-30 20:01 ` bugzilla-daemon
2018-08-31  9:04 ` bugzilla-daemon
2018-09-03  8:46 ` bugzilla-daemon
2018-09-06 13:06 ` bugzilla-daemon
2018-09-14 16:33 ` bugzilla-daemon
2018-10-31 12:49 ` bugzilla-daemon
2018-11-04  1:19 ` bugzilla-daemon
2018-11-16 14:28 ` bugzilla-daemon
2018-11-16 14:44 ` bugzilla-daemon
2018-11-17 13:28 ` bugzilla-daemon
2018-11-17 15:36 ` bugzilla-daemon
2018-11-19  5:08 ` bugzilla-daemon
2018-11-19  5:31 ` bugzilla-daemon
2018-11-20 14:15 ` bugzilla-daemon
2019-02-05 16:27   ` Garry Hurley
2018-11-20 15:18 ` bugzilla-daemon
2018-11-20 20:32 ` bugzilla-daemon
2018-11-21  0:52 ` bugzilla-daemon
2018-11-22 18:47 ` bugzilla-daemon
2018-11-22 19:27 ` bugzilla-daemon
2018-11-22 19:28 ` bugzilla-daemon
2019-01-15 14:18 ` bugzilla-daemon
2019-01-17 22:25 ` bugzilla-daemon
2019-01-17 22:32 ` bugzilla-daemon
2019-01-23 19:44 ` bugzilla-daemon
2019-01-23 19:46 ` bugzilla-daemon [this message]
2019-01-23 20:23 ` bugzilla-daemon
2019-01-23 21:05 ` bugzilla-daemon
2019-01-25  7:36 ` bugzilla-daemon
2019-01-25  8:20 ` bugzilla-daemon
2019-01-26 13:18 ` bugzilla-daemon
2019-02-02 10:55 ` bugzilla-daemon
2019-02-04  3:17 ` bugzilla-daemon
2019-02-04 18:38 ` bugzilla-daemon
2019-02-04 18:42 ` bugzilla-daemon
2019-02-05  2:18 ` bugzilla-daemon
2019-02-05 13:42 ` bugzilla-daemon
2019-02-05 16:28 ` bugzilla-daemon
2019-02-10  0:13 ` bugzilla-daemon
2019-02-23 12:14 ` bugzilla-daemon
2019-03-09 10:31 ` bugzilla-daemon
2019-03-10  9:37 ` bugzilla-daemon
2019-03-10 10:03 ` bugzilla-daemon
2019-03-10 10:07 ` bugzilla-daemon
2019-03-10 10:55 ` bugzilla-daemon
2019-03-11  6:49 ` bugzilla-daemon
2019-03-12  8:35 ` bugzilla-daemon
2019-07-16 10:18 ` bugzilla-daemon
2019-07-17  3:00 ` bugzilla-daemon
2019-07-17  7:58 ` 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-105733-502-ETNXjJR8ER@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;
as well as URLs for NNTP newsgroup(s).