From: boris.dekshteyn@gmail.com (Boris A. Dekshteyn)
To: 35575@debbugs.gnu.org
Subject: bug#35575: Some graphical programs borked with Guix on Arch
Date: Sun, 05 May 2019 22:33:53 +1200 [thread overview]
Message-ID: <87zho1dwby.fsf@gmail.com> (raw)
In-Reply-To: <c276ed96-e5a0-975d-7954-77b8831487c0@brendan.scot> (Brendan Tildesley's message of "Sun, 5 May 2019 17:58:13 +1000")
Hi,
Brendan Tildesley <mail@brendan.scot> writes:
> Any one have any clues on how to debug such a thing?
>
> https://brendan.scot/p/borked-godot.png
check dmesg for something like:
--8<---------------cut here---------------start------------->8---
[ 337.066640] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0000480c for process Xorg pid 845 thread Xorg:cs0 pid 846
[ 337.068114] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
[ 337.069354] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0404800C
[ 337.070674] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 2, pasid 32768) at page 0, read from 'TC0' (0x54433000) (72)
--8<---------------cut here---------------end--------------->8---
if you have something similar, try doing:
--8<---------------cut here---------------start------------->8---
rm -rf $HOME/.cache/mesa_shader_cache/
--8<---------------cut here---------------end--------------->8---
--
WBR, Boris Dekshteyn
next prev parent reply other threads:[~2019-05-05 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 7:58 bug#35575: Some graphical programs borked with Guix on Arch Brendan Tildesley
2019-05-05 10:33 ` Boris A. Dekshteyn [this message]
2019-05-07 11:09 ` Brendan Tildesley
2019-05-08 9:42 ` Boris A. Dekshteyn
2020-03-29 4:00 ` bug#35575: logo,Some " Brendan Tildesley
2020-03-31 14:53 ` Marius Bakke
2021-02-22 8:31 ` bug#35575: closing. bug has not reoccurred since Brendan Tildesley
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zho1dwby.fsf@gmail.com \
--to=boris.dekshteyn@gmail.com \
--cc=35575@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).