All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105251] [Vega10]  GPU lockup on boot: VMC page fault
Date: Fri, 01 Jun 2018 17:31:30 +0000	[thread overview]
Message-ID: <bug-105251-502-jiT3x1H8OM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105251-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from dxxf@volny.cz ---
It seems I'm now affected by this bug too...

Hardware:
GPU: RX Vega 64 Liquid
CPU: Ryzen R7 1800X

Software:
OS: OpenSUSE Tumbleweed
Kernel: 4.17rc5 (from OpenSUSE Factory repos)
Mesa: 18.1.0 (from OpenSUSE Tumbleweed repos)

Kernel log - "journalctl -b -1 -r | grep amdgpu":
May 31 20:38:04 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, last signaled seq=2, last emitted seq=3
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:   at page 0x00000005000c0000 from
27
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0
ring:222 vmid:1 pasid:32768)
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:   at page 0x00000005000c0000 from
27
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0
ring:222 vmid:1 pasid:32768)
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:   at page 0x00000005000c0000 from
27
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0
ring:222 vmid:1 pasid:32768)
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:   at page 0x00000005000c0000 from
27
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0
ring:222 vmid:1 pasid:32768)
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:   at page 0x00000005000c0000 from
27
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0
ring:222 vmid:1 pasid:32768)
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:   at page 0x00000005000c0000 from
27
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0
ring:222 vmid:1 pasid:32768)
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:   at page 0x00000005000c0000 from
27
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0
ring:222 vmid:1 pasid:32768)
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:   at page 0x00000005000c0000 from
27
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0
ring:222 vmid:1 pasid:32768)
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00000000
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:   at page 0x00000005000c0000 from
27
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0
ring:222 vmid:1 pasid:32768)
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x001013BD
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0:   at page 0x00000005000c0000 from
27
May 31 20:37:54 kernel: amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0
ring:222 vmid:1 pasid:32768)
May 31 20:35:48 kernel: [drm] Initialized amdgpu 3.25.0 20150101 for
0000:0d:00.0 on minor 0
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 17(vce2) uses VM inv eng 11
on hub 1
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 16(vce1) uses VM inv eng 10
on hub 1
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 15(vce0) uses VM inv eng 9 on
hub 1
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 14(uvd_enc1) uses VM inv eng
8 on hub 1
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 13(uvd_enc0) uses VM inv eng
7 on hub 1
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 12(uvd) uses VM inv eng 6 on
hub 1
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 11(sdma1) uses VM inv eng 5
on hub 1
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 10(sdma0) uses VM inv eng 4
on hub 1
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 9(kiq_2.1.0) uses VM inv eng
13 on hub 0
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 8(comp_1.3.1) uses VM inv eng
12 on hub 0
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 7(comp_1.2.1) uses VM inv eng
11 on hub 0
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 6(comp_1.1.1) uses VM inv eng
10 on hub 0
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 5(comp_1.0.1) uses VM inv eng
9 on hub 0
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 4(comp_1.3.0) uses VM inv eng
8 on hub 0
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 3(comp_1.2.0) uses VM inv eng
7 on hub 0
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 2(comp_1.1.0) uses VM inv eng
6 on hub 0
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 1(comp_1.0.0) uses VM inv eng
5 on hub 0
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: ring 0(gfx) uses VM inv eng 4 on
hub 0
May 31 20:35:48 kernel: amdgpu 0000:0d:00.0: fb0: amdgpudrmfb frame buffer
device
May 31 20:35:48 kernel: fbcon: amdgpudrmfb (fb0) is primary device
May 31 20:35:47 kernel: [drm] amdgpu: 8176M of GTT memory ready.
May 31 20:35:47 kernel: [drm] amdgpu: 8176M of VRAM memory ready
May 31 20:35:47 kernel: amdgpu 0000:0d:00.0: GTT: 512M 0x000000F600000000 -
0x000000F61FFFFFFF
May 31 20:35:47 kernel: amdgpu 0000:0d:00.0: VRAM: 8176M 0x000000F400000000 -
0x000000F5FEFFFFFF (8176M used)
May 31 20:35:47 kernel: [drm] add ip block number 6 <gfx_v9_0>
May 31 20:35:47 kernel: amdgpu 0000:0d:00.0: enabling device (0006 -> 0007)
May 31 20:35:47 kernel: fb: switching to amdgpudrmfb from EFI VGA
May 31 20:35:47 kernel: [drm] amdgpu kernel modesetting enabled.

