05:34 alkisg: imirkin: I tested it in the office a lot, but I didn't have a chance yet to deploy it to a school that I was sure it had the issue
14:43 sigod: what's the story with the new nvidia hardware docs that were released, are they very useful?
15:24 doobz: Anybody (other than I) tried glmark2 on nv4b?
15:42 imirkin: alkisg: but your testing so far indicates that things have improved?
15:42 imirkin: doobz: i'm 99% sure i've tried running glmark on a nv4x, not a nv4b specifically
15:42 alkisg: imirkin: all problems solved! :)
15:43 imirkin: alkisg: awesome. i'll do a release, i think that's important enough to do, and it's not like there's a ton of "natural" development on the nouveau ddx anyways - it's pretty stable in general
15:44 alkisg: imirkin: thanks a lot; please ping me with the commit link so that I try to get it backported to Ubuntu... I uploaded a patched xorg, but they release newer versions every 6 months, so it's hard to have to patch them all the time...
15:44 imirkin: sure
16:03 imirkin: doobz: what version of mesa are you on now?
16:06 imirkin: sigod: they're very useful, but the usefulness tends to be for fairly niche features (like the recent release of crc readback)
16:07 imirkin: the important things are all RE'd by the time the docs come out
16:11 doobz: I tried to upgrade the deb buster installation to testing, and all was not well. Can try again. Am I able to just upgrade a single or select few packages?
16:15 imirkin: doobz: i have zero knowledge of debian ... you mentioned you did something, and it still didn't work. do you know what mesa version the something ended up with?
16:19 doobz: I'm guessing it was a 19 something. :) It was super glitchy and hung pretty quickly. I have a fresh buster install on a GF7100 desktop that exhibits the same issues as my laptopn. I can try a newer mesa on that fairly quickly.
16:21 imirkin: can you find out the actual version somehow?
16:21 imirkin: and glitchy in firefox, or in general? was this with xfce?
16:27 doobz: The login screen was kinda flashing in a bad way, the clock was stuck. After it hung when copying a couple of file to the network, I lost interest. It was late so nuked install to try sabayon.
16:28 doobz: I guess it was 19.2.1-1
16:32 imirkin: what's "sabayon"?
16:33 doobz: a gentoo based distro.
16:33 imirkin: ah ok
16:33 imirkin: next time this happens, have a look at /proc/interrupts
16:34 imirkin: and see if the number on the nvkm line increases
16:34 imirkin: i think we've had some issues with MSI interrupts on nv4x's
16:34 imirkin: iirc it was nv46 though
16:43 doobz: Just having a look on this install - and seem to be getting ~2 per second. No idea if that is normal or not
16:44 imirkin: that's within the realm of possibility
16:56 doobz: Is a valgrind output any good to anyone, specifically glmark2 seg-faulting?
16:59 imirkin: the backtrace from the segfault itself would be primarily interesting
16:59 imirkin: as well as how you invoked glmark2
17:16 doobz: $%^&! It's nearly 27MB. Does pastebin work with such large files?
17:16 imirkin: unlikely.
17:17 imirkin: but it's not very interesting to look for bugs in glmark2...
17:17 imirkin: if you have a stack trace, that should be enough to get started
17:21 doobz: Max paste size .5MB
17:27 doobz: Valgrind log here - http://www.filedropper.com/valgrind
17:28 doobz: Invoked - valgrind --leak-check=yes --log-file=valgrind.txt glmark2
18:12 mattst88: h/win 8
18:12 mattst88: derp