03:30sneil: dboyan_: no luck (same desktop freeze, except mouse cursor) with imirkin's suggestion on NV50_PROG_SCHED=0 and also no luck reverting d03bfb078. I didn't bother trying both together
04:09dboyan_: sneil: well, no idea then. You could bisect anyway if you're sure it was okay before and know a good revision.
04:29sneil: I'm not sure it was ever okay before, but I'll start to look
04:31sneil: do you think I can bisect just the gallium/drivers/nouveau/nvc0 directory
05:08dboyan_: sneil: First find a known working version, and 'git bisect' will help you find out in just a few tries
07:40hakzsam: sneil: which maxwell chipset?
07:42hakzsam: I remember something weird with compute on maxwell actually
07:42hakzsam: like my gm107 doesn't work very well, but mupuf's one works like a charm
07:43hakzsam: I didn't investigate more though
07:43hakzsam: probable unrelated to mesa
07:43hakzsam: mupuf: do you remember?
07:46hakzsam: ie. perf counters for example
07:49dboyan_: hakzsam: I remember sneil has gm107
07:49pmoreau: hakzsam: If I were to write some code that would measure perf of an OpenGL application running on Nouveau, how would I set up and read the performance counters? Is there a library to link against?
07:52pmoreau: Cool, thanks
07:53pmoreau: And that should support everything?
07:54hakzsam: pmoreau: yeah, https://cgit.freedesktop.org/~hakzsam/piglit/commit/?h=perf_counters&id=38ea6fb2299ad52caf99a6309ee0e3107738e332
07:55hakzsam: sneil: can you try 'GALLIUM_HUD="inst_executed" glxgears' on your gm107 and tell me what happens?
08:00mupuf: hakzsam: yeah, I remember your perf counter issue
15:47sneil_: Sure, I'll give that a try. Lastest git I assume?
16:51hakzsam: karolherbst: https://bugs.freedesktop.org/show_bug.cgi?id=100239#c7
16:51hakzsam: can you reproduce on nouveau?
16:52hakzsam: sneil_: yes
16:53karolherbst: hakzsam: that bug or the comment?
16:54hakzsam: while replaying the trace
16:55hakzsam: karolherbst: starting at frame 5310
16:56karolherbst: ahhhh okay, that's easy then
16:56karolherbst: the trace from comment 5 or 7?
16:56hakzsam: the trace should replay just fine
16:56karolherbst: that download site......
16:57karolherbst: ahh, there I have to click
16:59karolherbst: hakzsam: my internet situation here is currently very crappy, will take me like 2 hours to download :(
16:59karolherbst: or is that site just slow?
17:01hakzsam: it's slow but not that much
17:01hakzsam: dl.free.fr is a crappy french site
17:02karolherbst: I get around 100kB/s
17:02hakzsam: karolherbst: feel free to leave my a comment later or during the weekend
17:02hakzsam: there is no rush
17:02hakzsam: *me a
17:02karolherbst: I already see it coming: abort after 99.9%, please start from 0
17:04hakzsam: I think you shouldn't be able to reproduce the issue with nouveau, but I can be wrong :)
18:04karolherbst: hakzsam: could you give me the output of the public khronos CTS for 4.5 on AMD hardware? So I know which tests I should focus on. I kind of want to fix issue to get more into mesa development
18:05karolherbst: I get it to run on my system with nouveau
18:05karolherbst: and there are enough fails to work on
19:08Lyude: How difficult would it be to hook up a card running nouveau to a machine that already has a GPU using amdgpu? would like to render some stuff on a nvidia card while using the amdgpu card for everything else
19:12librin: I seem to have hit a nouveau-related regression, but I am not exactly sure
19:18librin: one of my monitors now starts flickering and has messed up contrast/brightness if I set the refresh rate to anything higher 60Hz
19:19librin: and even on 60Hz, there's a little bit of flickering
19:21librin: anyone has any idea if something in recent nouveau-related changes could have what could cause that?
19:21librin: (recent as in "past two weeks or so")
19:21librin: s/higher 60Hz/higher than 60Hz/
19:22karolherbst: Lyude: DRI_PRIME
19:22karolherbst: Lyude: or second X server
19:22Lyude: that'll just work? nothing else needed?
19:23karolherbst: it just works with DRI3
19:23karolherbst: otherwise you need to do that xrandr configuration stuff
19:23karolherbst: but yeah, DRI_PRIME should just work
19:23Lyude: huh, i would think gnome-shell would be using dri3 for wayland
19:23Lyude: that's cool, thanks for the info
19:28karolherbst: found an infinite loop within RA with khronos CTS :) fun
19:33karolherbst: that tgsi: https://gist.github.com/karolherbst/267b329b88c99c8a65f7e36beaca4e5f
19:36librin: I tried downgrading my xf86-video-nouveau, libdrm and mesa to revisions before them, but that didn't help.
19:36librin: Any idea what else could interfere with how nouveau handles monitors that I could try downgrading?
19:45librin: oh, right, forgot to mention I didn't touch the kernel at all
19:45librin: still on the same 4.10.12 which worked fine
19:50librin: this is so weird; if I didn't know any better, I'd think it's a hardware problem :S
19:50librin: which it isn't – I booted to windows (yuck!) and it works fine there
20:13Lyude: btw karolherbst would you happen to know how the primary GPU is selected in a config like that?
20:16karolherbst: Lyude: you can set the pci address in DRI_PRIME somehow... don
20:16karolherbst: 't know the format
20:16Lyude: on that note, it would be really nice if this desktop actually had USB-C ports I could use for plugging another GPU into
20:16karolherbst: but yeah, you can somehow explicitly select the device as well
20:17karolherbst: Lyude: interesting idea
20:17Lyude: karolherbst: yeah it's been done for a while, every now and then people poke me and ask if we're ever going to support hotplugging GPUs...
20:17karolherbst: DRI3 supports hotplugging
20:17Lyude: it does?
20:17Lyude: oh wow, I never even knew that
20:17karolherbst: well the main GPU stays the same
20:17karolherbst: but that
20:18karolherbst: 's X fault
20:18karolherbst: well the PCIe bus also needs to support hotplugging
20:18karolherbst: but with DRI3 you can load nouveau after X started
20:18karolherbst: and use it via DRI_PRIME
20:18karolherbst: that's how I do it
20:18karolherbst: ohhh wait, there is something required
20:18karolherbst: because DRI2 sucks
20:19karolherbst: Lyude: https://gist.githubusercontent.com/karolherbst/4341e3c33b85640eaaa56ff69a094713/raw/c976daa9e406d37e01351357ea9d8c20d5097d66/xorg.conf.d.nouveau.conf
20:19Lyude: luckily I just use wayland for most everything at this point
20:19karolherbst: with that you can unload Nouveau with X running
20:20karolherbst: with that I actually switch between Nvidia and Nouveau without restarting X on my laptop
21:39karolherbst: hakzsam: ......... the download just failed two times now, because of silly reasons :/
21:39karolherbst: twice around 600MB
22:05Manoa: hi did you guys know that you win 10,000 internets ?
22:06Manoa: I digged up my linux installation and updated everything, I didn't expect anything to work at all, but to my surprise all of my important games work very well
22:06Manoa: almost as good as windows
22:07Manoa: I have a couple questions, I have a kepler GK110B 780 Ti, I heard that it has some fancy memory compression feature, I was wondering if that is being used and I think in one of my games I am running out of video memory, I tried to use GALLIUM_HUD but it didn't have that graph in the help list
22:08Manoa: reclockig works flawlessly
22:08Manoa: it's a EVGA classified kingpin card
22:09Manoa: is it possible that when it's out of video memory that it could cause texture corruption ?
22:10Manoa: will video memory in wine use the same amount as video memory in nine ?
22:13Manoa: I have a hardware monitoring sensors in the card, I noticed that when I used a ubuntu stock kernel in my slackware, but in my custom built kernel I don't have those sensors, do I need to include some i2c and smbus drivers to enable ?
22:19librin: Manoa: the "texture corruption" You see is most likely caused by a x86 game running out of that very limited address space. As at least under Wine, last time I checked, textures, buffers and whatnot are in the same address space as the game's process, easily leading to address space exhaustion and because of it, problems ranging from texture issues to outright crashes.
22:21Manoa: can I used huga pages to reduce pressure on the virtual address space ?
22:22Manoa: yes that is the problem, I saw many times wine says out of memory
22:23librin: there's little You can do with the 4GiB limitation
22:23librin: of x86
22:23Manoa: guess I will have to give all those fancy graphics mods :x
22:25Manoa: and the sensors ? are they only exist on ubuntu kernel ? or can I enable them in the kernel config ? there are so many sensor drivers I don't know which one gives the diagnostic for the card :x
22:27librin: Unless You can code a way to put the graphics part that's outside of the game's reach to a separate address space. Which is done on windows AFAIK and which nvidia's blob does. But when it comes to Wine, there's also the issue of the Wine's side of things, which would have to be separated... separately.
22:28librin: why would sensors be only on ubuntu's kernel?
22:28Manoa: I don't know :x they are there and but here
22:29Manoa: I guess I didn't include those smbus i2c drivers in my compilation of the kernel
22:29Manoa: but I don't know which they are so mybe I need to include all of them next time I build kernel
22:29librin: what distro are You on right now?
22:29Manoa: slackware 14.1
22:30Manoa: my kernel is 4.11
22:30Manoa: ubuntu kernel is 4.10
22:31Manoa: from ubuntu 17
22:31librin: You most likely need CONFIG_I2C, yes
22:31Manoa: so this explain why I can run all those mods on windows but out of memory on wine, I had no idee that nvidea can do this
22:32Manoa: but you know they don't do it very well, there is still a limit, I had the game crash on windows too
22:33librin: a x86 game itself is still limited to 3GiB (yes, less than on Linux) of address space on Windows either way, so having enough mods can easily do that, yes
22:35Manoa: is there a way to see video memory / gpu usage and similar besides GALLIUM_HUD ? for some reason these options don't show up when I say GALLIUM_HUD=help
22:36Manoa: or is this not yet exist in nouveau ?
22:48Manoa: another question, when I run a gl app with pp_jimenezmlaa envoronment I get an error saying pp: Failed to translate a shader for depth1fs, usually the app crash because of this, is this problem fixable ?
22:48Manoa: I want this anti aliasing because it the best
22:49Manoa: funny thing happens is when I enable MSAA on nine I get blurred rendering, but in wine I don't, I dont want to run wine because nine give performance, but on the other hand I want anti aliasing :x
22:51Manoa: I also try to use shader mod to improve graphics but his SMAA anti aliasing also causing blurred rendering