From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111819] When starting Signal or Steam via Flatpak: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32770, for process X pid 2148 thread X:cs0 pid 2151) in page starting at address 0x0000000107720000 from 27, VM_L2_PROTECTION_FAULT_STATUS:0x00101031
Date: Thu, 26 Sep 2019 06:18:07 +0000 [thread overview]
Message-ID: <bug-111819-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1828 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111819
Bug ID: 111819
Summary: When starting Signal or Steam via Flatpak: [gfxhub]
retry page fault (src_id:0 ring:0 vmid:1 pasid:32770,
for process X pid 2148 thread X:cs0 pid 2151) in page
starting at address 0x0000000107720000 from 27,
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: not set
Priority: not set
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: devurandom@gmx.net
Created attachment 145518
--> https://bugs.freedesktop.org/attachment.cgi?id=145518&action=edit
dmesg
My system runs fine until I try to start com.valvesoftware.Steam or
org.signal.Signal via Flatpak (org.zulip.Zulip works fine). Then the graphical
X screen locks up and does not react to input (key presses, mouse clicks)
anymore. Moving the mouse cursor is visible. I can move to another VT
(ctrl+alt+F2), log in and `flatpak kill ...` the offending application, switch
back to the first VT and the system is back to normal without any obvious
damage. In dmesg I will find a bunch of messages like these:
[ 204.449968] amdgpu 0000:0a:00.0: [gfxhub] retry page fault (src_id:0 ring:0
vmid:1 pasid:32770, for process X pid 2148 thread X:cs0 pid 2151)
[ 204.449977] amdgpu 0000:0a:00.0: in page starting at address
0x0000000107720000 from 27
[ 204.449982] amdgpu 0000:0a:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
Device 0000:0a:00.0 is an AMD Ryzen 5 2400G.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3342 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
next reply other threads:[~2019-09-26 6:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 6:18 bugzilla-daemon [this message]
2019-09-26 6:18 ` [Bug 111819] When starting Signal or Steam via Flatpak: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32770, for process X pid 2148 thread X:cs0 pid 2151) in page starting at address 0x0000000107720000 from 27, VM_L2_PROTECTION_FAULT_STATUS:0x00101031 bugzilla-daemon
2019-09-26 6:20 ` bugzilla-daemon
2019-09-26 6:21 ` bugzilla-daemon
2019-09-26 6:22 ` bugzilla-daemon
2019-09-26 6:23 ` bugzilla-daemon
2019-09-26 6:26 ` bugzilla-daemon
2019-09-26 18:26 ` [Bug 111819] When starting Atom, " bugzilla-daemon
2019-09-26 18:34 ` bugzilla-daemon
2019-09-26 18:51 ` bugzilla-daemon
2019-09-26 19:11 ` bugzilla-daemon
2019-09-28 3:23 ` [Bug 111819] Running apps via Flatpak with DRI device access: " bugzilla-daemon
2019-09-28 3:42 ` bugzilla-daemon
2019-11-19 9:55 ` 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-111819-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox