All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111986] 5700 XT hangs entire system in games
Date: Tue, 15 Oct 2019 00:24:13 +0000	[thread overview]
Message-ID: <bug-111986-502-8GG31jQ4ZL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111986-502@http.bugs.freedesktop.org/>


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

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

--- Comment #12 from Daniel Suarez <danielsuarez369@protonmail.com> ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #11)
> (In reply to Daniel Suarez from comment #10)
> > Created attachment 145736 [details]
> > Got by running sudo journalctl -b > dmesg.log
> > 
> > Thanks to the explanation by someone I believe I understand now what you
> > meant. I went ahead and reproduced the hang by running gfxbench and when the
> > system hanged at around 3:23 I force shutdown seconds later, once I booted
> > in I ran "sudo journalctl -b > dmesg.log" and I am sending you the output now
> 
> You need to use "sudo journalctl -b -1 > dmesg.log" to get the logs from the
> previous boot (= the one that hanged).

I am deeply sorry, I attach the correct one now

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

[-- Attachment #1.2: Type: text/html, Size: 2125 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-10-15  0:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-13  2:29 [Bug 111986] 5700 XT hangs entire system in games bugzilla-daemon
2019-10-13  2:46 ` bugzilla-daemon
2019-10-13  4:06 ` bugzilla-daemon
2019-10-13  4:07 ` bugzilla-daemon
2019-10-13  4:07 ` bugzilla-daemon
2019-10-13  4:29 ` bugzilla-daemon
2019-10-13 14:42 ` bugzilla-daemon
2019-10-13 14:53 ` bugzilla-daemon
2019-10-13 17:50 ` bugzilla-daemon
2019-10-14  9:54 ` bugzilla-daemon
2019-10-14 17:54 ` bugzilla-daemon
2019-10-14 17:54 ` bugzilla-daemon
2019-10-14 19:27 ` bugzilla-daemon
2019-10-14 20:17 ` bugzilla-daemon
2019-10-15  0:24 ` bugzilla-daemon [this message]
2019-10-15  0:24 ` bugzilla-daemon
2019-10-15 17:20 ` bugzilla-daemon
2019-10-22 16:12 ` bugzilla-daemon
2019-10-22 17:25 ` bugzilla-daemon
2019-11-19  9:57 ` 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-111986-502-8GG31jQ4ZL@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.