From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111986] 5700 XT hangs entire system in games
Date: Mon, 14 Oct 2019 17:54:15 +0000 [thread overview]
Message-ID: <bug-111986-502-op2Uy5nHEa@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111986-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1171 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111986
--- Comment #8 from Daniel Suarez <danielsuarez369@protonmail.com> ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #7)
> Thanks for your bug report.
>
> It would be really helpful to have the content of dmesg when your system
> hangs.
> You can get it from another computer using ssh or you could extract it from
> /var/log/dmesg* files after a reboot.
>
> You can also check some of the existing bugs and see if they are the same as
> yours:
> - https://bugs.freedesktop.org/show_bug.cgi?id=111986
> - https://bugzilla.kernel.org/show_bug.cgi?id=205169
Thank you so much for taking the time to reply to my bug report, I really
wanted to provide that but unfortunately it doesn't exist, I even did "ls -ls
/var/log/" to make sure it wasn't dolphin hiding the file, but a dmesg
file/folder doesn't exist. Closest thing I see is "Xorg.0.log.old" which I will
attach just incase
As for bug report 205169, I do not believe so since my system hangs regardless
if a game or application is fullscreen or not.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2269 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
next prev parent reply other threads:[~2019-10-14 17:54 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 [this message]
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
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-op2Uy5nHEa@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.