https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #17 from deltasquared ---
Apologies for being late to reply.
Having run mesa built from the MR branch, I have since been unable to get the
same crash when running minetest.
Certainly the apitrace capture can no longer bring my
https://bugs.freedesktop.org/show_bug.cgi?id=111231
Pierre-Eric Pelloux-Prayer changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #15 from Pierre-Eric Pelloux-Prayer
---
Could you test the branch from MR
https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1554 and let me know if
it fixes the issue for you?
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #14 from deltasquared ---
The apitrace no longer causes issues on my system either if I use
AMD_DEBUG=nodpbb . I also decided to try this on minetest and *so far* (bearing
in mind the issue was indetermistic in the first place, so a
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #13 from Pierre-Eric Pelloux-Prayer
---
Using AMD_DEBUG=nodpbb "fixes" the problem.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #12 from Pierre-Eric Pelloux-Prayer
---
Thanks for the bug report.
I could reproduce the bug using the provided apitrace, both on a Ryzen platform
and on a Vega Mobile laptop (can't reproduce on Navi).
Using MESA_DEBUG=flush or
https://bugs.freedesktop.org/show_bug.cgi?id=111231
Bas Nieuwenhuizen changed:
What|Removed |Added
QA Contact||dri-devel@lists.freedesktop
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #11 from deltasquared ---
Some additional information I had neglected to mention in the initial
description in the "excitement" of filing my first bug here...
Relevant hardware is as stated a ryzen 2200G running solely on
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #10 from deltasquared ---
Created attachment 144890
--> https://bugs.freedesktop.org/attachment.cgi?id=144890=edit
Observed graphical corruption - right hand side of monitor
Other side of above.
The sky colour is otherwise
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #9 from deltasquared ---
Created attachment 144889
--> https://bugs.freedesktop.org/attachment.cgi?id=144889=edit
Observed graphical corruption - left hand side of monitor
Taken in two photos as my screen's a rather large one.
https://bugs.freedesktop.org/show_bug.cgi?id=111231
deltasquared changed:
What|Removed |Added
Version|XOrg git|unspecified
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #8 from deltasquared ---
Created attachment 144888
--> https://bugs.freedesktop.org/attachment.cgi?id=144888=edit
dmesg output from boot to stopping dmesg when killing xorg was possible
In this case I was able to kill xorg and
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #7 from deltasquared ---
Created attachment 144887
--> https://bugs.freedesktop.org/attachment.cgi?id=144887=edit
dmesg log from boot to running apitrace replay on the above apitrace trace file
Notably there are a lot more
https://bugs.freedesktop.org/show_bug.cgi?id=111231
deltasquared changed:
What|Removed |Added
Attachment #144884|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=111231
deltasquared changed:
What|Removed |Added
Attachment #144883|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #4 from deltasquared ---
Oh dear, it seems I'm getting in a bit of a muddle with the attachments, please
bear with.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #3 from deltasquared ---
Created attachment 144884
--> https://bugs.freedesktop.org/attachment.cgi?id=144884=edit
apitrace replay --verbose --debug: stderr
stderr of the same as above.
I made them separate as it helped me to have
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #2 from deltasquared ---
Created attachment 144883
--> https://bugs.freedesktop.org/attachment.cgi?id=144883=edit
apitrace replay --verbose --debug: stdout
NB: stderr attached separately.
Note that it stops after a certain swap
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #1 from deltasquared ---
Created attachment 144882
--> https://bugs.freedesktop.org/attachment.cgi?id=144882=edit
API trace that can reliably cause GPU protection faults on a ryzen 2200G
The adformentioned "dodgy" apitrace trace
https://bugs.freedesktop.org/show_bug.cgi?id=111231
deltasquared changed:
What|Removed |Added
Summary|VM_L2_PROTECTION_FAULT when |random
|loading
20 matches
Mail list logo
