03:44 imirkin: Lyude: friendly ping on the mst thing
08:11 pabs3: my GPU seems to be in some sort of weird freeze state. GL apps freeze but X11 works fine. compositing WMs seem to freeze too. any idea how to debug this?
08:11 pabs3: when I press Ctrl+C in gdb, I get this: http://paste.debian.net/1025193/
08:13 pabs3: aha, I also get this in dmesg: http://paste.debian.net/1025194/
08:14 pabs3: this is with Linux 4.16.5-1 from Debian buster
08:15 pabs3: my GPU: 01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GT 740] (rev a1)
09:38 karolherbst: skeggsb, imirkin: I am currently thinking if we should disable runpm support on all laptops doing this _PR thing, because it is broken on 2 laptops I have access to out of 2 having _PR
09:39 karolherbst: I am not talking about disabling it inside nouveau, but on the whole kernel level, because I am sure it is broken for AMD GPUs as well
09:57 karolherbst: I will try to figure something out on this new laptop I got my hands on, which has a gm204 GPU
10:05 airlied: karolherbst: sounds like the sort of problem RH would want fixed
10:07 karolherbst: yeah..
10:07 karolherbst: the situation is.... weird
10:11 karolherbst: anyway, I tried to look into it and well
10:11 karolherbst: it's just a bug inside the linux kernel basically
10:11 karolherbst: so basically what happens is, that the GPU suspends just fine
10:11 karolherbst: also resuming just works, but we don't get any connection through the PCIe bus
10:12 karolherbst: so what works is: remove PCIe device, call ACPI methods, rescan bus -> load nouveau
10:26 karolherbst: ahhh github change their website layout :(
11:34 imirkin: pabs3: update to a newer kernel. swiotlb error messages got fixed at some (recent) point ... finally.
11:36 pabs3: imirkin: any idea which version? 4.16.9 or 4.17-rc5?
11:37 imirkin: yes, either one of those
11:39 karolherbst: imirkin: famous last words
12:19 karolherbst: hum, I just spammed some glxspheres and this happened: https://gist.githubusercontent.com/karolherbst/3abe9eb280196529c38bdbc437d25607/raw/23795b29750b0bf0179ffc6062cf99b97d916023/gistfile1.txt
12:20 karolherbst: I guess this is the famous multi context issue we hit?
12:36 imirkin: karolherbst: glxspheres shouldn't be threaded afaik
12:36 imirkin: [ 513.452930] nouveau 0000:02:00.0: gr: GPC0/PROP trap: 00000400 [RT_LINEAR_MISMATCH] x = 368, y = 66, format = 2a, storage type = 0
12:36 imirkin: that's the real issue...
12:36 imirkin: some kind of buffer mismanagement
12:37 karolherbst: mhh
12:38 imirkin: (or context switch issue)
12:38 karolherbst: or that
12:38 karolherbst: I was running it on a gk106 which should have those issues where blob firmware helps
12:39 imirkin: oh
12:39 karolherbst: but this something I would like to look into next week
12:39 karolherbst: I was just surprised that I triggered that after a few seconds
12:39 imirkin: yeah, for those GK106's, the issues come about quickly.
12:39 karolherbst: ahh
12:39 karolherbst: I see
12:39 karolherbst: so I guess something in the firmware is fishy then and maybe I can track it down with that card
13:13 imirkin_: or something with how gr is initialized
13:13 imirkin_: which their ctxsw handles but ours doesn't
13:13 imirkin_: check ben's recent stuff
13:14 imirkin_: he has some gr init updates
13:14 imirkin_: not sure if they'd matter
13:34 karolherbst: I ran it on his master branch
13:35 karolherbst: I also gave him traces of this card, but he said he didn't catch anything suspicious
13:35 imirkin_: ok
19:51 diogenes_: Hello guys, so i've got nvidia optimus (intel + nvidia), i use nouveau and if i understand it right, in order to run an application with nvidia card, i have to use: DRI_PRIME=1 application, but is there any monitoring tool something similar to nvidia-settings to see the gpu percentage utilization and stuff?
19:58 imirkin_: there is not.
20:01 HdkR: tsk tsk :P
20:01 imirkin_: send patches.
20:01 imirkin_: i haven't a clue how to even measure gpu utilization
20:02 diogenes_: imirkin_, so how can one be sure if the gpu is being utilized?
20:02 imirkin_: DRI_PRIME=1 glxinfo
20:02 imirkin_: if that says nouveau, then you're good.
20:02 imirkin_: you can also tell based on whether nouveau_dri.so is loaded (check /proc/<pid>/maps)
20:03 imirkin_: i suppose we could expose various counters, like "job submitted" and so on
20:03 imirkin_: (like perf events or something)
20:03 glennk: doesn't nouveau expose various counters for GALLIUM_HUD?
20:03 diogenes_: imirkin_, ok thanks, one more question, are there any tricks to improve the performance with nouveau?
20:04 imirkin_: glennk: sure, but this is for a side application
20:04 imirkin_: diogenes_: what GPU?
20:08 diogenes_: imirkin_, NVIDIA Corporation GK107M [GeForce GT 650M]
20:09 orbea: before xorg 1.20.0 DRI3 + modesetting had a small, but noticable perf boost, now it doesn't work...
20:10 orbea: reclocking too ofc
20:13 imirkin_: diogenes_: assuming you're on kernel 4.10 or later, you can reclock your gpu
20:13 imirkin_: it boots into the lowest perf level, so you should be able to get a lot more speed out of it
20:13 imirkin_: cat /sys/kernel/debug/dri/0/pstate (or /1/pstate)
20:14 imirkin_: that should give you a list of the available perf levels
20:14 diogenes_: imirkin_, i've just done the furmark test and i got with intel modesetting - 274 points and with nouvea - 184
20:14 diogenes_: kernel 4.4
20:14 imirkin_: ah yeah, with kernel 4.4 your options are limited
20:14 imirkin_: there was early reclocking then, i think ... you may be able to go up to a middle clock speed
20:15 imirkin_: 4.4 came out like 2y ago though, so you're missing out on some fixes :)
20:15 orbea: I'd think updating the graphics stack/kernel might be worth it in general for nouveau :)
20:15 diogenes_: imirkin_, ok, soon my distro will be upgraded to 1.16 i guess
20:15 imirkin_: hopefully 4.16 :)
20:16 diogenes_: errr
20:16 diogenes_: 4.16 :)
20:16 imirkin_: what intel is in there? haswell?
20:17 imirkin_: i'm not surprised that on lowest perf level it wouldn't have outperformed
20:17 diogenes_: imirkin_, i7 ivi bridge
20:17 imirkin_: ouch
20:17 imirkin_: ivybridge was pretty slow
20:18 diogenes_: maybe but in furmark it gets mre points than my nvidia
20:18 imirkin_: yes
20:18 imirkin_: with the lowest perf level, not super-surprising
20:18 imirkin_: cat that pstate file
20:18 imirkin_: should tell you where you are now, and what the card max is
20:18 imirkin_: (pastebin the results)
20:18 diogenes_: imirkin_, sorry, i missed something, what should i cat?
20:18 imirkin_: oh, maybe in 4.4 it was actually still in sysfs, not debugfs yet
20:19 imirkin_: so long ago
20:19 imirkin_: 4.4 released Jan 10, 2016
20:20 diogenes_: imirkin_, here is the output of cat: http://termbin.com/i44pk
20:20 imirkin_: ok right. so it's off now, hence the zero's
20:20 imirkin_: my guess is that you should be able to reclock to 0a in kernel 4.4
20:21 imirkin_: if you feel like trying it, start something that uses the gpu
20:21 imirkin_: and then as root
20:21 imirkin_: echo 0a > /sys/kernel/debug/dri/0/pstate
20:21 imirkin_: note that there's a 50% chance that your comp will hang.
20:21 imirkin_: so save your work :)
20:23 imirkin_: lol. https://github.com/skeggsb/nouveau/issues/2
20:23 diogenes_: imirkin_, i ran: echo 0a > /sys/kernel/debug/dri/0/pstate but nothing's going on, only the fans are louder now
20:23 imirkin_: diogenes_: while an app was using the gpu?
20:23 imirkin_: (the nvidia gpu)
20:23 diogenes_: imirkin_, nothing was using the gpu
20:24 imirkin_: ok, so now you have a hung cpu probably
20:24 imirkin_: like i said above, something must be running on the gpu
20:24 imirkin_: so you should reboot.
20:24 diogenes_: ok i reboot and come back
20:25 imirkin_: skeggsb: the fps on intel is much more better!
20:26 diogenes_: imirkin, so what should i do now? what are the steps?
20:27 imirkin_: diogenes_: step 1: make sure something is running on nvidia gpu
20:27 imirkin_: step 2: echo 0a > .../pstate
20:27 imirkin_: step 3: enjoy higher perf
20:27 diogenes_: ok let me see
20:27 imirkin_: step 2 must happen WHILE osmething's urnning on the gpu
20:27 imirkin_: also i think once it stops, the settings won't persist
20:27 diogenes_: so i have to run: DRI_PRIME=1 application
20:27 imirkin_: (the gpu gets auto-suspended when not used)
20:27 diogenes_: then run the echo
20:27 imirkin_: while the app is running
20:27 imirkin_: yes
20:28 diogenes_: ok let's see :)
20:28 imirkin_: note that 4.4 is a long time ago, and we had a lot of trouble with reclocking in those days
20:28 imirkin_: 0f definitely won't work out
20:28 imirkin_: 0a might work
20:28 imirkin_: with a 4.10+ kernel 0f should work
20:29 imirkin_: (v4.10 was released Feb 19, 2017)
20:31 diogenes_: imirkin_, wow, i actually got twice as much as intel gave me, so it's definitely cool, how can i make it persistent?
20:32 imirkin_: you can't.
20:32 imirkin_: er wait... no you can
20:32 imirkin_: add nouveau.config=NvClkMode=10 to your kernel config
20:32 diogenes_: how how how :)
20:32 diogenes_: to grub?
20:32 imirkin_: (or equivalent effect via modprobe config)
20:32 imirkin_: yes
20:32 imirkin_: er, add ... to your kernel cmdline, of course. not config. my bad.
20:32 diogenes_: let's see :) thanks so much for such a cool trick
20:35 diogenes_: imirkin_, ok added it and before i reboot, one more little question, when i boot, i notice a few messages like this:
20:35 diogenes_: nouveau 0000:01:00.0: iccsense: Unknown sensor type 30, power reading disabled
20:35 imirkin_: you should get another 4x improvement with 0f, i suspect.
20:36 imirkin_: that's fine
20:36 imirkin_: someone might be interested in your vbios though
20:37 diogenes_: so what do you say, instead of NvClkMode=10 i should add NvClkMode=0f?
20:37 imirkin_: =15. but that won't work with kernel 4.4
20:37 diogenes_: ok, let me reboot and see what's going on
20:43 diogenes_: imirkin, yay! perfect, it works like a charm, thank you very much and i think i could add this trick to archwiki because it's not mentioned anywhere and that's not right, everyone should know this, nouveau is cool!
20:57 imirkin_: diogenes_: not according to this guy: https://github.com/skeggsb/nouveau/issues/2
21:00 imirkin_: apparently nouveau fps must be much more!
21:01 diogenes_: imirkin_, well with the trick you provided, now it's 2x more than intel
21:01 imirkin_: hehe
21:02 diogenes_: previously it was much lower than intel
21:45 diogenes_: imirkin, i've just tried with =15 and it's amazing, i got a result very close to the nvidia proprietary driver, so it's trully amazing!
21:45 diogenes_: so it turns out, it works on 4.4
21:46 HdkR: "Nvidia devs hate him using this one simple trick. Click to find out more."
21:48 annadane: what are people talking about?
21:48 diogenes_: about improving nouveau performance
21:48 HdkR: putting the GPU in a higher power mode to get better perf
21:49 annadane: i kind of just caved and started using the proprietary driver