JohnnyonFlame has quit [Read error: Connection reset by peer]
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #etnaviv
JohnnyonFlame has joined #etnaviv
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #etnaviv
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #etnaviv
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #etnaviv
Net147 has quit [Excess Flood]
Net147 has joined #etnaviv
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #etnaviv
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #etnaviv
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #etnaviv
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #etnaviv
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #etnaviv
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #etnaviv
kherbst has joined #etnaviv
_whitelogger has joined #etnaviv
pcercuei has joined #etnaviv
kherbst has quit [Ping timeout: 246 seconds]
kherbst has joined #etnaviv
kherbst has quit [Ping timeout: 246 seconds]
pcercuei has quit [Ping timeout: 245 seconds]
pcercuei has joined #etnaviv
kherbst has joined #etnaviv
\\server\share has joined #etnaviv
kherbst has quit [Quit: duh 🐧]
<marex>
austriancoder: hey, have you ever seen flickering artifacts on WL desktop shell with etnaviv ?
<marex>
mntmn: ^
pcercuei has quit [Ping timeout: 245 seconds]
<marex>
austriancoder: I sent you an email with the photo of the corruption, it happens after many hours of running the machine and then the Weston desktop shell has this reverse L-shaped black thing flickering every second frame
<marex>
oh, and the "notch" (the ____|-----) is not always the same, sometimes it is lower, sometimes higher
<marex>
it is not always in the middle of the screen
pcercuei has joined #etnaviv
pcercuei has quit [Ping timeout: 246 seconds]
<mntmn>
marex: what is wl desktop shell? but i've seen flickering artifacts often with etnaviv
<mntmn>
i have nothing reproducible though
<marex>
mntmn: oh ?
<marex>
mntmn: weston desktop shell
<marex>
mntmn: do you have any pictures of it ?
pcercuei has joined #etnaviv
berton has joined #etnaviv
berton has quit [Remote host closed the connection]
<mntmn>
marex: i only know the normal weston, is that the same thing?
<mntmn>
marex: i don't have pictures
<mntmn>
marex: but i have found on sway and especially gnome with some more extreme usage (i think last time with chromium-ozone) i would run into situations where it would get into a flickery mess state
<mntmn>
marex: also reproducible with plugging secondary display device out and in on sway i think
<mntmn>
marex: i meant chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
<mntmn>
but otoh my experience has been extremely stable in the last weeks, i'm using this imx8mq based laptop as my primary laptop all day without trouble
<marex>
mntmn: yes, the "normal weston" is the desktop-shell
<marex>
mntmn: what does "flickery mess" look like ?
<marex>
see email
<marex>
its as if one of the weston desktop buffers got corrupted
<mntmn>
seen
<mntmn>
hmm hard to say when it starts for me it can be all kinds of missing/non-updating rectangles
<marex>
mntmn: is that the failure you saw ?
<mntmn>
it doesn't look the same every time
<mntmn>
but it's always a double buffering kind of flicker, like one buffer goes out of sync or is not updated anymore
<marex>
mntmn: thats what it looks like in here too
<mntmn>
when i encounter it again i'll record it
<marex>
mntmn: well there is something obviously broken
<marex>
mntmn: and I suspect it might even trigger further corruption elsewhere
<marex>
which shouldn't happen on MMU-capable vivante GPUs, so it shouldnt happen even on your GPU
<marex>
on mine it might, the GCnano has MMU off
<marex>
hmmmm
<mntmn>
i am not using latest mesa because it wasn't stable for me, but i did so much fiddling in the last 2 weeks that i can't remember what exactly was wrong
<marex>
Im on 20.3.4
<mntmn>
oh i'm on 21.1.0
<marex>
Im afraid this is the context sharing issue all over again