| Bug ID | 89015 |
|---|---|
| Summary | [radeonsi] unvanquished & nexuiz crash after switching AA |
| Product | Mesa |
| Version | git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | arek.rusi@gmail.com |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 113233 [details]
unvanquished.log
Without AA everything looks good. Atfer turn on antialliasing both games crash
with log:
EE r600_texture.c:326 r600_texture_get_fmask_info - Got error in surface_init
while allocating FMASK
and
"_name_of_process_":dri2.c:547: dri2_allocate_textures: Assertion
`drawable->msaa_textures[statt]' failed.
Created attachment 113234 [det=
ails]
nexuiz.log
sw:
linux:drm-next-3.20
mesa: git-d4a461c
llvm: r228386
xorg: 1.17.0 + modesetting instead radeon
hw:
capeverde
i've tried this with xf86-video-ati and it looks like the prob= lem is in modesetting ddx.=20 With radeon AA works fine.=20 Should i fill new bug in xorg/modesetting thread?
| What | Removed | Added |
|---|---|---|
| Component | Drivers/Gallium/radeonsi | Driver/modesetting |
| Assignee | dri-devel@lists.freedesktop.org | xorg-team@lists.x.org |
| Product | Mesa | xorg |
| QA Contact | dri-devel@lists.freedesktop.org | xorg-team@lists.x.org |
Please attach the output of glxinfo from using the modesetting= and radeon drivers.
| What | Removed | Added |
|---|---|---|
| Component | Driver/modesetting | Drivers/Gallium/radeonsi |
| Assignee | xorg-team@lists.x.org | dri-devel@lists.freedesktop.org |
| Product | xorg | Mesa |
| QA Contact | xorg-team@lists.x.org | dri-devel@lists.freedesktop.org |
Somebody needs to track down why radeon_surface_init returns a= non-0 value. I think it most likely comes from si_surface_sanity, but I'm not sure. For now, let's assume this is a radeonsi driver bug.
Please check your kernel version and if it is outdated test with at least 3.19 and rebuilded xf86-video-ati.
kernel 3.19 and xf86-video-ati current git version fixed similar problem for me.
Igor, i use 1-day old git/svn for mesa/llvm/kenel except for x=
f86-video-ati, i
don't use it at all. If your distribution use xorg-1.17.x you may try
xf86-video-modesetting. It would be really nice if you can. As I wrote befo=
re,
for xf86-video-ati the problem doesn't exist ...at least for me.
Could you tell which version of radeon ddx failed for unvanquished + AA.
Created attachment 113672 [details]
somewhere between mesa 10.2.x & 10.3
I've tested some tags of mesa with: llvm-3.5.1 & xorg 1.17.1+modesettin=
g &
drm_next.
1)mesa 10.2.9 - looks ok
2)mesa 10.3.(0,1)&10.4.4 - looks like a crap (see pic) but not fails (p=
lay
music, can screen shot, can escape with ALT+F4)
3)mesa dev-10.(5,6) - crashes
| What | Removed | Added |
|---|---|---|
| Attachment #113672 mime type | text/plain | image/png |
between stage 2&3 the winner is: 3da735cc4c478b0ab2ecc2164899cf9d77dc671a is the first bad commit commit 3da735cc4c478b0ab2ecc2164899cf9d77dc671a Author: Jason Ekstrand <= jason.ekstrand@intel.com> Date: Sat Aug 23 10:45:00 2014 -0700 main: Add a concept of an array format An array format is a 32-bit integer format identifier that can represent any format that can be represented as an array of standard GL datatypes. Whie the MESA_FORMAT enums provide several of these, they don't account= for all of them. v2 by Iago Toral Quiroga <i= toral@igalia.com>: - Implement mesa_array_format as a plain bitfiled uint32_t type instea= d of using a struct inside a union to access the various components packe= d in it. This is necessary to support bigendian properly, as pointed out = by Ian. - Squashed: Make float types normalized v3 by Iago Toral Quiroga <i= toral@igalia.com>: - Include compiler.h in formats.h, which is necessary to build in MSV= C as indicated by Brian Paul. Reviewed-by: Jason Ekstrand <jason@jlekstrand.net> :040000 040000 87f8588bd2eeda5fbf0669360f2ff66564c93a3c f2b353b9593f085e196f184a2d6ebee2e2194dea M src for stages 1&2... wip
and for 1->2 trigger is: 27c686309e035d211c7cf38d1c0902f1bf2886c5 is the first bad commit commit 27c686309e035d211c7cf38d1c0902f1bf2886c5 Author: Axel Davy <axel.davy@= ;ens.fr> Date: Wed Jun 18 23:27:30 2014 -0400 gallium: Add __DRIimageDriverExtension support to gallium __DRIimageDriverExtension is used by GLX DRI3 and Wayland. This patch is a rewrite of http://lists.freedesktop.org/archives/mesa-dev/2014-May/060318.htm= l and http://lists.freedesktop.org/archives/mesa-dev/2014-May/060317.htm= l Previous patches were: Signed-off-by: Ben Skeggs <bskeggs@redhat.com> Signed-off-by: Keith Packard <keithp@keithp.com> Signed-off-by: Axel Davy <ax= el.davy@ens.fr> Reviewed-by: Marek Ol=C5=A1=C3=A1k <marek.olsak@amd.com> Reviewed-by: Ben Skeggs <b= skeggs@redhat.com> Signed-off-by: Dave Airlie <airlied@redhat.com> :040000 040000 bed5212b498ec77bf272f1caa433442a3e897601 d1b1be3159255a47c2fa21e2ad0735798cbc78b7 M src
modesetting in dri2 mode is fine here :). Probably, but do you use xserver's modesetting driver in dri3 mode? There are whole bunch of piglit crashes and gpu lockups here with anything dri3 related - be it with xserver's modeseting or radeon ddx (i tried this patched radeon https://github.com/iXit/xf86-video-ati/commits/master and it suffer from the same issues like modesetting)
Is there any way to switch dri mode? As far i know xorg1.17+mo= desseting just uses dri3. There is no log with dmesg/xorg/systemd when dri3 is used.=20 So answer for your question is: so probably yes, but i don't know for sure.= =20 DDX from https://github= .com/iXit/xf86-video-ati/ has the same symptoms like modeseting but looks worse a lot (this is why i never like it)
I've just tried new mesa/master and it doesn't crash anymore. = Problem goes back to stage 2 (see pics), but: ----- EE r600_texture.c:326 r600_texture_get_fmask_info - Got error in surface_in= it while allocating FMASK. ----- is still present.=20 Probably is like smoki said, dri3 is problem here and if there's no official support for dri3, should we really care about it for now?
Apparently, MSAA doesn't work with DRI3. I think it's a bug in= st/dri.
This works fine for me in current ddx and mesa in DRI3 mode. Please recheck with current mesa.
This might have fixed this: http://cgit.freedesktop.org/mesa/mesa/commit/?= id=3D6611f65047575054a38ce83ebfe0331e39e1774f
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |
(In reply to smoki from comment #17) > This works fine for me in current ddx and mesa = in DRI3 mode. >=20 > Please recheck with current mesa. (In reply to Marek Ol=C5=A1=C3=A1k from comment #18) > This might have fixed this: > http://cgit.= freedesktop.org/mesa/mesa/commit/ > ?id=3D6611f65047575054a38ce83ebfe0331e39e1774f Closing.