13:42 glisse: anybody seen acr loading failure on 1080 ?
14:01 karolherbst: glisse: donnu, it doesn't load relible on my 1050
14:01 karolherbst: glisse: it's the gr init time out thing you see, right?
14:01 karolherbst: glisse: that patch might help, mind trying it out? https://github.com/karolherbst/linux/commit/ecb1d072ebdb5538e5b4fd5210c4173dd7f33719
16:05 glisse: karolherbst: just someone at lsf that has that problem, it always work for me so i was kind of surprise for pascal
16:05 glisse: karolherbst: i will point out your patch
16:07 karolherbst: cool
19:10 jamincollins: I believe I've followed the nouveau Optimus documentation, but I can't seem to get DRI_PRIME=1 working for either DRI2 or DRI3: https://gist.github.com/jamincollins/d80bbf5ddae1074c47051ba9e63caf1d
19:11 jamincollins: also, there are long (multi-second) delays when the X session initially starts up
19:12 gnarface: did you check the xorg log to see if it's even loading the nouveau driver first? i thought that long delay comes from it cycling through framebuffer drivers
19:13 jamincollins: if it wasn't loading the driver I don't believe I'd have it listed in the `xrandr --listproviders` output
19:13 jamincollins: [ 1126.320] (--) NOUVEAU(G0): Chipset: "NVIDIA NV137"
19:13 gnarface: maybe so, i dunno
19:14 gnarface: though the delay could be caused by that even if it settles on the right one eventually
19:14 jamincollins: that was my experience before getting to this point, in order to even get this far, I had to create an xorg config stub telling it to load the nouveau driver
19:15 karolherbst: jamincollins: with dri3 you won't have to do any of the xrandr calls
19:15 jamincollins: that would be great, but neither of them work =)
19:15 karolherbst: is nouveau loaded at all?
19:15 jamincollins: yep
19:16 karolherbst: ohhh
19:16 karolherbst: "nvc0_screen_create:1007 - Error allocating PGRAPH context for M2MF: -16"
19:16 karolherbst: yeah....
19:16 jamincollins: yep
19:16 karolherbst: mhhh
19:16 karolherbst: okay, so something fails hard
19:16 karolherbst: dmesg should contain more information
19:16 karolherbst: I think I know what it is, but I rather want to check to be sure
19:18 karolherbst: jamincollins: you might need to set nouveau.runpm=0 _and_ need this kernel patch: https://github.com/karolherbst/linux/commit/ecb1d072ebdb5538e5b4fd5210c4173dd7f33719
19:18 karolherbst: maybe only one of them is required
19:18 karolherbst: dunno if runpm works on your machine
19:18 karolherbst: dunno if secboot fails
19:18 karolherbst: dmesg should tell us
19:18 jamincollins: [ 2652.137590] nouveau 0000:01:00.0: timeout
19:18 jamincollins: [ 2652.137638] WARNING: CPU: 8 PID: 4474 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207 gf100_vmm_flush_+0x17b/0x190 [nouveau]
19:19 karolherbst: mind uploading your full dmesg somewhere?
19:19 jamincollins: working on it, it's HUGE
19:20 jamincollins: https://pastebin.com/qvF5q5fB
19:23 karolherbst: "dmesg | xclip -selection clipboard" helps :)
19:23 jamincollins: $ dmesg | pastebinit
19:23 karolherbst: or that
19:23 karolherbst: anyway, I am more interested in what errors we have before the stacks
19:24 jamincollins: I'll reboot and brb with a fresh state
19:27 jamincollins: https://pastebin.com/mmaZNYTF
19:27 jamincollins: that's as fresh as I can get it
19:28 jamincollins: still seems to be missing 12 seconds
19:28 karolherbst: mhhh .. :/
19:29 jamincollins: looking in journalctl now
19:29 karolherbst: jamincollins: journalctl --boot 0 --dmesg
19:29 karolherbst: ahh.. yeah
19:29 jamincollins: https://pastebin.com/cxjfCLab
19:30 karolherbst: cool, that looks better
19:30 jamincollins: Apr 30 13:25:03 odin kernel: nouveau 0000:01:00.0: fifo: fault 00 [READ] at 0000000000000000 engine 1f [PHYSICAL] client 07 [GPC0/T1_2]>
19:31 karolherbst: jamincollins: okay.. it's the secboot issue
19:31 karolherbst: jamincollins: mind compiling a kernel with the patch applied I linked above?
19:31 jamincollins: it's been a long while, but I can give it a shot
19:31 karolherbst: I think it shouldn't be too hard with arch
19:32 jamincollins: and you'll need to relink me, rebooted between then and now
19:32 karolherbst: https://github.com/karolherbst/linux/commit/ecb1d072ebdb5538e5b4fd5210c4173dd7f33719.patch
19:33 karolherbst: jamincollins: you might want to test that with nouveau.runpm=0 set as well to rule out suspending the GPU messes up things later :/
19:33 karolherbst: kind of working on getting that fixed as well
19:34 karolherbst: this gf100_gr_init failing issue kind of only happens on a few random GPUs... no idea what's wrong there as nvidia literally prevents us from debuggin this on a hardware level
19:34 jamincollins: why make it easy?
19:34 karolherbst: well, signed firmware and such
19:35 karolherbst: we essentially boot some engines with signed firmware and while the engine is booting, we can't look into the state
19:35 karolherbst: essentially it's a black box :)
19:35 karolherbst: and then it stops because $something failed
19:35 karolherbst: and of course, because it stopped, we can't look into the state as well
19:35 karolherbst: it's super annoying
19:35 karolherbst: anyway, that patch fixes this on my machine as well
19:36 jamincollins: attempting a kernel build
19:36 gnarface: i think you guys should try hiring a psychic to help guess what's going on in those states
19:36 gnarface: nothing else works, might as well try everything, right?
19:36 karolherbst: gnarface: wouldn't come up with worse guesses at least
19:37 gnarface: you never know. sometimes psychics are good at guessing stuff :)
19:37 karolherbst: that's like 99% of their skills, yes
19:37 karolherbst: good guessing :p
19:37 gnarface: it would be pretty funny if that worked
19:38 karolherbst: I'd rather try AI enforced reverse engineering :p
19:38 gnarface: "we couldn't reverse engineer anything past this point, so we hired some professional guessers..."
19:38 gnarface: i can picture the documentary now
19:38 karolherbst: too cheap
19:38 karolherbst: :D
19:39 karolherbst: but actually, AI should be able to come up with a working GL driver...
19:40 karolherbst: apitrace in, commands out
19:40 karolherbst: just.. that none of the current systems would be fast enough for it
19:40 karolherbst: would probably take millions of years
19:44 jamincollins: so, karolherbst, which line in the dmesg output cinched it for you?
19:45 karolherbst: jamincollins: nouveau 0000:01:00.0: gr: init failed, -16
19:46 karolherbst: and the absence of other issues
19:47 jamincollins: the wait for the X session to actually start is long enough I gave up on it the first several times
19:48 jamincollins: got lucky (I guess) and was distracted while waiting for one of the attempted boots
20:25 jamincollins: karolherbst: installing now
20:26 jamincollins: rebooting
20:29 jamincollins: looks better in terms of boot time
20:30 jamincollins: and DRI works
20:31 jamincollins: *and* my external display works =)
20:32 jamincollins: I'm in a little slice of heaven right now
20:33 jamincollins: karolherbst: THANK YOU!
20:33 karolherbst: :)
20:40 karolherbst: jamincollins: we might be able to merge that commit at some point, the nouveau maintainer asked me to get more user testing on that one
20:40 karolherbst: or rather proof it helps
20:52 jamincollins: karolherbst: I'm happy to note such on the report
20:53 jamincollins: and I updated the github gist with a link to the patch
21:02 jamincollins: am I right in thinking that with nouveau and Optimus that the nvidia chip _should_ power down at some point?