01:12 imirkin: skeggsb: looks like more DP fail :)
01:13 imirkin: might be related to the OR refactor
01:41 mangix: wayland fails in f26. not good.
02:03 mangix: getting this: https://paste.fedoraproject.org/paste/I-udg5iCrtJMDnheZWa2jw
02:03 mangix: last line keeps getting spammed
02:03 mangix: journald can't keep up with the spam
02:06 imirkin: mangix: update your kernel... feels like the 64-bit issue
02:07 imirkin: [with secboot]
02:07 mangix: what 64-bit issue?
02:07 imirkin: there was some issue with secboot and >= 4GB vram where the pointer would get messed up
02:08 imirkin: or something like that
02:08 mangix: i have those patches
02:08 mangix: applied
02:08 imirkin: i'm wrong then. all hope is lost.
02:08 mangix: :(
02:17 mangix: hrm that's a weird address
02:17 mangix:had an epiphany
02:19 mangix: GART: 1048576 MiB
02:19 mangix: what is this GART?
02:20 imirkin: 1TB - 40bit address space.
02:37 mwk: mangix: GART is system memory that is mapped to GPU's virtual memory system
03:03 rhyskidd: mwk: No problem by the way with your comment on my envytools PR :)
03:03 mwk: rhyskidd: ?
03:03 rhyskidd: is mwk == koriakin?
03:03 mwk: yes
03:04 rhyskidd: it was the nv04_pgraph_is_nv25p() based clean up that I've now dropped
03:05 mwk: ah, I thought it was about the ELPG_ENABLE thing
03:06 rhyskidd: I'm thinking how best to verify those ELPG_ENABLE bits, given they aren't *used* much in the pre-Pascal mmiotraces I have access to
03:07 mwk: meh about that
03:07 mwk: just fix the variants and we're good to go
03:07 mwk: it's quite obvious from the placement that they're the same bits as in ENABLE
03:07 mwk: my complaint is that you have eg. GP100- variants for PGRAPH
03:08 rhyskidd: okay
03:08 mwk: while it obviously exists since GF104
05:39 airlied: skeggsb: you're git pull url is wrong btw, git://github.com/skeggsb/git/linux has an extra git
05:39 skeggsb: oh, oops, want me to re-send?
05:40 airlied: nope it's fine, I just edited out
05:40 skeggsb: i'm currently playing "downgrade random shit to find what regressed wayland in f26"
05:40 skeggsb: no luck so far on obvious candidates
05:41 airlied: skeggsb: what happens? fails to start?
05:42 skeggsb: it appears to be limited to gm20x (maybe gp10x i guess, but not sure), but the gpu just goes psycho for unknown reasons
05:42 skeggsb: spews dmesg then hangs
05:44 airlied: skeggsb: which bit dies, graphics or display?
05:44 skeggsb: graphics
05:51 airlied: skeggsb: does just running mutter against bare X break it?
05:51 skeggsb: the gnome X session is fine, just wayland
05:51 airlied: oh doh
06:02 airlied: skeggsb: does the gdm session work?
06:02 skeggsb: yeah, gdm works for some reason
06:02 airlied: a g86 bug with PRAMIN exhaustion just went past me
06:02 airlied: with wayland
06:03 skeggsb: i did see something about that... i *am* noticing that when i do try to login with wayland, we're using a *fucktonne* of channels
06:03 skeggsb: which would probably also be why g86 is running out of space there i guess.. that shouldn't be fatal on its own, we fall back to a slower method of touching those structures if we run out of PRAMIN BAR space
06:07 skeggsb: does something in f26 cause more "normal" apps/widgets/whatever to be accelerated by chance?
06:07 skeggsb: (ie. why so many channels being used?)
06:09 airlied: skeggsb: maybe something with gtk
06:10 airlied: but I didn't think much changed, I should update something to f26 at some point
06:14 skeggsb: hmmm
06:17 skeggsb: airlied: it's related alright
06:17 skeggsb: the minute we go over 16MiB of PRAMIN usage on gm20x, we start getting the weird GPU faults people are reporting
06:17 skeggsb: the BAR is 32MiB, so not sure wtf is up there
06:18 skeggsb: i force-limited the size to 16MiB here, and can login OK (with the PRAMIN exhausted messages, but, as i said, that shouldn't actually matter)
06:20 skeggsb: i should plug in a g86 now and make sure it works as expected there
06:20 skeggsb: and probably add some kind of LRU to instmem mappings....
06:38 skeggsb: airlied: so, the g86 works, it hits the exhaustion thing too.. the slowdown is probably explained by any new page tables or channel structures etc having to be written to by an awfully slow method instead
06:38 skeggsb: i don't see the level of slowness the reporter mentions though
07:07 mangix: skeggsb: both wayland and xwayland have similar issues
07:07 mangix: earlier paste; https://paste.fedoraproject.org/paste/I-udg5iCrtJMDnheZWa2jw
08:11 mangix: btw this is some kind of change in wayland causing nouveau to lock up like this. f25 with the same kernel was fine
08:31 mangix: sometimes it crashes on logind, other times on xorg. weird.
10:10 tjaalton: i've got a bug report saying that mesa 12.0.x -> 17.0 upgrade broke blur on 7300GT, and is still broken on git. asked him to file it upstream
11:31 imirkin: tjaalton: correct thing to do :)
11:35 imirkin: tjaalton: of course "blur" isn't a thing - it's just some shader thing that broke which happens to hit the shader that does blur on some game...
11:35 imirkin: [probably]
11:36 imirkin: tjaalton: if you could have them provide an apitrace, which when replayed, reproduces the issue, that'd be super.
12:52 tjaalton: imirkin: it shows with unity, dunno how to reproduce with other means
12:53 karolherbst: tjaalton: apitrace
13:12 tarragon: omg!!
13:12 tarragon: does nouveau have this?? --> feral games
13:13 tarragon: oops I meant this --> http://phoronix.com/scan.php?page=news_item&px=Kabylake-Intel-GVT-g
13:21 mwk: tarragon: that's Intel-specific technology, so no
13:21 mwk: no way
13:22 tarragon: mmggghhhffuuuu!!!!
13:23 karolherbst: well there is always Vt-d
13:24 mwk: that's not exactly virtualization...
13:24 karolherbst: I know
13:24 karolherbst: but that's the farest you can come to it
13:26 karolherbst: uhm.. *clostest
13:27 karolherbst: who is comming to XDC by the way?
13:30 mupuf: me me me!
13:32 karolherbst: y
13:32 karolherbst: ay
13:32 karolherbst: I added myself to the list, I think the best would be to share a place to stay like we did last year?
13:34 mupuf: right
13:34 mupuf: well, I let's at least be in the same hotel so we can help shuttle people with the car we rented
13:39 karolherbst: ohh, you rented a car?
13:46 RSpliet: mupuf: I'll pass (like with SHA2017 :-( ), think I'll be best off investing that kind of money into a driver's license :-P
13:46 karolherbst: but yeah, staying at least in the same hotel sounds like a good idea to me. I guess we can figure out details later. I just need to start doing those bureaucratic things on my end, cause I have no (valid) travel pass....
13:47 mupuf: RSpliet: sure, except if you had a talk proposal, you could get funded to go
13:47 RSpliet: mupuf: I don't atm. And PhD is a bit more pressing than XDC unfortunately
13:47 mupuf: this is indeed the hard cold reality, yes :s
13:48 karolherbst: :/
13:48 RSpliet: Was hoping to get some fermi, reg alloc, insn sched stuff done perhaps, but I can only spend my time once :-)
13:48 RSpliet: So if things go well, perhaps next year. Otherwise things get easier if/when I move into decently paid work
13:48 mupuf: yep!
13:49 mupuf: and we could maybe meet at fosdem!
13:49 karolherbst: sounds like a plan
13:49 RSpliet: Who knows... That's about when I need to start stressing about write-ups and publications :-D
13:50 imirkin_: skeggsb: https://github.com/skeggsb/nouveau/commit/4f425acdeb471e7e7b1804cebd9ca606b94c9223 -- why didn't that get included in your pull?
13:50 imirkin_: it's affecting people with otherwise-working setups
13:54 karolherbst: imirkin_, pmoreau, hakzsam: XDC status on your side?
13:55 hakzsam: no idea
14:11 imirkin_: karolherbst: huh?
14:11 imirkin_: what status?
14:12 mupuf: imirkin_: I guess he is asking wether you plan on attending or not
14:15 karolherbst: exactly
14:42 pmoreau: karolherbst: Not coming as I have too much stuff to do between labs and papers submissions.
14:45 karolherbst: pmoreau: ack
15:14 rhyskidd_: I'm considering the trip to XDC this time, given closer for me than recent years
16:32 tjaalton: karolherbst: apitrace of the session?
16:32 tjaalton: basically compiz
16:39 karolherbst: no, of the application
16:40 karolherbst: or does compiz produce this issue?
16:40 karolherbst: usually it's the application itself doing OpenGL stuff
16:41 imirkin_: tjaalton: well, so here's the deal - i need to reproduce the issue. you can be sure i'm not about to install compiz. so apitrace works nicely.
16:41 imirkin_: (if it's compiz that's failing - if it's a GL application then i'd need that GL application)
16:44 tjaalton: karolherbst: it shows with transparent backgrounds when blur effect is enabled, no other reproducer so far
16:49 tjaalton: imirkin_: yeah we'll see..
16:50 tjaalton: is 8600gt close enough to 7300gt?
16:51 tjaalton: because i have the former somewhere
16:57 imirkin_: tjaalton: nope
16:57 imirkin_: 7300gt is nv4x, while 8600gt is g8x/g9x
16:57 imirkin_: there was a *major* architectural change between those
16:58 imirkin_: and they use different gallium driver backends
16:58 imirkin_: (nv30 vs nv50 backends)
16:58 imirkin_: tjaalton: perhaps also worth mentioning that the nv30 backend sucks
16:58 imirkin_: that doesn't mean we don't try, but ... limited resources and all
17:02 tjaalton: imirkin_: right, okay
17:02 imirkin_: tjaalton: you can take the apitrace on any gpu though...
17:03 imirkin_: HOWEVER you'd have to limit mesa to the features available on nv4x
17:03 imirkin_: which may not be an extremely easy thing to do =/
17:04 tjaalton: ah, well i'm not sure where my card is, so :)
17:05 imirkin_: basically 7300gt is a DX9 part, while 8600gt is a DX10 part
17:06 imirkin_: obviously if the user can do a bisect and find the responsible change, that would also go a long ways to figuring out the issue
17:07 imirkin_: [probably a dozen bisection steps]
17:34 tjaalton: right
19:54 pmoreau: After using the Intel chip as main card on this laptop, I had forgotten how easily Nouveau would lockup with KDE; it could be due to something else but the lockup occured during a window resizing effect.
19:55 pmoreau: And I had also forgotten how NVIDIA would overscale the interface on HiDPI… :-/
20:00 imirkin_: moral of the story - use nouveau ^ kde :)
20:01 karolherbst: pmoreau: :D
20:02 pmoreau: Well, it was working fine as long as I was on the integrated chip. But today, probably after updating to 4.12(.3), it stopped working…
20:02 karolherbst: pmoreau: guess why I always suggest using intel even on a desktop if somebody mentions they have an intel gpu
20:03 pmoreau: On the same hand, I lost keyboard support, I have no idea how as I kept the same kernel config as usual
20:03 karolherbst: pmoreau: you still need to _press_ the keys, even using intel
20:03 pmoreau: O_O
23:47 skeggsb: mangix: yeah, i know *what* the issue is, i'm trying to find the root cause so i can fix it properly. it's not caused by a driver change, but something in f26 is using the gpu a bit differently and triggering a bug
23:47 skeggsb: imirkin_: oversight, i'll fix that
23:48 imirkin: ok cool. just wanted to make sure you weren't excluding it on purpose.
23:48 imirkin: the other thing with not creating heads is wtvr, only known affected chip is GP108 which isn't supported officially yet
23:48 skeggsb: nope.. just single-mindedly trying to fix all these horrific issues that have popped up and pulling me away from other stuff :P
23:49 imirkin: i assume you saw the new DP errors?
23:49 skeggsb: yep
23:49 imirkin: fun, right? :)
23:49 skeggsb:needs more time in the day, or a clone
23:49 imirkin: everything seems to be crumbling at the same time... not sure what happened
23:50 skeggsb: definitely don't get paid enough for this shit hehe ;)
23:50 imirkin: well - having more people full time on nouveau would sure be great
23:50 imirkin: us volunteers try to help, but it's hard to keep up
23:50 skeggsb: indeed
23:50 imirkin: so we stick to our little areas of the world
23:51 airlied: skeggsb: I don't think we can fix whatever changed in f26, I assume it was deliberate change
23:51 skeggsb: airlied: i can fix the driver
23:52 airlied: yup just probably not worroying so much about root causing :)
23:52 skeggsb: oh, by root cause i mean: why instmem mappings >16MiB don't work
23:52 airlied: oh sorry, yeah that is a real problem :)
23:52 imirkin: 32MB bar advertised but only first 16MB work?
23:52 imirkin: that's nice.
23:52 airlied: can you make the binary use > 16MB?
23:53 skeggsb: imirkin: yep
23:53 imirkin: someone was off-by-one in the pci config
23:53 skeggsb: airlied: presumably, i will try that at some point, but still working through ruling out some stupid driver bug in mmu mapping or bar setup etc