dri-devel Archive on 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: Sat, 18 May 2019 01:48:02 +0000	[thread overview]
Message-ID: <bug-110701-502-fpXEpOwevY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110701-502@http.bugs.freedesktop.org/>


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

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

--- Comment #3 from Yury Zhuravlev <stalkerg@gmail.com> ---
Similar, after the update today I have the same errors even for KDE KWin. 
Looks like Marek something did.

Error:
[  240.649210] amdgpu 0000:1f:00.0: [gfxhub] no-retry page fault (src_id:0
ring:24 vmid:7 pasid:32769, for process systemsettings5 pid 12567 thread
systemsett:cs0 pid 12571)                                                       
[  240.649211] amdgpu 0000:1f:00.0:   in page starting at address
0x0000800100be6000 from 27
[  240.649212] amdgpu 0000:1f:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00701031
[  240.649215] amdgpu 0000:1f:00.0: [gfxhub] no-retry page fault (src_id:0
ring:24 vmid:7 pasid:32769, for process systemsettings5 pid 12567 thread
systemsett:cs0 pid 12571)                                                       
[  240.649216] amdgpu 0000:1f:00.0:   in page starting at address
0x0000800100bf3000 from 27
[  240.649217] amdgpu 0000:1f:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  240.649220] amdgpu 0000:1f:00.0: [gfxhub] no-retry page fault (src_id:0
ring:24 vmid:7 pasid:32769, for process systemsettings5 pid 12567 thread
systemsett:cs0 pid 12571)

and etc. 

My spec:
OpenGL renderer string: Radeon RX Vega (VEGA10, DRM 3.30.0, 5.1.0-gentoo, LLVM
9.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.2.0-devel
(git-28c2ce7105)

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

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

  parent reply	other threads:[~2019-05-18  1:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17 11:58 [Bug 110701] GPU faults in in Unigine Valley 1.0 bugzilla-daemon
2019-05-18  0:22 ` bugzilla-daemon
2019-05-18  0:37 ` bugzilla-daemon
2019-05-18  1:48 ` bugzilla-daemon [this message]
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-fpXEpOwevY@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox