alyssa changed the topic of #panfrost to: Panfrost - FLOSS Mali Midgard & Bifrost - Logs https://freenode.irclog.whitequark.org/panfrost - <daniels> avoiding X is a huge feature
anarsoul has joined #panfrost
icecream95 has quit [Ping timeout: 260 seconds]
icecream95 has joined #panfrost
NeuroScr has quit [Quit: NeuroScr]
_whitelogger has joined #panfrost
jolan has quit [Quit: leaving]
jolan has joined #panfrost
vstehle has quit [Ping timeout: 260 seconds]
BenG83 has joined #panfrost
<HdkR> alyssa: It's also only a tiny amoutn of code. Not much logic happening there
<HdkR> Only spent about an hour or so getting familiar with the code again
BenG83 has quit [Quit: Leaving]
megi has quit [Ping timeout: 260 seconds]
cowsay_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
cowsay has joined #panfrost
davidlt has joined #panfrost
<tomeu> leinax: that file isn't accessible any more
<tomeu> leinax: is it BOs, or malloced stuff from within Mesa?
<tomeu> icecream95: haven't seen any, is that easily reproducible with rtcwake?
vstehle has joined #panfrost
guillaume_g has joined #panfrost
<icecream95> tomeu: It seems less of a "5% of the time it doesn't work" problem and more that it works fine
<icecream95> for a while, then something trips and suspend doesn't work until I reinsert the panfrost module.
<icecream95> Maybe just restarting Sway would fix it, but I haven't tried that yet.
<tomeu> icecream95: can it be reproduced with a script that repeatedly calls rtcwake?
<icecream95> I don't think it can
<icecream95> Maybe I should make a script than runs rtcwake for three seconds every five minutes, so I can see what
<icecream95> I was doing when it breaks...
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #panfrost
<icecream95> Running glmark2-es2 -b refract in the background can trigger it, but I'm not sure if it's the same cause
yann|work has quit [Ping timeout: 268 seconds]
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #panfrost
icecream95 has quit [Ping timeout: 258 seconds]
pH5 has joined #panfrost
<tomeu> refract with rtcwake being repeatedly called?
yann|work has joined #panfrost
raster has joined #panfrost
<robmur01> tomeu: I'd guess either something gets wedged such that panfrost_job_is_idle() returns a false positive, or system suspend really goes quickly enough that the last job is still running
<robmur01> we might need to reconsider whether force_suspend() is sufficient
<tomeu> hmm, yeah
<tomeu> we should really get panfrost igt running in kernelci...
BenG83 has joined #panfrost
davidlt has quit [Remote host closed the connection]
davidlt has joined #panfrost
karolherbst has joined #panfrost
megi has joined #panfrost
pp3345 has joined #panfrost
TheKit has joined #panfrost
karolherbst has quit [Quit: duh 🐧]
buzzmarshall has joined #panfrost
karolherbst has joined #panfrost
BenG83 has quit [Ping timeout: 268 seconds]
tgall_foo has joined #panfrost
pp3345 has quit [Ping timeout: 260 seconds]
BenG83 has joined #panfrost
BenG83 has quit [Quit: Leaving]
<leinax> tomeu: Doesn't look like bo's. I can see that weston-simple-egl slowly leaks. It looks like mesa is mallocing every so often. If I catch the brk syscall in gdb the mallocs are consistently originating from panfrost_scoreboard_queue_job_internal's util_dynarray_append calls.
<tomeu> oh, cool, will take a look with valgrind
<tomeu> I suspect that would be slowing things quite a bit
<leinax> Other common source of mallocs seems to be panfrost_batch_update_bo_access calling rzalloc_size. I'm not sure if either of those are the actual source of the leak.
<tomeu> cool
<tomeu> alyssa: this branch runs 1 5th of the gles3 tests in the same time that takes to run the full gles2: https://gitlab.freedesktop.org/tomeu/mesa/commits/panfrost-deqp-gles3
<tomeu> will push a MR once this one is merged: https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295
megi has quit [Ping timeout: 268 seconds]
yann|work has quit [Ping timeout: 260 seconds]
megi has joined #panfrost
pH5 has quit [Quit: bye]
yann|work has joined #panfrost
pH5 has joined #panfrost
pp3345 has joined #panfrost
robertfoss has quit [Ping timeout: 258 seconds]
robertfoss has joined #panfrost
davidlt has quit [Ping timeout: 268 seconds]
pp3345 has quit [Remote host closed the connection]
raster has quit [Quit: Gettin' stinky!]
guillaume_g has quit [Quit: Konversation terminated!]
buzzmarshall has quit [Remote host closed the connection]
raster has joined #panfrost
<alyssa> tomeu: Nice :)
<alyssa> HdkR: Yupyup
karolherbst has quit [Ping timeout: 268 seconds]
robert_ancell has joined #panfrost
<krh> yupyup
robert_ancell has quit [Ping timeout: 258 seconds]
karolherbst has joined #panfrost
karolherbst has quit [Client Quit]
NeuroScr has joined #panfrost
anarsoul|c has quit [Quit: Connection closed for inactivity]
icecream95 has joined #panfrost
<icecream95> for i in {1..10}; do timeout 3 glmark2-es2 -b refract; done seems to be quite a reliable way of triggering recursive faults.
<icecream95> i.e. you will get a kernel panic or hang soon
<leinax> This is probably way more useful than what I posted before. weston-simple-egl massif output after several hours: https://pastebin.com/kQz9UBcn
raster has quit [Quit: Gettin' stinky!]
pH5 has quit [Quit: -_-]
m][sko has joined #panfrost
<m][sko> Nice work with panfrost. I did some runs on MALI T620(Odroid XU4) and there are some artefacts. for example pure weston and glmark2. Are there any change that we see some "love" for T620 :)
AreaScout_ has quit [Remote host closed the connection]
<m][sko> I am really happy with state of panfrost on ubuntu 19.10 with gnome wayland.
m][sko has quit [Remote host closed the connection]
raster has joined #panfrost