Bug 106870 - [Raven Ridge occasionally hangs] VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Summary: [Raven Ridge occasionally hangs] VM_L2_PROTECTION_FAULT_STATUS:0x00000000
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2018-06-09 11:47 UTC by Luca
Modified: 2018-06-15 18:20 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Freeze before launching android emulator (265.79 KB, text/plain)
2018-06-09 11:47 UTC, Luca
no flags Details

Description Luca 2018-06-09 11:47:42 UTC
Created attachment 140109 [details]
Freeze before launching android emulator

X become unresponsive occasionally during the day, it usually happens before launching applications but it's not reproducible constantly, it also happens while browsing in Firefox. I have attached the log when it happened before launching the android emulator (amdgpu.vm_debug was set to true to show the stack trace). I can reboot the machine with a sysRq but everything graphical is freeze. Sometime it says gfxhub others mmhub.
Ubuntu 18.04, Kernel is 4.17 from the kernel-ppa, asrock ab350m pro4 updated to the latest test firmware with AGESA to see if it fixed the problem but still happens, mesa stack from the oibaf ppa, with padoka it seems the error appears less frequently and the error is usually silent and can only see this "[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=453604"
Comment 1 Michel Dänzer 2018-06-11 09:56:24 UTC
The attached dmesg looks like bug 106418.

Other than that, per https://bugs.freedesktop.org/show_bug.cgi?id=105251#c9 , try the latest microcode files from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu and make sure LLVM is version >= 6.
Comment 2 Luca 2018-06-12 19:19:18 UTC
I think they are the same bug but in the title it was mentioned it was occurring during boot and that is not my case although I have this problem at boot (https://bugs.freedesktop.org/show_bug.cgi?id=106225). I've updated the microcode to the latest version, llvm was already at version 6. It seems it happens again but more rarely, it happened now after 7 hours of uptime.
Comment 3 Luca 2018-06-15 18:20:07 UTC
I have updated the microcode for raven ridge, Mesa 18.0.5 and the microcode of the CPU also. I haven't had a problem in 2 days so I considered it solved.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.