Attachment 145918 Details for Bug 111763 – Journal excerpt vega56 ring gfx timeout, then gpu reset

Journal excerpt vega56 ring gfx timeout, then gpu reset

journal-excerpt-amdgpu-ring-gfx-crash-1573267675.txt (text/plain), 4.58 KB, created by Ben Klein on 2019-11-09 02:54:53 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Ben Klein

Created: 2019-11-09 02:54:53 UTC

Size: 4.58 KB

patch

obsolete

>Nov 08 21:00:35 robo-triangulum gnome-shell[18528]: [19174:19209:1108/210035.527242:ERROR:ssl_client_socket_impl.cc(969)] handshake failed; returned -1, SSL error code 1, net_error -202
>Nov 08 21:00:39 robo-triangulum gnome-shell[18528]: [19174:19209:1108/210039.529227:ERROR:ssl_client_socket_impl.cc(969)] handshake failed; returned -1, SSL error code 1, net_error -202
>Nov 08 21:00:44 robo-triangulum kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
>Nov 08 21:00:49 robo-triangulum kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
>Nov 08 21:00:49 robo-triangulum kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=68232366, emitted seq=68232368
>Nov 08 21:00:49 robo-triangulum kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 2565 thread Xorg:cs0 pid 2569
>Nov 08 21:00:49 robo-triangulum kernel: amdgpu 0000:0c:00.0: GPU reset begin!
>Nov 08 21:00:49 robo-triangulum kernel: amdgpu 0000:0c:00.0: GPU BACO reset
>Nov 08 21:00:49 robo-triangulum kernel: amdgpu 0000:0c:00.0: GPU reset succeeded, trying to resume
>Nov 08 21:00:49 robo-triangulum kernel: [drm] PCIE GART of 512M enabled (table at 0x000000F400900000).
>Nov 08 21:00:49 robo-triangulum kernel: [drm] VRAM is lost due to GPU reset!
>Nov 08 21:00:49 robo-triangulum kernel: [drm] PSP is resuming...
>Nov 08 21:00:50 robo-triangulum kernel: [drm] reserve 0x400000 from 0xf401000000 for PSP TMR
>Nov 08 21:00:50 robo-triangulum kernel: [drm] SADs count is: -2, don't need to read it
>Nov 08 21:00:51 robo-triangulum kernel: [drm] UVD and UVD ENC initialized successfully.
>Nov 08 21:00:51 robo-triangulum kernel: [drm] VCE initialized successfully.
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring gfx uses VM inv eng 0 on hub 0
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring sdma0 uses VM inv eng 0 on hub 1
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring page0 uses VM inv eng 1 on hub 1
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring sdma1 uses VM inv eng 4 on hub 1
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring page1 uses VM inv eng 5 on hub 1
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring uvd_0 uses VM inv eng 6 on hub 1
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on hub 1
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on hub 1
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring vce0 uses VM inv eng 9 on hub 1
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring vce1 uses VM inv eng 10 on hub 1
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: ring vce2 uses VM inv eng 11 on hub 1
>Nov 08 21:00:51 robo-triangulum kernel: [drm] ECC is not present.
>Nov 08 21:00:51 robo-triangulum kernel: [drm] SRAM ECC is not present.
>Nov 08 21:00:51 robo-triangulum kernel: [drm] recover vram bo from shadow start
>Nov 08 21:00:51 robo-triangulum gnome-shell[18528]: amdgpu: amdgpu_cs_query_fence_status failed.
>Nov 08 21:00:51 robo-triangulum gnome-shell[18528]: amdgpu: The CS has been cancelled because the context is lost.
>Nov 08 21:00:51 robo-triangulum kernel: [drm] recover vram bo from shadow done
>Nov 08 21:00:51 robo-triangulum kernel: [drm] Skip scheduling IBs!
>Nov 08 21:00:51 robo-triangulum kernel: [drm] Skip scheduling IBs!
>Nov 08 21:00:51 robo-triangulum kernel: amdgpu 0000:0c:00.0: GPU reset(2) succeeded!
>Nov 08 21:00:51 robo-triangulum kernel: [drm] Skip scheduling IBs!
>Nov 08 21:00:51 robo-triangulum kernel: [drm] Skip scheduling IBs!
>

Actions: View

Attachments on bug 111763: 145464 | 145465 | 145918

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.