All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110701] GPU faults in in Unigine Valley 1.0
Date: Fri, 17 May 2019 11:58:27 +0000	[thread overview]
Message-ID: <bug-110701-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 110701
           Summary: GPU faults in in Unigine Valley 1.0
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: eero.t.tamminen@intel.com
        QA Contact: dri-devel@lists.freedesktop.org

Setup:
- FullHD monitor (through HDMI KVM)
- HadesCanyon KBL i7-8809G ([AMD/ATI] Vega [Radeon RX Vega M] (rev c0))
- Ubuntu 18.04
- drm-tip git kernel v5.1
- Last VegaM firmware from kernel git
- X server git version
- Unigine Valley 1.0
- Mesa:
OpenGL renderer string: AMD VEGAM (DRM 3.32.0, 5.1.0, LLVM 7.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.2.0-devel
(git-d65b160e6a)

Test-cases:
* Several runs of:
  bin/valley_x64 -project_name Valley -data_path ../ -engine_config
../data/valley_1.0.cfg -system_script valley/unigine.cpp -video_app opengl
-sound_app null -video_mode -1 -video_fullscreen 1 -video_multisample 0
-video_width 1920 -video_height 1080 -extern_define
,BENCHMARK,RELEASE,LANGUAGE_EN,QUALITY_HIGH 

Expected outcome:
* No GPU issues (same as earlier, e.g. with yesterday's Mesa a9cef4f0e5)

Actual outcome:
* On last of 3 runs:
-----------------------------------------------
[  451.020091] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0b618802 for
process valley_x64 pid 2048 thread valley_x64:cs0 pid 2066
[  451.020093] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00044F6C
[  451.020093] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x06188002
[  451.020095] amdgpu 0000:01:00.0: VM fault (0x02, vmid 3, pasid 32772) at
page 282476, read from 'TC0' (0x54433000) (392)
[  451.020101] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0b610402 for
process valley_x64 pid 2048 thread valley_x64:cs0 pid 2066
[  451.020102] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000000
[  451.020102] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0608400C
[  451.020103] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 3, pasid 32772) at
page 0, read from 'TC5' (0x54433500) (132)
[  451.020109] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0b698402 for
process valley_x64 pid 2048 thread valley_x64:cs0 pid 2066
[  451.020110] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000002
[  451.020110] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0618800C
[  451.020111] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 3, pasid 32772) at
page 2, read from 'TC0' (0x54433000) (392)
[  451.020468] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0ac90802 for
process valley_x64 pid 2048 thread valley_x64:cs0 pid 2066
[  451.020469] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000000
[  451.020470] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x06104002
[  451.020471] amdgpu 0000:01:00.0: VM fault (0x02, vmid 3, pasid 32772) at
page 0, read from 'TC3' (0x54433300) (260)
[  451.020476] amdgpu 0000:01:00.0: GPU fault detected: 147 0x00108402 for
process valley_x64 pid 2048 thread valley_x64:cs0 pid 2066
[  451.020477] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00046DD2
[  451.020477] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x06088002
[  451.020478] amdgpu 0000:01:00.0: VM fault (0x02, vmid 3, pasid 32772) at
page 290258, read from 'TC4' (0x54433400) (136)
[  451.020484] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0ad90402 for
process valley_x64 pid 2048 thread valley_x64:cs0 pid 2066
[  451.020484] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x000460A8
[  451.020485] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x06008002
[  451.020486] amdgpu 0000:01:00.0: VM fault (0x02, vmid 3, pasid 32772) at
page 286888, read from 'TC6' (0x54433600) (8)
[  451.020491] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0c380402 for
process valley_x64 pid 2048 thread valley_x64:cs0 pid 2066
[  451.020492] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00046A0F
[  451.020493] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x06104002
[  451.020494] amdgpu 0000:01:00.0: VM fault (0x02, vmid 3, pasid 32772) at
page 289295, read from 'TC3' (0x54433300) (260)
[  451.020499] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0ac98402 for
process valley_x64 pid 2048 thread valley_x64:cs0 pid 2066
[  451.020500] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00045EAA
[  451.020500] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x06108002
[  451.020501] amdgpu 0000:01:00.0: VM fault (0x02, vmid 3, pasid 32772) at
page 286378, read from 'TC2' (0x54433200) (264)
[  451.020507] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0ed88802 for
process valley_x64 pid 2048 thread valley_x64:cs0 pid 2066
[  451.020507] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x000454BD
[  451.020508] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x06108002
[  451.020509] amdgpu 0000:01:00.0: VM fault (0x02, vmid 3, pasid 32772) at
page 283837, read from 'TC2' (0x54433200) (264)
[  451.020514] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0be80402 for
process valley_x64 pid 2048 thread valley_x64:cs0 pid 2066
[  451.020515] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x0004732D
[  451.020516] amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x06088002
[  451.020516] amdgpu 0000:01:00.0: VM fault (0x02, vmid 3, pasid 32772) at
page 291629, read from 'TC4' (0x54433400) (136)
[  451.025291] amdgpu 0000:01:00.0: IH ring buffer overflow (0x0008D420,
0x00006CE0, 0x0000D430)
[  451.521948] [drm] Fence fallback timer expired on ring sdma0
-----------------------------------------------

This is only time I've seen this so far -> it's possible that it requires
specific Mesa & kernel version.

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

[-- Attachment #1.2: Type: text/html, Size: 7587 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-05-17 11:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17 11:58 bugzilla-daemon [this message]
2019-05-18  0:22 ` [Bug 110701] GPU faults in in Unigine Valley 1.0 bugzilla-daemon
2019-05-18  0:37 ` bugzilla-daemon
2019-05-18  1:48 ` bugzilla-daemon
2019-05-18  3:33 ` bugzilla-daemon
2019-05-18  3:53 ` bugzilla-daemon
2019-05-18 11:43 ` bugzilla-daemon
2019-05-19  4:15 ` bugzilla-daemon
2019-05-19  9:50 ` bugzilla-daemon
2019-05-19 10:19 ` bugzilla-daemon
2019-05-19 15:52 ` bugzilla-daemon
2019-05-19 17:48 ` bugzilla-daemon
2019-05-19 23:19 ` bugzilla-daemon
2019-05-19 23:30 ` bugzilla-daemon
2019-05-20  0:24 ` bugzilla-daemon
2019-05-20  0:27 ` bugzilla-daemon
2019-05-20  3:20 ` bugzilla-daemon
2019-05-20  3:38 ` bugzilla-daemon
2019-05-20  3:46 ` bugzilla-daemon
2019-05-20 13:48 ` bugzilla-daemon
2019-05-21  7:08 ` bugzilla-daemon
2019-05-21  9:44 ` bugzilla-daemon
2019-05-21 18:36 ` bugzilla-daemon
2019-05-21 21:38 ` bugzilla-daemon
2019-05-21 23:19 ` bugzilla-daemon
2019-05-22  0:19 ` bugzilla-daemon
2019-05-23 20:01 ` bugzilla-daemon
2019-05-24  0:08 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-110701-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.