From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370) Date: Tue, 17 Apr 2018 19:10:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1232204542==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 619CE6E1B6 for ; Tue, 17 Apr 2018 19:10:35 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1232204542== Content-Type: multipart/alternative; boundary="15239922350.3EDAa2Cbe.24682" Content-Transfer-Encoding: 7bit --15239922350.3EDAa2Cbe.24682 Date: Tue, 17 Apr 2018 19:10:35 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D105425 --- Comment #33 from iive@yahoo.com --- This doesn't sound good. The sshd dying indicates that the kernel or the CPU has hang. If there is G= PU shader hang this doesn't happen right away, it usually waits 10 seconds bef= ore attempting to reset the GPU and then panics. 1. When the system hangs, do you see LEDs on the keyboard flashing? When kernel panics this is how it signals it. You might need to wait for 10 seconds or minute... 2. It seems that OpenSuse disables "sysrq", google told me that=20 "You can enable it in YaST->Security and Users->Security Center and Hardening..." Alternatively you should be able to enable it with executing this as root: echo 1 > /proc/sys/kernel/sysrq Check if it works with "Alt+PrtScr+h", it should display help message in `dmesg` . 3. After you have sysrq working, try to reproduce the crash, (without apitrace). This is to check if sysrq is working at all during hang and if it does then hopefully getting a kernel panic message in the log. 4. If you cannot get crash messages in the logs/journal, then you might to = use `serial console` or `netconsole`. The Serial console is best option, if both computers have their own serial ports and you happen to have a serial cable to connect them. linux-source/Documentation/admin-guide/serial-console.rst Otherwise you might try network console logger, that sends UDP packets to t= he second computer. linux-source/Documentation/networking/netconsole.txt Setting up these might be tricky, as they might not even be compiled in the stock kernel. So if you need detailed instructions, at least check if they = are present as modules or built-in the kernel. zgrep CONFIG_NETCONSOLE /proc/config.gz zgrep SERIAL_8250_CONSOLE /proc/config.gz 5. Disable vsync and run `glxgears` for hours. Leave it to work through the night or something. I just want to know if your computer hangs with that simple 3D. vblank_mode=3D1 glxgears --- Let me be clear. I want to see the crash messages for only 2 reasons: - To see that there is a kernel crash. - To see if the crash is in the graphics stack. Since the `sshd` stops working, it might be network-card crash. (Multiplayer games, using network...) If the machine just hangs, without actual kernel crash... then it might be hardware problem, but not a graphic card, it might also be MB, CPU, PSU, RA= M, etc... --=20 You are receiving this mail because: You are the assignee for the bug.= --15239922350.3EDAa2Cbe.24682 Date: Tue, 17 Apr 2018 19:10:35 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 33 on bug 10542= 5 from iive@yahoo.com
This doesn't sound good.
The sshd dying indicates that the kernel or the CPU has hang. If there is G=
PU
shader hang this doesn't happen right away, it usually waits 10 seconds bef=
ore
attempting to reset the GPU and then panics.


1. When the system hangs, do you see LEDs on the keyboard flashing?
When kernel panics this is how it signals it. You might need to wait for 10
seconds or minute...

2. It seems that OpenSuse disables "sysrq", google told me that=20
"You can enable it in YaST->Security and Users->Security Center =
and
Hardening..."
Alternatively you should be able to enable it with executing this as root:
  echo 1 >  /proc/sys/kernel/sysrq

Check if it works with "Alt+PrtScr+h", it should display help mes=
sage in
`dmesg` .

3. After you have sysrq working, try to reproduce the crash, (without
apitrace).
This is to check if sysrq is working at all during hang and if it does then
hopefully getting a kernel panic message in the log.

4. If you cannot get crash messages in the logs/journal, then you might to =
use
`serial console` or `netconsole`.
The Serial console is best option, if both computers have their own serial
ports and you happen to have a serial cable to connect them.
    linux-source/Documentation/admin-guide/serial-console.rst

Otherwise you might try network console logger, that sends UDP packets to t=
he
second computer.
    linux-source/Documentation/networking/netconsole.txt

Setting up these might be tricky, as they might not even be compiled in the
stock kernel. So if you need detailed instructions, at least check if they =
are
present as modules or built-in the kernel.
    zgrep CONFIG_NETCONSOLE /proc/config.gz
    zgrep SERIAL_8250_CONSOLE /proc/config.gz

5. Disable vsync and run `glxgears` for hours. Leave it to work through the
night or something.
I just want to know if your computer hangs with that simple 3D.
    vblank_mode=3D1 glxgears

---

Let me be clear.
I want to see the crash messages for only 2 reasons:
 - To see that there is a kernel crash.
 - To see if the crash is in the graphics stack.

Since the `sshd` stops working, it might be network-card crash. (Multiplayer
games, using network...)

If the machine just hangs, without actual kernel crash... then it might be
hardware problem, but not a graphic card, it might also be MB, CPU, PSU, RA=
M,
etc...


You are receiving this mail because:
  • You are the assignee for the bug.
= --15239922350.3EDAa2Cbe.24682-- --===============1232204542== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1232204542==--