From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 111819] When starting Atom, 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 19:11:24 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1344226137==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id B0F816EDF9 for ; Thu, 26 Sep 2019 19:11:24 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1344226137== Content-Type: multipart/alternative; boundary="15695250842.60B1C0e.22843" Content-Transfer-Encoding: 7bit --15695250842.60B1C0e.22843 Date: Thu, 26 Sep 2019 19:11:24 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D111819 --- Comment #8 from Dennis Schridde --- Running /var/lib/flatpak/app/io.atom.Atom/current/active/files/share/atom/a= tom (the binary started by .../bin/atom-real) will also lock up the system. I installed net-im/signal-desktop-bin-1.27.2::gentoo to my system, natively, using the package manager. Running /usr/sbin/signal-desktop does not lock = it up. Running /var/lib/flatpak/app/org.signal.Signal/current/active/files/Signal/signal-d= esktop also does not lock it up. Ignoring io.atom.Atom and concentrating on org.signal.Signal, I assume that something that Flatpak does to setup its namespaces and cgroups trips OpenG= L / Mesa and the Linux kernel's AMDGPU driver... The last kernel where I did not notice such lock ups was 5.1.4 (on the same Gentoo system). I did not use this machine since mid/end May until now, so= I did not run any kernels in between 5.1.4 and 5.3.1. --=20 You are receiving this mail because: You are the assignee for the bug.= --15695250842.60B1C0e.22843 Date: Thu, 26 Sep 2019 19:11:24 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 8 on bug 11181= 9 from Dennis Schridde 
Running /var/lib/flatpak/app/io.atom.Atom/current/active/files=
/share/atom/atom
(the binary started by .../bin/atom-real) will also lock up the system.

I installed net-im/signal-desktop-bin-1.27.2::gentoo to my system, natively,
using the package manager.  Running /usr/sbin/signal-desktop does not lock =
it
up.

Running
/var/lib/flatpak/app/org.signal.Signal/current/active/files/Signal/signal-d=
esktop
also does not lock it up.

Ignoring io.atom.Atom and concentrating on org.signal.Signal, I assume that
something that Flatpak does to setup its namespaces and cgroups trips OpenG=
L /
Mesa and the Linux kernel's AMDGPU driver...

The last kernel where I did not notice such lock ups was 5.1.4 (on the same
Gentoo system).  I did not use this machine since mid/end May until now, so=
 I
did not run any kernels in between 5.1.4 and 5.3.1.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15695250842.60B1C0e.22843-- --===============1344226137== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1344226137==--