| Bug ID | 110721 |
|---|---|
| Summary | graphics corruption on steam client with mesa 19.1.0 rc3 on p= olaris |
| Product | Mesa |
| Version | unspecified |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | edisonalvarez@arnet.com.ar |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 144315 [details]<=
/span>
dmesg
it started happening with rc3.
Mesa compiled with llvm8
it happens both with the beta and stable channel.
https://i.imgur.com/7g2EK1G.png=
Opensuse 15.0
Kernel 4.19.42
Radeon rx460 4gb
I get similar corruption in Chromium and Visual Studio Code wi= th Mesa 19.1.0-rc3. There was no problem with 19.1.0-rc2. This is on Archlinux, kernel 5.1.3, the card is an RX480. I tried compiling Mesa with both LLVM 8 and 9 (r360929). It's very visible in Chromium when Chromium is started with parameters that enable its hardware acceleration: chromium \ --ignore-gpu-blacklist \ --enable-gpu-rasterization \ --enable-native-gpu-memory-buffers \ --enable-zero-copy \ --disable-gpu-driver-bug-workarounds
now the bug has hit 19.0.5. There is a fix for steam if you un= check "Enable Gpu accelarated rendering in web views"
| What | Removed | Added |
|---|---|---|
| Version | unspecified | 19.0 |
(In reply to alvarex from comment #2) > now the bug has hit 19.0.5. Are you saying the bug was not present in 19.0.4, but is now present in 19.= 0.5? If so, that's only 22 new commits, 10 if you exclude obvious non-candidates. If you can reliably test this, that's at most 5 build & test you need t= o do when bisecting mesa-19.0.4..mesa-19.0.5; could you do this please? It would greatly help figure out the cause :)
yes the bug was not present on 19.0.4. I'll give it a shot, I don't compile mesa from git in a standard way, I com= pile it on opensuse build service.
I need help, I build up mesa and set the git bisect good and b= ad commits, but steam does not start because it needs 32bits libs and I can't seem to build them. What option should I pass to meson or ninja to compile 32 bit? I can't trigger the bug on chrome, chrome or chromium do launch but the bug doesn't trigger . @Ropid what do you mean with Visual Studio Code? where should= I find that extension?
@alvarex: Try starting chromium with this command line here, it makes it show corrupt= ion everywhere for me here: chromium --ignore-gpu-blacklist --enable-gpu-rasterization --enable-native-gpu-memory-buffers --enable-zero-copy --disable-gpu-driver-bug-workarounds About Visual Studio Code, I see corruption when I click on the main menu and move the mouse around to open and close the different menus there.
(In reply to Ropid from comment #6) > @alvarex: >=20 > Try starting chromium with this command line here, it makes it show > corruption everywhere for me here: >=20 > chromium --ignore-gpu-blacklist --enable-gpu-rasterization > --enable-native-gpu-memory-buffers --enable-zero-copy > --disable-gpu-driver-bug-workarounds >=20 > About Visual Studio Code, I see corruption when I click on the main me= nu and > move the mouse around to open and close the different menus there. no the bug doesn't trigger with chromium unless this error has something to= do maybe chrome is not detecting the gpu (same as steam) > ac: Unknown GPU, using 0 for raster_config > [1:7:0522/132124.876161:ERROR:command_buffer_proxy_impl.cc(125)]=20 > ContextResult::kTransientFailure: Failed to send=20 > GpuChannelMsg_CreateCommandBuffer. > [31337:31346:0522/132131.668335:ERROR:browser_process_sub_thread.cc(21= 7)]=20 > Waited 322 ms for network service @Ropid what version of chromium are u using??
![https://i.imgur.com/7g2EK1G.png=](3D"https://i.imgur.com/7g2EK1G.png"){kind=link}
> (In reply to Ropid from comment #6)
> @alvarex:
>=20
> Try starting chromium with this command line here, it makes it show
> corruption everywhere for me here:
>=20
> chromium --ignore-gpu-blacklist --enable-gpu-rasterization
> --enable-native-gpu-memory-buffers --enable-zero-copy
> --disable-gpu-driver-bug-workarounds
>
Same here so I did a bisect.
There are 2 problematic commits, making the bisect a bit more complicated.
The first one has already been solved by d6053bf2a170.
The second one is 811fa9a79cf ("mesa: unreference current winsys buffe=
rs when
unbinding winsys buffers").=20
Using master + this commit reverted: no more corruption in chromium.
(In reply to Pierre-Eric Pelloux-Prayer from comment #9) > > (In reply to Ropid from comment #6) > > @alvarex: > >=20 > > Try starting chromium with this command line here, it makes it sh= ow > > corruption everywhere for me here: > >=20 > > chromium --ignore-gpu-blacklist --enable-gpu-rasterization > > --enable-native-gpu-memory-buffers --enable-zero-copy > > --disable-gpu-driver-bug-workarounds > >=20 >=20 > Same here so I did a bisect. > There are 2 problematic commits, making the bisect a bit more complica= ted. >=20 > The first one has already been solved by d6053bf2a170. > The second one is 811fa9a79cf ("mesa: unreference current winsys = buffers > when unbinding winsys buffers").=20 >=20 > Using master + this commit reverted: no more corruption in chromium. for me it doesn't happen on chrome with 64 bits libs, (I couldn't compile 32bits) I tried several versions of chrome, but not that precise one. not s= ure if it is the same bug. what version of chrome does steam use?
> The second one is 811fa9a79cf ("mesa: unref=
erence current winsys buffers
> when unbinding winsys buffers").=20
>
I'm going to try reverting that commit and building anyway.(In reply to alv=
arex
| What | Removed | Added |
|---|---|---|
| Resolution | --- | FIXED |
| Status | NEW | RESOLVED |
| What | Removed | Added |
|---|---|---|
| Status | RESOLVED | VERIFIED |
| What | Removed | Added |
|---|---|---|
| Status | VERIFIED | REOPENED |
| Resolution | FIXED | --- |
That bug was affecting Discord, Brave and Chromium. Fixed by reverting : 811fa9a79cf
| What | Removed | Added |
|---|---|---|
| CC | 0xe2.0x9a.0x9b@gmail.com |
*** Bug 110736 has been marked as a du= plicate of this bug. ***
>=20
> Using master + this commit reverted: no more corruption in chromium.
I reverted the commit on 19.1.0 rc3 and it works as well.
I confirm that reverting "mesa: unreference current winsy= s buffers when unbinding winsys buffers" fixes the rendering issues in Spotify and Vi= sual Studio Code. Thanks.
19.0.5 also completely broke Blender 2.8 for me, which now cra= shes whenever I select any geometry in edit more. 19.0.4 was fine. Can confirm that building master & reverting "mesa: unreference cu= rrent winsys buffers when unbinding winsys buffers" fixes the issues for me -- both= with Blender crashing as well as the previously mentioned render glitches in Chromium & Electron based programs.
*** Bug 110759 has been marked as a du= plicate of this bug. ***