From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 95261] R5 M330 GPU lockup with DPM + high power states Date: Wed, 04 May 2016 13:27:50 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0265615044==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id B61136E80C for ; Wed, 4 May 2016 13:27:50 +0000 (UTC) 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 --===============0265615044== Content-Type: multipart/alternative; boundary="14623684700.56d7206F.27906"; charset="UTF-8" --14623684700.56d7206F.27906 Date: Wed, 4 May 2016 13:27:50 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=95261 Bug ID: 95261 Summary: R5 M330 GPU lockup with DPM + high power states Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel@lists.freedesktop.org Reporter: andrzej.mendel@gmail.com Created attachment 123454 --> https://bugs.freedesktop.org/attachment.cgi?id=123454&action=edit /var/log/syslog at the moment of hangup (photo) System: Ubuntu 16.06 with Mesa git (padoka ppa) and kernel 4.6-rc6 GPU: Intel HD 5500 + AMD R5 M330 - all command below run with DRI_PRIME=1 I get GPU hangups, which result in freeze after a soft reset, whenever the load is high enough to push the GPU into higher power states. If I run, for example, glmark2, only the first frame gets rendered and then the GPU lockups. After ~30s system freezes with information about GPU soft reset as the last message in syslog (see attachment) If I run a non-GPU-intensive commands (say, glxgears with vsync), then the GPU stays in low power states and I do not get this hangup. If I force lower power states (echo battery > /sys/class/drm/card1/device/power_dpm_state), I don't get this hangup even with glmark2. If I force high power states (echo performance > /sys/class/drm/card1/device/power_dpm_state; echo high > /sys/class/drm/card1/device/power_dpm_force_performance_level; echo on > /sys/class/drm/card1/device/power/control) then I do not get the hangup as long as there is no activity at all on the GPU. A simple glxgears is enough to trigger a hangup in this situation. This bug is present since at least kernel 4.2. I would appreciate any info on how to debug this further and will provide more info if requested. -- You are receiving this mail because: You are the assignee for the bug. --14623684700.56d7206F.27906 Date: Wed, 4 May 2016 13:27:50 +0000 MIME-Version: 1.0 Content-Type: text/html
Bug ID 95261
Summary R5 M330 GPU lockup with DPM + high power states
Product DRI
Version DRI git
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component DRM/Radeon
Assignee dri-devel@lists.freedesktop.org
Reporter andrzej.mendel@gmail.com

Created attachment 123454 [details]
/var/log/syslog at the moment of hangup (photo)

System: Ubuntu 16.06 with Mesa git (padoka ppa) and kernel 4.6-rc6
GPU: Intel HD 5500 + AMD R5 M330 - all command below run with DRI_PRIME=1

I get GPU hangups, which result in freeze after a soft reset, whenever the load
is high enough to push the GPU into higher power states.

If I run, for example, glmark2, only the first frame gets rendered and then the
GPU lockups. After ~30s system freezes with information about GPU soft reset as
the last message in syslog (see attachment)

If I run a non-GPU-intensive commands (say, glxgears with vsync), then the GPU
stays in low power states and I do not get this hangup. If I force lower power
states (echo battery > /sys/class/drm/card1/device/power_dpm_state), I don't
get this hangup even with glmark2.

If I force high power states (echo performance >
/sys/class/drm/card1/device/power_dpm_state; echo high >
/sys/class/drm/card1/device/power_dpm_force_performance_level; echo on >
/sys/class/drm/card1/device/power/control) then I do not get the hangup as long
as there is no activity at all on the GPU. A simple glxgears is enough to
trigger a hangup in this situation.

This bug is present since at least kernel 4.2.

I would appreciate any info on how to debug this further and will provide more
info if requested.


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