(In reply to Shiverly from comment #0)
> [...] dmesg has errors. 

I only see messages about failing to allocate a larger BAR, which is harmless.


> I think this is either AMDGPU bug or something ryzen related (most likely
> not, because they manifest as sudden reboots, never as system freezes. And
> last bios update stopped them 2 months ago).

FWIW, Andres Rodriguez reported similar symptoms with a Ryzen system on IRC, and raising voltages / disabling Cool'n'Quiet / disabling C6 states fixed them for him.

> FWIW, Andres Rodriguez reported similar symptoms with a Ryzen system on IRC,
> and raising voltages / disabling Cool'n'Quiet / disabling C6 states fixed
> them for him.

I raised the memory and the core voltages specifically. The other voltages like SoC were left untouched.

(In reply to Andres Rodriguez from comment #2)
> > FWIW, Andres Rodriguez reported similar symptoms with a Ryzen system on IRC,
> > and raising voltages / disabling Cool'n'Quiet / disabling C6 states fixed
> > them for him.
> 
> I raised the memory and the core voltages specifically. The other voltages
> like SoC were left untouched.

I didn't have these symptoms in arch or ubuntu 16.04 LTS, only when using this driver/kernel combination (which is only one that keeps both monitors usable). Long compilation jobs don't cause system freezes either.

I got some logs. Maybe they are related (found them in journalctl)

Nov 15 20:09:06 tibu-pc kernel: gmc_v8_0_process_interrupt: 626 callbacks suppressed
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x01, vmid 5) at page 154068154, read from 'TC5' (0x54433500) (192)
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A0C0001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x092EE4BA
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x05d0c001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x02, vmid 5) at page 5545728, read from 'TC7' (0x54433700) (68)
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A044002
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00549F00
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x05d00001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x01, vmid 5) at page 154068154, read from 'TC0' (0x54433000) (8)
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A008001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x092EE4BA
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x05d00801
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x02, vmid 5) at page 5541638, read from 'TC9' (0x54433900) (136)
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A088002
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00548F06
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x06500001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x01, vmid 5) at page 154068170, read from 'TC0' (0x54433000) (8)
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A008001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x092EE4CA
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x06500801
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x02, vmid 5) at page 5541634, read from 'TC8' (0x54433800) (64)
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A040002
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00548F02
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x06504001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x01, vmid 5) at page 154068170, read from 'TC7' (0x54433700) (68)
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A044001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x092EE4CA
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x06504401
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x01, vmid 5) at page 154068170, read from 'TC2' (0x54433200) (0)
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A000001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x092EE4CA
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x06500001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x01, vmid 5) at page 154068171, read from 'TC7' (0x54433700) (68)
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A044001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x092EE4CB
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x06584401
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x01, vmid 5) at page 154068170, read from 'TC7' (0x54433700) (68)
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A044001
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x092EE4CA
Nov 15 20:08:20 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x06504401
Nov 15 20:08:20 tibu-pc kernel: gmc_v8_0_process_interrupt: 1830 callbacks suppressed
Nov 15 20:08:03 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x01, vmid 1) at page 154054911, read from 'TC5' (0x54433500) (192)
Nov 15 20:08:03 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020C0001
Nov 15 20:08:03 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x092EB0FF
Nov 15 20:08:03 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x07f8c001
Nov 15 20:08:03 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x01, vmid 1) at page 154054911, read from 'TC0' (0x54433000) (8)
Nov 15 20:08:03 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02008001
Nov 15 20:08:03 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x092EB0FF
Nov 15 20:08:03 tibu-pc kernel: amdgpu 0000:22:00.0: GPU fault detected: 147 0x07f80801
Nov 15 20:08:03 tibu-pc kernel: amdgpu 0000:22:00.0: VM fault (0x01, vmid 1) at page 154054911, read from 'TC11' (0x54433131) (128)
Nov 15 20:08:03 tibu-pc kernel: amdgpu 0000:22:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02080001

