ChanServ changed the topic of #lima to: Development channel for open source lima driver for ARM Mali4** GPUs - Kernel has landed in mainline, userspace driver is part of mesa - Logs at https://people.freedesktop.org/~cbrill/dri-log/index.php?channel=lima and https://freenode.irclog.whitequark.org/lima - Contact ARM for binary driver support!
megi has quit [Ping timeout: 258 seconds]
drod has quit [Remote host closed the connection]
yuq825 has joined #lima
jrmuizel has joined #lima
yuq8251 has joined #lima
yuq825 has quit [Ping timeout: 258 seconds]
jrmuizel has quit [Remote host closed the connection]
Elpaulo has quit [Read error: Connection reset by peer]
Elpaulo has joined #lima
yuq8251 has quit [Remote host closed the connection]
chewitt has joined #lima
chewitt has quit [Quit: Zzz..]
dddddd has quit [Remote host closed the connection]
chewitt has joined #lima
chewitt has quit [Client Quit]
Barada has joined #lima
yuq825 has joined #lima
guillaume_g has joined #lima
guillaume_g has left #lima ["Konversation terminated!"]
cwabbott has joined #lima
Barada has quit [Quit: Barada]
<cwabbott> bshah: https://invent.kde.org/snippets/347 does indeed look like an infinite loop in the gp scheduler
<cwabbott> I can guess what's going on, but to be sure I need to have the shader it came from so that I can reproduce it
<cwabbott> https://bshah.in/lima-log-virtual-keyboard.txt doesn't seem to have that information (all the shaders in there are scheduled successfully)
<cwabbott> https://bshah.in/lima.dump doesn't have any gpir debugging information at all
<cwabbott> I need the messages that come right before it starts spewing the stuff in https://invent.kde.org/snippets/347
<bshah> that's going to be insta hard to debug
<bshah> erm insta hard to fetch I mean :)
z3ntu has quit [Write error: Broken pipe]
romainmahoux[m] has quit [Read error: Connection reset by peer]
bshah|matrix has quit [Remote host closed the connection]
<bshah> as there is etoomuch output.. but I can try and see
calcprogrammer1 has quit [Remote host closed the connection]
<bshah> cwabbott: re: lima.dump file, do LIMA_DEBUG=all doesn't work? that was generated with it
<cwabbott> no idea, but I guess it doesn't
<cwabbott> I mean, you can see that it doesn't have anything starting with "gpir: "
<bshah> hm yeah, lima.dump file was auto generated IIRC, and output was spawned in stderr
<bshah> Okay, I'll retry and send you log before today evening
<cwabbott> oh yeah, that's right, lima.dump is meant for replaying so it only has the raw binary output
<enunes> wasn't that with an out of tree patch and without the latest gpir fixes?
megi has joined #lima
<cwabbott> enunes: my fixes won't fix that
<cwabbott> they fix a crash elsewhere, and some silently incorrect code generation
<bshah> enunes: yes, it was out-of-tree patch, I mentioned it :)
<bshah> and no teh MR didn't help
<cwabbott> bshah: you can try attaching a debugger and going up the callstack to see what shaders it was compiling
<enunes> to output the shaders in my logs I use MESA_GLSL=dump MESA_DEBUG=1
<cwabbott> that would require some fiddling with mesa internals or kde internals in gdb though
<bshah> cwabbott: I think capturing log would be easy enough ... it's just atm occupied with $work stuff :)
<cwabbott> sure
<cwabbott> just remember to also do MESA_DUMP=glsl to see the GLSL source code
bshah|matrix has joined #lima
<bshah> cwabbott: So ultimately I grab full output with : MESA_DUMP=glsl LIMA_DEBUG_GP=1 right?
<bshah> building git mesa master atm ^^
<cwabbott> iirc it's LIMA_DEBUG=gpir instead of LIMA_DEBUG_GP=1 now
<bshah> ah right.
calcprogrammer1 has joined #lima
z3ntu has joined #lima
romainmahoux[m] has joined #lima
yuq825 has quit [Remote host closed the connection]
buzzmarshall has joined #lima
dddddd has joined #lima
<bshah> hm
<bshah> for some reason with debug set app doesn't die at all
<bshah> oh there we go
drod has joined #lima
<cwabbott> bshah: I think I see the bug, but I'm going to have to think about the best way to fix it
yuq825 has joined #lima
<cwabbott> I'm gonna think it over but I gotta do real work stuff now
cwabbott has quit [Quit: cwabbott]
afaerber has quit [Quit: Leaving]
cwabbott has joined #lima
drod has quit [Ping timeout: 272 seconds]
buzzmarshall has quit [Quit: Leaving]
jrmuizel has joined #lima
buzzmarshall has joined #lima
buzzmarshall has quit [Quit: Leaving]
buzzmarshall has joined #lima
drod has joined #lima
tlwoerner has quit [Quit: Leaving]
yuq825 has quit [Remote host closed the connection]
<anarsoul> cwabbott: do you by any chance know how to fix standalone compiler to work with fragment shaders?
<cwabbott> anarsoul: it's broken atm with desktop GL, it was something stupid that I didn't want to spend too long to fix
<cwabbott> just add "#version 100\nprecision highp float;\n" at the beginning and replace gl_Color with a regular varying if that's the issue
<cwabbott> otherwise, I dunno... I haven't tried it recently with fragment shaders but it *should* work
<cwabbott> also, your address for your pinebook seems to be down... did you have to take it down?
<anarsoul> cwabbott: yeah, I accidentally disconnected it from power supply
<anarsoul> do you want me to bring it back?
<MoeIcenowy> what a pity that my continously working SBC uses Mali-T720
<anarsoul> OK, battery is dead, it'll take some time (~1h?) to charge it (it won't power on till it reaches certain threshold)
<MoeIcenowy> anarsoul: does this situation exist?
<MoeIcenowy> my Pinebook always instantly power on when DC inserted
<anarsoul> MoeIcenowy: what situation?
<anarsoul> it won't power on if battery is completely drained
<anarsoul> cwabbott: pinebook is up again, you should be able to ssh into it
<MoeIcenowy> oh maybe my battery is not drained enough?
drod has quit [Remote host closed the connection]
<anarsoul> I get occasional RCU stalls on 5.2 :(
<anarsoul> not related to lima though
drod has joined #lima
buzzmarshall has quit [Remote host closed the connection]
jrmuizel has quit [Remote host closed the connection]
jrmuizel has joined #lima
<anarsoul> enunes: are you running 5.2 on your pine64?
jrmuizel has quit [Ping timeout: 258 seconds]
drod has quit [Ping timeout: 246 seconds]
jrmuizel has joined #lima
drod has joined #lima
Net147 has quit [Ping timeout: 272 seconds]
Net147 has joined #lima
jrmuizel has quit [Remote host closed the connection]
Net147 has quit [Ping timeout: 258 seconds]
jrmuizel has joined #lima
Net147 has joined #lima
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #lima
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #lima
paulk-leonov has quit [Ping timeout: 250 seconds]
paulk-leonov has joined #lima
jrmuizel has quit [Remote host closed the connection]