From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370)
Date: Tue, 17 Apr 2018 20:06:57 +0000 [thread overview]
Message-ID: <bug-105425-502-Sb6jvb4bLg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105425-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2597 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #34 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
(In reply to iive from comment #33)
Ahhh... you've reminded me of a detail that I have in fact noticed but forgot
to mention: After the machine freezes and becomes completely unresponsive, some
keyboard leds will indeed turn off after roughly 10 seconds. I only noticed
this because I currently have a backlit keyboard that has the lighting
controlled by the Scroll Lock LED... I saw that a few seconds after the crash,
the keyboard lighting always turns itself off.
I cannot connect the computers with a serial cable: I think the motherboards
are too modern to have a serial port, and they're at a far distance in opposite
rooms. Both computers are connected to the same home router via LAN cables
though, and can communicate through local IP... so net console sounds like a
good idea, but I've never heard of it before so I'll have to look this up.
Your sysrq suggestion seems to have worked! I first did this:
echo 1 > /proc/sys/kernel/sysrq
Then I pressed 'Alt + PrintScreen + H'. Now dmesg shows me:
[265102.938475] sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c)
terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i)
thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l)
show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p)
show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V)
show-blocked-tasks(w) dump-ftrace-buffer(z)
I assume that after the crash, I should first use it to test REISUB?
And here is the output of the kernel features you said to check. If they're not
there, I'm out of luck on this one, as I don't know how to compile my own
kernel and can't risk breaking my machine with dangerous tests.
mircea@linux-qz0r:~> zgrep CONFIG_NETCONSOLE /proc/config.gz
CONFIG_NETCONSOLE=m
CONFIG_NETCONSOLE_DYNAMIC=y
mircea@linux-qz0r:~> zgrep SERIAL_8250_CONSOLE /proc/config.gz
CONFIG_SERIAL_8250_CONSOLE=y
Lastly I'll try glxgears without vsync for a few hours in the next days: I have
to leave my computer locked while I'm away from home or sleeping, but can leave
it on for roughly 3 hours of the day while I'm around but AFK. I should note
that I tried running Xonotic without vsync, and that seems to have made
absolutely no difference. Also this likely isn't network related, I always test
in a local match with bots and not online multiplayer.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3477 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
next prev parent reply other threads:[~2018-04-17 20:06 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-105425-502@http.bugs.freedesktop.org/>
2018-03-13 10:38 ` [Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370) bugzilla-daemon
2018-03-25 21:21 ` bugzilla-daemon
2018-03-28 0:20 ` bugzilla-daemon
2018-03-28 23:03 ` bugzilla-daemon
2018-03-30 1:49 ` bugzilla-daemon
2018-04-01 19:53 ` bugzilla-daemon
2018-04-01 23:11 ` bugzilla-daemon
2018-04-02 9:33 ` bugzilla-daemon
2018-04-02 12:15 ` bugzilla-daemon
2018-04-04 1:06 ` bugzilla-daemon
2018-04-04 17:36 ` bugzilla-daemon
2018-04-08 22:47 ` bugzilla-daemon
2018-04-09 19:43 ` bugzilla-daemon
2018-04-09 20:16 ` bugzilla-daemon
2018-04-09 20:22 ` bugzilla-daemon
2018-04-10 9:13 ` bugzilla-daemon
2018-04-10 11:55 ` bugzilla-daemon
2018-04-12 13:55 ` bugzilla-daemon
2018-04-12 13:56 ` bugzilla-daemon
2018-04-12 13:57 ` bugzilla-daemon
2018-04-12 15:42 ` bugzilla-daemon
2018-04-12 17:02 ` bugzilla-daemon
2018-04-12 17:14 ` bugzilla-daemon
2018-04-13 19:39 ` bugzilla-daemon
2018-04-14 18:41 ` bugzilla-daemon
2018-04-17 9:27 ` bugzilla-daemon
2018-04-17 13:58 ` bugzilla-daemon
2018-04-17 19:10 ` bugzilla-daemon
2018-04-17 20:06 ` bugzilla-daemon [this message]
2018-04-18 21:51 ` bugzilla-daemon
2018-04-18 22:43 ` bugzilla-daemon
2018-04-20 14:32 ` bugzilla-daemon
2018-04-20 14:34 ` bugzilla-daemon
2018-04-20 14:34 ` bugzilla-daemon
2018-04-21 11:46 ` bugzilla-daemon
2018-04-24 12:08 ` bugzilla-daemon
2018-04-24 12:13 ` bugzilla-daemon
2018-04-24 12:15 ` bugzilla-daemon
2018-04-24 16:26 ` bugzilla-daemon
2018-04-24 18:34 ` bugzilla-daemon
2018-04-24 19:23 ` bugzilla-daemon
2018-04-24 20:14 ` bugzilla-daemon
2018-04-24 20:25 ` bugzilla-daemon
2018-04-24 20:29 ` bugzilla-daemon
2018-04-25 10:03 ` bugzilla-daemon
2018-04-25 15:28 ` bugzilla-daemon
2018-04-26 0:51 ` bugzilla-daemon
2018-04-26 1:10 ` bugzilla-daemon
2018-04-26 15:23 ` bugzilla-daemon
2018-04-26 20:19 ` bugzilla-daemon
2018-04-29 19:41 ` bugzilla-daemon
2018-04-29 21:37 ` bugzilla-daemon
2018-04-30 11:50 ` bugzilla-daemon
2018-04-30 12:07 ` bugzilla-daemon
2018-04-30 20:59 ` bugzilla-daemon
2018-04-30 21:41 ` bugzilla-daemon
2018-05-01 0:03 ` bugzilla-daemon
2018-05-01 21:06 ` bugzilla-daemon
2018-05-02 0:29 ` bugzilla-daemon
2018-05-02 1:21 ` bugzilla-daemon
2018-05-02 2:55 ` bugzilla-daemon
2018-05-02 9:59 ` bugzilla-daemon
2018-05-02 20:35 ` bugzilla-daemon
2018-05-05 14:24 ` bugzilla-daemon
2018-05-12 22:42 ` bugzilla-daemon
2018-05-29 13:01 ` bugzilla-daemon
2018-05-30 11:36 ` bugzilla-daemon
2018-05-30 12:12 ` bugzilla-daemon
2018-05-30 13:32 ` bugzilla-daemon
2018-05-31 13:00 ` bugzilla-daemon
2018-05-31 21:07 ` bugzilla-daemon
2018-09-01 19:48 ` bugzilla-daemon
2018-12-08 14:53 ` 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-105425-502-Sb6jvb4bLg@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).