| Summary: | Bugs Bunny: Lost in Time | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | smoki <smoki00790> |
| Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Default DRI bug account <dri-devel> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 18.2 | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | mess on the screen | ||
|
Description
smoki
2018-12-27 16:19:07 UTC
Created attachment 142904 [details]
mess on the screen
This is how it looks like. Broken presentation image i would say, as trace shows it OK.
Link to the trace: https://www.dropbox.com/s/tk2i1j6ownzh4px/bugs-trace.7z Anyway, this replays fine here too. It is just when i run a game actually this mess came by. I tried to run game on a CPU by using software Mesa for Windows from here: http://fdossena.com/?p=mesa/index.frag With same version of software Mesa for Windows it also plays correctly. So no idea what this could be really :D So, software Mesa for Windows shows it correctly, while same version of software Mesa for Linux via LIBGL_ALWAYS_SOFTWARE=true show this garbage ;) I tried various MESA version overrides and R600_DEBUG variables like no2d, notiling and such to no avail, even tried to disable DRI3 with LIBGL_DRI3_DISABLE and nope - mess is still there. And BTW forgot to mention... on AMD proprietary OpenGL driver this is fine. Ah OK, that Mesa for Windows uses LLVM 6, while Debian Mesa uses LLVM 7... so could be an LLVM regression. But replaying of trace show it fine, so it isn't LLVM :D Got this old OpenGL game accelerated, by using gldirect: http://sourceforge.net/projects/gldirect/ That seems supports OpenGL 1.x to D3D9 just fine :) And then asking d3dadapter nine to play opengl game and everything looks fine this way. Well, this bug is still there since this is OpenGL game and should play on OpenGL driver fine. OK, found an variable that helped :) always_have_depth_buffer=true wine bugs.exe makes it showing up on screen normally. i am also getting same bug https://pathankottaxi.hatenablog.com/ https://pathankottaxi.in/pathankot-taxi-service/ These kind of bugs is usually due to app error (not requesting a depth buffer but still needing one, relying on the implementation to provide one anyway). Although in this case, I suppose wine could be involved too, maybe there's some pecularities when emulating wgl with glx. Seems unlikely to me though that the bug is in mesa code. OK, self variabled only in Mesa... closing then as worksforme. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.