https://bugs.freedesktop.org/show_bug.cgi?id=92850
Michel Dänzer changed:
What|Removed |Added
Component|Drivers/Gallium/radeonsi|Mesa core
Assignee|dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #27 from bellamorte42 at gmail.com ---
Yep, that seems to work. It's odd that it's the only game I have that has that
problem with context mis-match in pipe_sampler_view_release(). Doing some
additional tests to make sure.
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #26 from haro41 at gmx.de ---
sorry made a typo:
append: --enable-debug CFLAGS=-O0 CXXFLAGS=-O0
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #25 from haro41 at gmx.de ---
@bellamorte42,
i am meanwhile able to run WT by the following workaround:
Do always a 'make clean' before autogen.sh configuring, to avoid some strange
results.
append --enable-debug CFLAGS=-O0
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #24 from bellamorte42 at gmail.com ---
MESA_GL_VERSION_OVERRIDE=4.1COMPAT no longer required to avoid a black screen.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
https://bugs.freedesktop.org/show_bug.cgi?id=92850
haro41 at gmx.de changed:
What|Removed |Added
CC||haro41 at gmx.de
--- Comment #23 from
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #22 from bellamorte42 at gmail.com ---
Oh, I caught an error in the terminal during the crash.
context mis-match in pipe_sampler_view_release()
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #21 from bellamorte42 at gmail.com ---
Created attachment 120184
--> https://bugs.freedesktop.org/attachment.cgi?id=120184=edit
backtrace latest git
Just compiled mesa again and generated a new backtrace. It looks the same to
me.
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #20 from bellamorte42 at gmail.com ---
This has been happening with every git version from mesa 11. I don't know if
this bug existed before then. I don't know if the backtraces are the same tbh.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #19 from Nicolai Hähnle ---
Those config options are fine. Which version of Mesa are you building (what
does git show say?)
Do you consistently get the same crash and backtrace even after doing a
complete rebuild of Mesa?
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #18 from bellamorte42 at gmail.com ---
This is the dmesg I'm getting when I replay the trace.
[Nov24 12:41] traps: apitrace[4460] general protection ip:443625
sp:7ffe34202140 error:0 in apitrace[40+66000]
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #17 from bellamorte42 at gmail.com ---
Well, here's what I'm building mesa with.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #16 from bellamorte42 at gmail.com ---
Created attachment 120092
--> https://bugs.freedesktop.org/attachment.cgi?id=120092=edit
build
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #15 from Nicolai Hähnle ---
When I run the trace, all I get is a black window with occasional flickers of
garbage drawn, and finally a clean exit at the end of the trace. I cannot
reproduce the crash you've experienced.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #14 from bellamorte42 at gmail.com ---
Link to apitrace
https://www.dropbox.com/s/wxoywdk1pa0el2p/aces.7.trace?dl=0
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #13 from Nicolai Hähnle ---
Thanks! The crash happens in the Gallium state-tracker, i.e.
hardware-independent code. About that apitrace: perhaps you can upload it
somewhere like Dropbox or Google Drive?
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=92850
bellamorte42 at gmail.com changed:
What|Removed |Added
Attachment #119564|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #11 from bellamorte42 at gmail.com ---
I rebuilt mesa as instructed (--enable-debug) and that's what I got.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #10 from bellamorte42 at gmail.com ---
Created attachment 119594
--> https://bugs.freedesktop.org/attachment.cgi?id=119594=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #9 from bellamorte42 at gmail.com ---
Created attachment 119593
--> https://bugs.freedesktop.org/attachment.cgi?id=119593=edit
glxinfo
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #8 from Nicolai Hähnle ---
higuita, thanks for the heads up!
bellamorte, the backtrace still has no debug symbols. Also, you're missing
glxinfo and dmesg outputs.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #7 from bellamorte42 at gmail.com ---
Where should I upload the full trace to?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #6 from bellamorte42 at gmail.com ---
Created attachment 119564
--> https://bugs.freedesktop.org/attachment.cgi?id=119564=edit
backtrace
Here's the backtrace.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #5 from bellamorte42 at gmail.com ---
I've tried both versions of the client and have been having the issue for a
while (before the new 64bit client was an option).
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #4 from higuita at gmx.net ---
i too play war thunder but i'm not having problems with radeon mesa support.
I'm using mesa 11.0.4 on a AMD A10 APU, on slackwre64-current (so it was recent
packages) and also using the 4.1COMPAT flag.
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #3 from Nicolai Hähnle ---
Backtrace: When running in gdb, enter the "bt" command after the crash. That
will give you the backtrace.
Debug symbols: If you compile Mesa yourself, I believe running the configure
script with
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #2 from bellamorte42 at gmail.com ---
Well, as I said apitrace didn't yield any error messages. I'm using mesa git
from a few days ago. I've used probably 5 versions of mesa git with similar
results. The 4.1COMPAT is required to
https://bugs.freedesktop.org/show_bug.cgi?id=92850
--- Comment #1 from Nicolai Hähnle ---
Hi, thanks for the report. Which version of Mesa are you using? Could you
please provide a backtrace with debug symbols installed?
I notice you're using a MESA_GL_VERSION_OVERRIDE. Might the crash be
https://bugs.freedesktop.org/show_bug.cgi?id=92850
Bug ID: 92850
Summary: Segfault loading War Thunder
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
29 matches
Mail list logo