One way to get crash quickly is to play Overpass map in CS:GO in terrorist spawn. Textures near the stairs show corrupted, and system always hangs in first 5 minutes of gameplay. I think it's 3D related, because just using simple text editor or being in Ctrl-Alt-Fx terminal never hangs, but browser can cause hang but it's less quick to manifest than playing 3D game.

Created attachment 137005 [details]
Crash while playing Counter-Strike: Global Offensive

I think I'm running into the same issues. Attached is the kernel output while playing Counter-Strike: Global Offensive. It worked during the warmup, but froze in the first round, so I'd say about 3-5 minutes after starting the game.

I'm running an up-to-date Debian unstable with Linux 4.14.13 and Mesa 17.3.3.

Created attachment 137006 [details]
Errors while playing CS:GO, crash and reboot after opening VLC

Another crash pretty much right after the one from my previous comment. After rebooting the system to continue playing Counter-Strike: Global Offensive the errors kept coming, though the system did not freeze (note the timestamps in the error log).

After shutting down the game, I started VLC to watch a stream and the system froze immediately. After a short while (<5 minutes) I used Magic SysReq keys to reboot the system safely, which can also be seen in the log.

A possibly important detail: My system doesn't freeze entirely, only the graphics output does. Sound still works for a time, even voice chatting continues to work. However, all X output freezes (e.g. conky on desktop).

I haven't tried going to a virtual console, so do not know whether that still works.

I also had the same issue while playing Euro Truck Simulator 2, but it never happened while playing Dota 2. Given this, it seems like some illegal instruction is passed to the graphics driver. Would an ApiTrace help? If so, I can try to record one.

I was able to record an ApiTrace which shows the problem consistently. However, it's 2.5 gigabytes and contains personal information I'd rather not share on a public bugtracker -- I think a trace can only be truncated, removing stuff from the beginning messes up the OpenGL context?

I cannot switch to the virtual console when the freeze is triggered.

I also built radeonsi from current Mesa git (9b9a89cd795fda462a6ee898ef6e5135ca79d94e) but the problem persisted.

I get

[  133.978908] amdgpu 0000:09:00.0: GPU fault detected: 147 0x00198802
[  133.978911] amdgpu 0000:09:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00500003
[  133.978912] amdgpu 0000:09:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02188002
[  133.978914] amdgpu 0000:09:00.0: VM fault (0x02, vmid 1) at page 5242883, read from 'TC4' (0x54433400) (392)

or from another boot

[  204.841497] amdgpu 0000:09:00.0: GPU fault detected: 147 0x00188402
[  204.841501] amdgpu 0000:09:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00500003
[  204.841502] amdgpu 0000:09:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A084002
[  204.841504] amdgpu 0000:09:00.0: VM fault (0x02, vmid 5) at page 5242883, read from '' (0x00000000) (132)


When I try to launch steam. It never gets to draw any UI, the computer just freezes.
This happens with both 4.13(-ubuntu33) and 4.15.2 kernel with Mesa/LLVM from git (padoka).
When I reverted to Mesa 17.2.8 + LLVM 5.0.0 I could launch steam again.

The Vehicle Game demo seem to trigger this quite reliably for me:
https://wiki.unrealengine.com/Linux_Demos

Ok, the vm faults I see are caused by using Padoka ppa which currently has
https://cgit.freedesktop.org/mesa/mesa/commit/?id=847d0a393d7f0f967f39302900d5330f32b804c8
but not
https://reviews.llvm.org/D41663

That means it can't be the same as the original issue, and also that the solution for me is just to update to more recent versions. Sorry for the noise in this bug.

Ernst, I have also traced the error you have to usage of OpenCL in the Mesa clover driver on RX560 with LLVM upgraded from 5.0.1 to 6.0. What do you say is the solution? Is Mesa using intrinsics that are only in LLVM git? Or is that LLVM changeset you posted already in the release LLVM 6.0?

aceman: the problem was mismatching development snapshots, couldn't happen if you have any real releases in the mix.

I'm using Mesa git, but LLVM 6.0 release. Is that fine wrt. this mismatch?

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/258.