[Bug 104481] GPU lockup Polaris 11 - AMD RX 460 and RX 550 on amd64 and on ARMv7 platforms while playing video

* [Bug 104481] GPU lockup Polaris 11 - AMD RX 460 and RX 550 on amd64 and on ARMv7 platforms while playing video
@ 2018-01-03 17:04 bugzilla-daemon
  2018-01-03 17:07 ` bugzilla-daemon
                   ` (8 more replies)
  0 siblings, 9 replies; 10+ messages in thread
From: bugzilla-daemon @ 2018-01-03 17:04 UTC (permalink / raw)
  To: dri-devel

[-- Attachment #1.1: Type: text/plain, Size: 3212 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104481

            Bug ID: 104481
           Summary: GPU lockup Polaris 11 - AMD RX 460 and RX 550 on amd64
                    and on ARMv7 platforms while playing video
           Product: Mesa
           Version: git
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: luis.p.mendes@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 136527
  --> https://bugs.freedesktop.org/attachment.cgi?id=136527&action=edit
dmesg and iomem data from lockup obtained with glretrace

I am getting GPU lockups while playing video on Kodi, but it also happened with
other applications that play video, while OpenGL seems to be stable.
The system seem to be more sensitive to VP9 encoded videos. The freeze happens
both on amd64 as well as on armv7l platforms.
I am also able to reproduce GPU hangs on amd64 while replaying a glretrace
obtained with kodi on arm platform.

The arm dmesg and traces show a clear GPU lockup, while amd64 dmesg isn't so
clear, but the user experience is just the same, complete graphical system
freeze, while machine is still working with ssh or remote connections.

Please find amd64 logs in attachments, including iomem, dmesg and gdb traces.

In both platforms I am using Ubuntu 17.10 with Mate desktop, and lightdm
session manager, with libdrm-2.4.89, mesa-17.4 at commit "radv: Implement
binning on GFX9." - 6a36bfc64d2096aa338958c4605f5fc6372c07b8 and kernel
https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.16 at commit
"drm/amdgpu: Correct the IB size of bo update mapping." -  
104bd2ca1124dfd9aa904d5f5a96253ef2b580f6.

Please note that the system was more stable a few weeks ago with drm-next-4.16
based on kernel 4.15-rc2, and a previous mesa version, I don't remember the
actual commits, but despite it was more stable, both on arm as well as on
amd64, both systems still crashed similarly, it just got more evident with
these new versions.

There are two distinct crash behaviours on amd64: the ones that I obtained
while playing a video with kodi on amd64 and those that I obtained on amd64 by
replaying an apitrace from the arm platform while playing a VP9 video with
kodi.

The first kind of crashes is detailed with logs
kodi-processes_and_backtraces.txt and kodi-amdgpu_lockup_dmesg_and_iomem.txt.
The second kind of crashes is detailed with logs
glretrace-processes_and_backtraces.txt and
glretrace-amdgpu_lockup_dmesg_and_iomem.txt.

For some strange reason the amd64 platform is complaining about polaris11
firmware files, but they are in /lib/firmware and they taken by cloning
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git. I
am using the same firmware files on armv7l and the same graphics card and it
doesn't complain with the firmware. 

I can also provide the apitrace trace file, but it takes around 1GB of data.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 5004 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

^ permalink raw reply	[flat|nested] 10+ messages in thread