VMC Page faults are now in the log always, but "amdgpu_job_timeout" is 
persistent:
May 31 20:38:04 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, last signaled seq=2, last emitted seq=3

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

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

  parent reply	other threads:[~2018-06-01 17:31 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  9:39 [Bug 105251] [Vega10] GPU lockup on boot: VMC page fault bugzilla-daemon
2018-04-28  6:10 ` bugzilla-daemon
2018-04-29 13:29 ` bugzilla-daemon
2018-04-29 13:54 ` bugzilla-daemon
2018-05-24  5:24 ` bugzilla-daemon
2018-05-25 14:22 ` bugzilla-daemon
2018-06-01 17:31 ` bugzilla-daemon [this message]
2018-06-04 14:00 ` bugzilla-daemon
2018-06-04 17:52 ` bugzilla-daemon
2018-06-04 18:39 ` bugzilla-daemon
2018-06-05  8:50 ` bugzilla-daemon
2018-07-15 22:44 ` bugzilla-daemon
2018-07-15 22:56 ` bugzilla-daemon
2018-07-15 23:09 ` bugzilla-daemon
2018-07-16 15:13 ` bugzilla-daemon
2018-08-08 23:40 ` bugzilla-daemon
2018-08-14 19:19 ` bugzilla-daemon
2018-08-20  6:30 ` bugzilla-daemon
2018-08-20 15:13 ` bugzilla-daemon
2018-08-21  8:46 ` bugzilla-daemon
2018-08-21  8:48 ` bugzilla-daemon
2018-08-21 14:56 ` bugzilla-daemon
2018-08-21 15:12 ` bugzilla-daemon
2018-08-22 20:21 ` bugzilla-daemon
2018-08-24 14:11 ` bugzilla-daemon
2018-08-24 14:12 ` bugzilla-daemon
2018-08-24 14:24 ` bugzilla-daemon
2018-08-24 16:39 ` bugzilla-daemon
2018-08-24 19:35 ` bugzilla-daemon
2018-08-24 19:37 ` bugzilla-daemon
2018-08-25  2:48 ` bugzilla-daemon
2018-08-25  2:49 ` bugzilla-daemon
2018-08-25  5:59 ` bugzilla-daemon
2018-08-25  9:09 ` bugzilla-daemon
2018-08-27 16:12 ` bugzilla-daemon
2018-08-27 17:19 ` bugzilla-daemon
2018-08-27 23:14 ` bugzilla-daemon
2018-08-28 19:10 ` bugzilla-daemon
2018-08-28 19:20 ` bugzilla-daemon
2018-08-29  9:30 ` bugzilla-daemon
2018-08-29 14:32 ` bugzilla-daemon
2018-08-29 22:54 ` bugzilla-daemon
2018-08-30  1:37 ` bugzilla-daemon
2018-08-30  2:03 ` bugzilla-daemon
2018-08-30  2:41 ` bugzilla-daemon
2018-08-30 14:27 ` bugzilla-daemon
2018-08-30 14:33 ` bugzilla-daemon
2018-08-31 19:13 ` bugzilla-daemon
2018-09-03 13:26 ` bugzilla-daemon
2018-09-04 17:40 ` bugzilla-daemon
2018-09-06  4:07 ` bugzilla-daemon
2018-09-06  9:55 ` bugzilla-daemon
2018-09-11  8:36 ` bugzilla-daemon
2018-09-11 10:01 ` bugzilla-daemon
2018-09-12  3:26 ` bugzilla-daemon
2018-10-24  4:01 ` bugzilla-daemon
2018-10-24  8:38 ` bugzilla-daemon
2018-10-28 12:14 ` bugzilla-daemon
2018-10-28 23:19 ` bugzilla-daemon
2018-11-17 22:57 ` bugzilla-daemon
2018-11-18  1:13 ` bugzilla-daemon
2018-12-13  0:46 ` bugzilla-daemon
2018-12-13  9:05 ` bugzilla-daemon
2018-12-18  1:56 ` bugzilla-daemon
2018-12-18  2:08 ` bugzilla-daemon
2019-02-19  1:47 ` bugzilla-daemon
2019-05-19  2:38 ` bugzilla-daemon
2019-05-21 14:01 ` bugzilla-daemon
2019-05-21 14:02 ` bugzilla-daemon
2019-07-03 11:08 ` bugzilla-daemon
2019-07-04 15:19 ` bugzilla-daemon
2019-07-20 17:05 ` bugzilla-daemon
2019-07-22  7:40 ` bugzilla-daemon
2019-07-22  8:29 ` bugzilla-daemon
2019-07-22 20:15 ` bugzilla-daemon
2019-07-22 20:56 ` bugzilla-daemon
2019-07-22 20:57 ` bugzilla-daemon
2019-07-22 21:03 ` bugzilla-daemon
2019-07-22 21:06 ` bugzilla-daemon
2019-07-26 18:52 ` bugzilla-daemon
2019-11-19  8:31 ` 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-105251-502-jiT3x1H8OM@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.