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: Wed, 02 May 2018 09:59:54 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1067462882==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 64DB46E553 for ; Wed, 2 May 2018 09:59:54 +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 --===============1067462882== Content-Type: multipart/alternative; boundary="15252551941.2C0FB2eEF.17889" Content-Transfer-Encoding: 7bit --15252551941.2C0FB2eEF.17889 Date: Wed, 2 May 2018 09:59:54 +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 #67 from iive@yahoo.com --- (In reply to MirceaKitsune from comment #63) > (In reply to iive from comment #62) >=20 > I booted my machine with the kernel parameter panic=3D30 as instructed. I= then > waited for over two minutes to see if there's any sign of movement. Nothi= ng > happened: The machine never reboots on its own after the freeze, I still > need to press the reset button on the computer case to restart it. As I suspected.=20 It just hangs. > I also noticed another detail worth noting: The keyboard NumLock led only > seems to turn off after I press a key on the keyboard post freeze. So let= 's > say the machine just crashed: I can wait a whole minute and the led is st= ill > on... then I press Control or Shift or any other key, and after roughly 3 > seconds, the led then turns off. This is always the last noticeable respo= nse > from the PC. Are you using USB keyboard plugged into USB port? Your motherboard does have PS/2 ports, see if you can use the one for keybo= ard. (Sometimes keyboards come with small dongle that lets you plug USB keyboard into PS/2 port). > Lastly I have something important to mention: Someone just replied to my > thread about this crash on the openSUSE forum, and confirmed they're gett= ing > the same issue! They even posted a screenshot showing the exact same > graphical garbage I'm noticing in various applications (colorful little > squares littering the screen). This might be the first time someone else = can > confirm the problem, which is very exciting news if the person will provi= de > us with more info. >=20 > https://forums.opensuse.org/showthread.php/525727-3D-engines-causing- > frequent-GPU-lockups?p=3D2864284#post2864284 At very least they does manage to get errors from the kernel driver before = the crash. You haven't seen such kind of errors, have you? Still, you can share the blender trace with them. See if it causes hang for them too. See if it hangs at the same place... > Also, to answer iive's last point which I forgot in the previous response= : I > have temperature monitors on my desktop, and one of the Xonotic freezes > happened just a second after I alt-tab switched back from checking it. All > fans and temperatures were perfectly fine during that test: The CPU was > around the typical 48=C2=B0C, whereas the GPU never exceeded 68=C2=B0C it= self. > Temperatures are most surely not an issue. Chipset temperature is different than CPU and GPU. The motherboard has a huge chips that connects the CPU with the RAM and the PCIE slots. The GB website says it has temperature sensor on the North Brid= ge and there seems to be a huge passive cooler with heat pipes on it. One lead= ing to a radiator on top of the MB, probably to use the PSU intake for cooling. `sensors` should display everything that is available, even if they are not libeled correctly. GB like to increase the voltage a bit on their hardware, so it is more stab= le when overclocked. This however means it also runs a bit hotter. (And you need to dust off the heat sinks once or twice per year. Unless you have special dust filters on the PC case intake vents.) --=20 You are receiving this mail because: You are the assignee for the bug.= --15252551941.2C0FB2eEF.17889 Date: Wed, 2 May 2018 09:59:54 +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 # 67 on bug 10542= 5 from iive@yahoo.com
(In reply to MirceaKitsune from comment #63)
> (In reply to iive from comment #62)
>=20
> I booted my machine with the kernel parameter panic=3D30 as instructed=
. I then
> waited for over two minutes to see if there's any sign of movement. No=
thing
> happened: The machine never reboots on its own after the freeze, I sti=
ll
> need to press the reset button on the computer case to restart it.

As I suspected.=20
It just hangs.

> I also noticed another detail worth noting: The =
keyboard NumLock led only
> seems to turn off after I press a key on the keyboard post freeze. So =
let's
> say the machine just crashed: I can wait a whole minute and the led is=
 still
> on... then I press Control or Shift or any other key, and after roughl=
y 3
> seconds, the led then turns off. This is always the last noticeable re=
sponse
> from the PC.

Are you using USB keyboard plugged into USB port?
Your motherboard does have PS/2 ports, see if you can use the one for keybo=
ard.
(Sometimes keyboards come with small dongle that lets you plug USB keyboard
into PS/2 port).

> Lastly I have something important to mention: So=
meone just replied to my
> thread about this crash on the openSUSE forum, and confirmed they're g=
etting
> the same issue! They even posted a screenshot showing the exact same
> graphical garbage I'm noticing in various applications (colorful little
> squares littering the screen). This might be the first time someone el=
se can
> confirm the problem, which is very exciting news if the person will pr=
ovide
> us with more info.
>=20
> https://forums.opensuse.org/showthread.php/525727-3D-engines-cau=
sing-
> frequent-GPU-lockups?p=3D2864284#post2864284

At very least they does manage to get errors from the kernel driver before =
the
crash. You haven't seen such kind of errors, have you?

Still, you can share the blender trace with them. See if it causes hang for
them too. See if it hangs at the same place...

> Also, to answer iive's last point which I forgot=
 in the previous response: I
> have temperature monitors on my desktop, and one of the Xonotic freezes
> happened just a second after I alt-tab switched back from checking it.=
 All
> fans and temperatures were perfectly fine during that test: The CPU was
> around the typical 48=C2=B0C, whereas the GPU never exceeded 68=C2=B0C=
 itself.
> Temperatures are most surely not an issue.

Chipset temperature is different than CPU and GPU.

The motherboard has a huge chips that connects the CPU with the RAM and the
PCIE slots. The GB website says it has temperature sensor on the North Brid=
ge
and there seems to be a huge passive cooler with heat pipes on it. One lead=
ing
to a radiator on top of the MB, probably to use the PSU intake for cooling.

`sensors` should display everything that is available, even if they are not
libeled correctly.

GB like to increase the voltage a bit on their hardware, so it is more stab=
le
when overclocked. This however means it also runs a bit hotter.
(And you need to dust off the heat sinks once or twice per year. Unless you
have special dust filters on the PC case intake vents.)


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