00:24imirkin: karolherbst: RT_HORIZ is set in nvc0_validate_fb.
00:24imirkin: karolherbst: and the whole glReadPixels thing is the thing i said was broken with MSAA visuals
00:25imirkin: so like glReadPixels isn't aware of MSAA. and so if you try to do it on a MSAA fb, then you get a GL_INVALID_OPERATION. makes sense, right?
00:25imirkin: but no, if you have a MSAA visual, then the fb that's displayed is implicitly resolved
00:25imirkin: and so when you do a glReadPixels, you're supposed to do an implicit resolve
00:25imirkin: we don't handle that properly.
00:26imirkin: [resolve == operation that takes a MSAA fb and comes up with a single color per pixel out of all the samples. in the case of stencil and other integer buffers, that means "take the value for sample 0"]
00:27imirkin: [and to all the people sitting around laughing and saying, "ha, this guy doesn't know shit about opengl" -- please speak up and correct me.]
00:34airlied: I'm laughing, but it sounds correct :-)
00:36imirkin: airlied: in case you care to laugh some more: https://www.youtube.com/watch?v=5FFRoYhTJQQ
02:01Llmiseyhaa: Good evening folks
02:04Llmiseyhaa: I have been working through various troubleshooting and FAQs but I still have a persistent problem with my system hard locking... strangely, particularly when I go to a map site like maps.google.com. Both firefox and chrome. Sometimes I can SSH in and kill chrome (or X) and get things moving again, other times not.
02:04Llmiseyhaa: GF108 on a GT730 board
02:04gnarface: got swap?
02:05Llmiseyhaa: 16GB of swap, 16GB of main memory
02:05gnarface: hmm. i'm not sure if it's a known issue or not. what kernel & mesa versions?
02:06gnarface: sometimes newer is better. sometimes not.
02:07Llmiseyhaa: 4.12.10, though I've had it off and on since 4.10 or earlier
02:07Llmiseyhaa: mesa 17.0.6
02:07gnarface: well that's all pretty new
02:07Llmiseyhaa: xorg-server 1.19.3, running glamor though I had the same issue with the nouveau ddi
02:07Llmiseyhaa: err, ddx
02:07Llmiseyhaa: that's the relevant kernel messages, including bringup for the gf108
02:08Llmiseyhaa: Ryzen 7 1700, Corsair memory in stock speed (not X-AMP), half of my memory is in 8x1GB hugepages that I use for a Windows VM, and I have an AMD GPU that I pass through to Windows. Other than vfio-pci though nothing under Linux touches that and I'm booting UEFI without CSM so while both are brought up during boot, Linux only ever does anything with the GF108.
02:10Llmiseyhaa: I haven't run into swap to my knowledge, though I set it up as back in the day like kernel 2.2 or something the Linux kernel did not care for having no swap and I wanted to have the option of suspend-to-disk. Have since decided not to use it, but, eh, storage is cheap.
02:11Llmiseyhaa: Thank you for the replies, by the way. I didn't see any known bugs that covered this.
02:11gnarface: well i'm sorry, i've got nothing to help
02:11Llmiseyhaa: If I missed one, I certainly apologize.
02:11gnarface: i can guess it could be a memory leak or other such problem with mesa though
02:12gnarface: 17.x is pretty new and chrome and firefox both use opengl-accelerated rendering by default
02:12Llmiseyhaa: Hrm. Maybe, but it seems to happen just as easily right after I boot as later.
02:13gnarface: i wonder if it would happen with any opengl program at the same speed/rate
02:13gnarface: i wonder if it would not happen when running something else entirely non-opengl
02:13gnarface: the only fixes i can suggest are deductive
02:13gnarface: i guess that means they're not really fixes, just tests
02:13Llmiseyhaa: Well, I've tried setting chrome to disable OpenGL via commandline; not sure if it does what it says though or if it lies to me.
02:14Llmiseyhaa: That gist would seem to -- though I'm not discounting your theories, and I appreciate them -- some form of driver or card error. It always starts with a "DATA_ERROR" of the type "INVALID_BITFIELD". Often channel 4, though I'm not sure if that's just coincidence or not.
02:14gnarface: i would think there'd be a noticable change in the amount of ram it takes to render a page
02:15gnarface: i don't know enough about the driver to know what that means, but it does sound suspicious
02:15Llmiseyhaa: No segfaults either since I got a stepping 1 Ryzen off of AMD RMA
02:16Llmiseyhaa: and no other messages in kernel logs or dmesg that would indicate any hardware issues.
02:16Llmiseyhaa: (I keep suspecting bum RAM, but I'd expect to see other issues in userland there.)
02:16gnarface: data error, invalid bitfield... what could that mean? it gets passed the graphical data with an alpha-channel it's not expecting? something like that?
02:17gnarface: if you could trigger it more reliably, that would help narrow the issue
02:17Llmiseyhaa: Oh, I can. Every time I try to go to a map page, it may happen immediately or it may happen after a bit.
02:17gnarface: what's the browser doing usually when it locks up? is it always on a page with ads, or video?
02:17Llmiseyhaa: Even embedded OpenStreetMap stuff. I've literally booted, relaunched my browser, and had it.
02:17gnarface: oh right, you said maps
02:18Llmiseyhaa: If I by some chance manage to load them, the moment I click and drag in one, it locks. Cursor still moves, but I can't interact with anything strangely.
02:18gnarface: now that's odd
02:18gnarface: using desktop compositing?
02:18Llmiseyhaa: Yeah, XFCE
02:18Llmiseyhaa: Hadn't thought to disable it. Let me go do that now.
02:19gnarface: i'd try disabling desktop compositing AND opengl in firefox, then aggressively see if maps would still lock it up
02:19gnarface: then if they don't, i'd run glxgears or some gl screensavers of some sort until it locked up
02:19gnarface: and if that didn't lock it up, i'd just never turn on compositing again
02:19Llmiseyhaa: Weirdly I've not actually seen any GL screensaver lock. o..O
02:20Llmiseyhaa: I use the one that shows a car engine because I'm a wrench wench when I'm not working on computers.
02:20gnarface: the guys who actually know stuff are usually in here earlier in the day
02:20Llmiseyhaa: Holy shit I turned off compositing and my window movements got slower. o..O
02:20Llmiseyhaa: I... did not expect that. Well, wish me luck.
02:20gnarface: good luck
02:20gnarface: oh, yea compositing smooths stuff out a bit
02:20gnarface: but how much slower is it?
02:21Llmiseyhaa: Drastically slower.
02:21gnarface: if it's TOO much slower, it might be a sign of something else wrong
02:21Llmiseyhaa: I am running the card at PCIe x4, and I'm in the glamor DDX
02:21Llmiseyhaa: and firefox just crashed, no nouveau errors but firefox died.
02:21Llmiseyhaa: switching to nouveau DDX
02:21gnarface: which distro is this you're using?
02:22gnarface: doing anything crazy with the compilation flags? compile the kernel or mesa with -O3 or anything edgy like that?
02:22gnarface: sometimes stuff isn't stable above -O2
02:24gnarface: i'd be curious if it still happens on something older, like devuan jessie
02:25gnarface: you might just have run into a new bug. not a lot of people are using all this bleeding edge software with nouveau
02:26frobos: had the same problems with a 660ti and random system hangs
02:27frobos: dmesg didn't help
02:27gnarface: i don't know anything at all about glamour
02:27frobos: the answer I got is that nouveau can't track it down without nvidia's full docs
02:28frobos: I was on gentoo as well, compiling all with O2 and many software versions
02:28frobos: tried reclocking as well
02:28frobos: nothing solved the problem
02:29Llmiseyhaa: Nope. -O2
02:30Llmiseyhaa: and I can't run anything older because Ryzen 7
02:30Llmiseyhaa: Anyway, on the nouveau ddx and everything is snappier than I remember it being, well, pretty much ever. Guess the card isn't that capable of doing 2x 1440p screens with compositing. I am asking a lot of an old GF108.
02:31Llmiseyhaa: Though before folks suggest newer: I can only fit a single slot card for my Linux video
02:31frobos: yea, with nvidia for full support you will need proprietary driver
02:31frobos: this nugget would save me hours of bug hunting
02:31duttasankha: can someone help me about the purpose of the code inside nvkm/engine/gr?
02:34Llmiseyhaa: Well, confirmed; I still get the crash with compositing off and using the nouveau ddx
02:35Llmiseyhaa: Unfortunately I was not able to get it to sync the logs to disk before rebooting so I can't be certain of the error messages but every time I have borrowed my wife's computer to SSH in and reboot, I've had the same messages.
02:36gnarface: maybe imirkin knows something about it
02:36Llmiseyhaa: Notably, while the rodent doesn't lock up the keyboard handler in X does. o..O
02:36gnarface: you could set up network logging
02:36Llmiseyhaa: (At least I presume it's in X, because I can't even turn off numlock.)
02:36Llmiseyhaa: I could. We do have a home server. I've simply been lazy.
02:37Llmiseyhaa: I wish I could get Intel graphics, but being an AMD Ryzen that's pretty impossible.
02:37duttasankha: gnarface: maybe imirkin knows something about it ....was that for me?
02:37gnarface: sorry, no duttasankha it wasn't intended to be, but coincidentally it also probably applies to you
02:39duttasankha: no worries..thanks...and sorry to coming in between the conversation
02:39Llmiseyhaa: So failing that, when I go water cooling I'll likely modify some dual-DVI AMD GPU board to fit in a single slot with a water block on it. Until then, though, I've got to keep this working. Though I've been pondering a GT1030... GP108 is rather newer.
02:39Llmiseyhaa: It's single slot, two DVI outputs, etc so it might do me. Both my monitors are dual-link DVI _only_. Yeah... annoying and weird, but... is what it is.
02:40Llmiseyhaa: How's the Pascal support doing, does anyone know?
02:41rhyskidd: Llmiseyhaa: Pascal support is limited; without more on your desired use case, it's probably not what you want
02:42rhyskidd: Absence of acceleration means cards are *slow*, even if you aren't affected by chip specific problems nouveau has
02:42Llmiseyhaa: Two 1440p displays and basic desktop stuff.
02:42Llmiseyhaa: All of my games get run under Windows; good to know before I go invest in a GP108.
02:42rhyskidd: Laptop? OPTIMUS?
02:42Llmiseyhaa: Ryzen 7 1700
02:42rhyskidd: I think we only have basic display output working for GP108, no accel or others
02:43rhyskidd: Absence of redistributable firmware for the GP108 hampers us
02:43Llmiseyhaa: Yeah, that won't do me and I'm not sure I trust the nVidia drivers on a system meant for PCIe passthrough.
02:44rhyskidd:checks again for GP108 in linux-firmware.git ... not there
02:47Llmiseyhaa: Hrm. Only vaguely related question, but should the GF108 be as... struggling as it is driving 2x 1440p displays for basic desktop usage (browser, SSH terminals, chat apps, etc)
02:47gnarface: maybe, if reclocking isn't working
02:47Llmiseyhaa: With the caveat that I can only run it at PCIe x4, but it's still slower than I remember desktop apps... ooooooh.
02:47gnarface: i thought i heard it was for those cards, but maybe i'm wrong
02:48Llmiseyhaa: How can I tell? It does hover right at 45C so you might be right about that.
02:48gnarface: i'm not sure how to tell
02:48gnarface: maybe with envytools?
02:48gnarface: with the proprietary drivers you can just see it in nvidia-settings
02:49Llmiseyhaa: ooooh, may have found it
02:50Llmiseyhaa: well, looking at /sys/kernel/debug/dri/0/pstate
02:50Llmiseyhaa: I've got four listed... 03, 07, 0f, and AC.
02:51Llmiseyhaa: judging from the listing, I'm on 07, because 07 and AC are the same. So 405MHz core, 324MHz memory
02:52Llmiseyhaa: aw bugger, nope, no reclocking on GF108
02:52Llmiseyhaa: "Function not implemented" when trying to write to the pstate file
02:53Llmiseyhaa: hey, looks like Pascal is (or already has) gotten 2D/3D accel in 4.12 (=
02:55gnarface: honestly that's still a really nice card for a multi-headed linux desktop, with the proprietary drivers. i hear ya on the security concern though.
02:55Llmiseyhaa: Oh, the current proprietary drivers work?
02:55Llmiseyhaa: I thought GF108 was so old it wouldn't do it
02:56gnarface: you said it was a 780?
02:56Llmiseyhaa: GT730, GF108 chip, NVC0 family
02:56gnarface: current drivers still support back to 500 i think
02:56gnarface: definitely 600, maybe also 500
02:57gnarface: you're right they'll roll off support eventually, but i'd guess you have a couple years before that happens
02:58Llmiseyhaa: Well I'm not so worried about the security (I mean I am but I use google fi, have a google phone, etc so I'm already snooped so much)... it's more
02:58Llmiseyhaa: PCI passthrough rigs are already touchy
02:58Llmiseyhaa: I'm afraid the nVidia drivers will do something that screws up my PCI passthrough
02:58Llmiseyhaa: and yeah, I know, I'm buying myself trouble with that but hey
03:01gnarface: the other thing that the nvidia proprietary drivers drop the ball on is xrandr layout syntax
03:02Llmiseyhaa: Yeah, that I'm not too worried about as long as I can get my screens side by side.
03:02Llmiseyhaa: well, and these things have corrupt bum (I know, I know) EDIDs
03:02gnarface: if you were doing something too fancy or cute with your multi-monitor layout, you may end up having to re-do it for the more limited feature set
03:02Llmiseyhaa: But nah I'm just doing side by side
03:02gnarface: side-by-side with the first one on the left should not be a problem
03:02Llmiseyhaa: yup that's how I run 'em
03:08Llmiseyhaa: updating to 4.13.5 while I'm at this.
03:17imirkin: Llmiseyhaa: what's the quick summary of your issue? random hangs with nouveau when accessing maps.google.com?
03:17gnarface: in chrome AND firefox, with or without opengl rendering and compositing in xfce
03:18imirkin: anything interesting in dmesg?
03:18imirkin: Oct 12 18:23:46 gryphon kernel: nouveau 0000:21:00.0: X: nv50cal_space: -16
03:19gnarface: "DATA_ERROR" of the type "INVALID_BITFIELD". Often channel 4, though I'm not sure if that's just coincidence or not.
03:19imirkin: that means "congratulations, you have run out of vram"
03:19Llmiseyhaa: Well that makes sense.
03:19Llmiseyhaa: 2x 1440p displays.
03:19imirkin: the fact that this happens *after* the various data errors is definitely rather odd.
03:20imirkin: 4GB of vram is quite a bit, too
03:20imirkin: so i'm not sure how this would happen
03:20imirkin: btw... wtf kind of board is this? 21:00.0 for the pci device id?
03:20Llmiseyhaa: Well, maybe maps just request a gigantic surface?
03:21Llmiseyhaa: Ryzen 7 1700
03:21Llmiseyhaa: MSI x370 SLI Plus
03:21gnarface:is so jealous
03:21imirkin: are there 21 pcie slots?
03:21Llmiseyhaa: But lots of onboard stuff and numbering is weird
03:21Llmiseyhaa: because there's a bunch of lanes off the CPU then a bunch of lanes off the 'northbridge'
03:21imirkin: i guess each onboard thing, yeah
03:22Llmiseyhaa: I'm running this off the northbridge since any cards I put in my two CPU powered slots get stuck in the same IOMMU group
03:22Llmiseyhaa:shakes fist at MSI firmware devs or whoever's responsible for THAT map.
03:23imirkin: well, this is weird
03:24imirkin: Oct 12 18:23:42 gryphon kernel: nouveau 0000:21:00.0: gr: DATA_ERROR 0000000c [INVALID_BITFIELD] ch 4 [00ff941000 X] subc 0 class 9197 mthd 0fc0 data 3f800000
03:24imirkin: that's inside of MSAA_MASK
03:24imirkin: while that's clearly a 1.0 float value
03:24imirkin: [which would not be appropriate for the MSAA_MASK]
03:25imirkin: this points to some kind of grctx restore failure
03:25imirkin: skeggsb: what do you make of it?
03:25imirkin: that happens before any "X: nv50cal_space: -16" messages
03:25imirkin: and then 4s later, total fail
03:26imirkin: i wonder if there's some kind of grctx restore failure condition under vram pressure
03:26Llmiseyhaa: What's really strange (to me) is the cursor never dies.
03:26Llmiseyhaa: I can move the rodent and the cursor follows but nothing responds at all.
03:26imirkin: that's normal
03:26Llmiseyhaa: Aaaaah, just seemed really weird to me. Sorry. (=
03:26imirkin: well, cursor position is just updated directly
03:26imirkin: it's composited in hardware
03:27imirkin: when you see a hang, your system is actually totally fine
03:27imirkin: with the minor small inconvenience of not getting anymore screen updates
03:27Llmiseyhaa: Oh, I know. I can SSH in and sometimes if I kill X (or chrome/firefox) I can recover it but sometimes not.
03:30Llmiseyhaa: Sometimes firefox just crashes, other times lockup I can recover over SSH, and finally there are times I can't recover it... X is dead, kill -9, not in ps aux... but display still shows the same thing
03:31imirkin: are you using the modesetting ddx?
03:31imirkin: or nouveau?
03:31Llmiseyhaa: I've tried both
03:31Llmiseyhaa: modesetting ddx with glamor and nouveau ddx
03:31imirkin: nouveau definitely is going to handle funny cases much better
03:31imirkin: i'd strongly advise against using glamor with nouveau
03:32Llmiseyhaa: Ok, at least somewhere on the page they suggested using the modesetting ddx + glamor for newer cards
03:32skeggsb: imirkin: pretty sure context switching doesn't go through the class interface, and restores the "strands" instead, so they wouldn't trigger class errors
03:32Llmiseyhaa: But I'm good with whichever
03:32imirkin: i guess they would advise to use glamor. but i would advise to not use it :)
03:33imirkin: skeggsb: well, i just mean if some bit of context got restored "wrong"
03:33imirkin: skeggsb: so that when process the "next" fifo command it lost its place
03:33skeggsb: yes, but those errors are triggered in response to decoding methods, which means they came through the push buffer somehow
03:33imirkin: skeggsb: i guess that'd be a FIFO "concern", not a GRAPH concern...
03:33Llmiseyhaa: I did have some cases where the nouveau ddx would repaint the entire contents of the screensaver that was stopped minutes ago over the screen then anything else would just update over top of that so you had to go through each window to get it back.
03:34Llmiseyhaa: Both my wife and myself have had that particular bug on the nouveau ddx with a GF108. Minor though.
03:34imirkin: Llmiseyhaa: the nouveau ddx is hardly perfect. but what it does do is error handling.
03:34Llmiseyhaa: I'm not trying to argue, I apologize if it came across that way.
03:34Llmiseyhaa: I was more trying to explain myself there, is all.
03:34imirkin: imho that's a very important quality in an xorg ddx. others don't agree.
03:36imirkin: skeggsb: i guess some kind of multithreading thing could trigger a similar problem. that's the only thing i can think of for how you might end up with a 1.0 in MSAA_MASK. the next theory goes along the lines of memory corruption.
03:36imirkin: skeggsb: speaking of... how's the mt stuff going? :)
03:37imirkin: Llmiseyhaa: btw, i lied. "X: nv50cal_space: -16" is actually indicative of running out of pushbuf space (sorta)
03:37skeggsb: imirkin: sidelined for the moment...
03:37imirkin: this happens for two reasons - #1 - gpu has hung, #2 - you're submitting commands *really* fast
03:38imirkin: skeggsb: =/
03:42Llmiseyhaa: ok, well, for now BRB gonna try the nvidia binary drivers. Thanks for the help folks
03:59Llmiseyhaa: well, know this isn't quite the channel for it but nvidia binary drivers work and don't kill my PCI passthrough
04:00Llmiseyhaa: for the time being I'll keep it set up where I can swap back and forth between them and try nouveau now and again, thanks for the help guys. If anyone thinks of stuff they'd like me to try and/or log, I will (=
08:23giovdav: some one can help me? I have some troubles with nouveau on Centos 7.4 with KDE4
08:30karolherbst: imirkin: yeah makes kind of sense, because glReadPixels reads the Stencil buffer and the values look the same with apitrace, where I suppose it does a texture view or something like that and not glReadPixels
09:01karolherbst: imirkin: but in the end it actually reduces my confusion, because now my observation starts to make sense
09:16karolherbst: giovdav: uhh, that's like ancient software. What GPU do you have?
09:16karolherbst: giovdav: bugfixes are usually not backported to _very_ old software
09:17giovdav: karolherbst: ug :( i have a Quadro K600
09:17karolherbst: okay, so you want a kernel like 4.12
09:17karolherbst: and mesa-17.1 at least
09:17giovdav: karolherbst: so your advice is to update the kernel?
09:18karolherbst: my advice is to update everything
09:18giovdav: ahahah :D
09:19giovdav: yes could be a good solution! :)
09:20karolherbst: I have no clue what the code is on centos 7.4
09:20karolherbst: it might be all recent enough and maybe not
09:20karolherbst: who knows
09:20karolherbst: skeggsb might know it :D
09:23karolherbst: airlied: yeah, but I was more thinking about the kernel side
09:23karolherbst: or more worries about that
09:24giovdav: i'm searching about the kernel update on Centos.. and what about the proprietary driver? someone have some experiences on it?
09:24karolherbst: I saw it has pascal support, but no idea what the actual source code is
09:28karolherbst: giovdav: but what are your troubles explicitly? Maybe it is one of those which isn't fixed yet
09:30giovdav: karolherbst: after a computer hibernation my desktop hang/freeze .. and xorg appear dead .. -.-"
09:30giovdav: karolherbst: i also have some glich in daily use .. some pixels are not displayed well ..
09:31karolherbst: pmoreau hat at some point working live images with recent nouveau code, no idea what the status is here
09:32pmoreau: karolherbst: They are still being compiled every week with the latest version (except when they break of course) :-D
09:32karolherbst: giovdav: so you might try those
09:32airlied: tge centos kernel makefilechas a drm version in it
09:32karolherbst: pmoreau: is it possible to install like KDE 4 on those?
09:33pmoreau: I don’t think there is enough free space left on the images for that.
09:37karolherbst: pmoreau: I meant on the live system. It's usually stored in RAM
09:37karolherbst: I hope it doesn't take too much space though
09:40pmoreau: True it is usually stored in RAM, but installing more than 10–50MB (of the top of my head) results in some error about not enough space, or failed to write to device. I haven’t investigated it.
09:41karolherbst: I see
12:27karolherbst: giovdav: in any case, it would be nice to get some info out of dmesg or the X logs or anything. Maybe it is a known issue, maybe it is something new, maybe somebody can reproduce this and we could try to fix it
12:28aphirst: btw i can't remember which username i was speaking to the other day about the HDMI audio thing, but i saw in the mailing list thread that they'd "think about it" and get affected users to test it as and when ready
12:29aphirst: so I just wanted to say that I'm willing to do that, and am (almost) always online
12:30giovdav: karolherbst there was nothing
12:30karolherbst: giovdav: :/
12:31giovdav: i have read now about the improvements of nouveau in the 4.3 kernel
12:31karolherbst: giovdav: idea: next time ssh into the machine and try to kill X
12:31giovdav: by the way for now i have installed the proprietary driver
12:31karolherbst: giovdav: on CentOs I wouldn't rely on kernel versions at all. it might be that you have a 4.2 kernel with 4.10 drm subsystem or something
12:33karolherbst: giovdav: can you run uname -r?
12:58giovdav: karolherbst: 3.10.0-693.2.2.el7.x86_64
13:19imirkin: giovdav: kernel 3.10 was released June 30, 2013. believe it or not, but there have been one or two fixes in the past 4 years.
13:19karolherbst: imirkin: CentOs ;)
13:19karolherbst: no, it is
13:19karolherbst: they have pascal support
13:19imirkin: but who knows how
13:19karolherbst: but usually they rebase new code on 3.10
13:20karolherbst: and stay with 3.10 like forever until there is a new major release
13:20karolherbst: I wouldn't be surprised if there is the 4.10 drm code in it or so
13:21karolherbst: airlied said that the exact drm version is in one of the files in the sources, but I am too busy right now to look it up
14:34giovdav: yes imirkin you have reason, i'm thinking to update kernel with elrepo
14:35imirkin_: that said, my recollection is that KDE + nouveau = fail, so perhaps that won't help
14:36imirkin_: dunno what other people's experience is. i never use KDE or GNOME or any of that stuff.
14:37karolherbst_: well with KDE 4 it shouldn't be as bad though
14:52gnarface: anything with compositing on by default is gonna be like punching yourself right in the nuts
14:52gnarface: i can't imagine it'd still be a problem if you can turn it off though
14:53gnarface: (which i think is possible in KDE but not in Gnome anymore? not sure)
15:04loonycyborg: nouveau is used by default in fedora, so they'd have to make it work
15:04loonycyborg: at least on newer cards
15:11karolherbst: loonycyborg: and who is paying them to do so ;) just asking about why they _have_to_ make it work
15:11loonycyborg: well fedora is base for red hat linux
15:12loonycyborg: so the answer would be "Red Hat" :P
15:12karolherbst: okay let me rephrase: who of the users is paying
15:13karolherbst: it is all fun and games until somebody starts to say somebody "has to" get something work, then it gets difficult
15:13karolherbst: if you want somebody to have to getting it to work: pay, if you can't pay, then help out yourself
15:14loonycyborg: I mean they'd have to either make nouveau+gnome work or lose support for nvidia cards
15:14loonycyborg: since they're not using blob by default
15:15karolherbst: no, they don't "have to". It would be nice it they did and they are also working on it and have paid devs who do this, but technically they don't "have to". I am mainly complaining about the term "have to" and what it's implicit message here is
15:15loonycyborg: anyway, I'm actually running fedora+gnome with nouveau on other pc
15:16loonycyborg: and it works nicely once it's using fermi based card
15:16karolherbst: yeah and most here are actually interested in fixing bugs
15:16loonycyborg: before that there was geforce 6800GS and it broke horribly with updates
15:16loonycyborg: both with nouveau and nvidia-drivers
15:17karolherbst: uhh, makes sense
15:17karolherbst: I guess they started to use advanced GL features nobody cares about on a 6800GS
15:18loonycyborg: I didn't have much luck running kde+nouveau on this gentoo desktop though
15:18karolherbst: I hope I will be able to build some reliable nouveau CI, so that we actually are able to prevent regressions, because this is something we don't do for nouveau right now
15:18loonycyborg: it works basically but there are occasional hangs and gpu lockups
15:19karolherbst: even on 4.13 with mesa 17.2?
15:19karolherbst: with 4.13 I mean the kernel, not kde4
15:19loonycyborg: I don't remember which exact versions I used last time
15:25peterius: for anyone who is interested, those 10 second hangs were not because of any of the firmware things, they were, I think, because of tracing in the kernel
15:25peterius: I saw the trace_printk warnings in dmesg but didn't think that could cause such hangs but I guess somehow either nouveau or i915 interacts badly with kernel tracing
15:25peterius: at least on my card
19:25karolherbst: imirkin_: does the code in nvc0_miptree_transfer_map needs to be adjusted for that implicit resolve or at some earlier point?
19:25imirkin_: no, that sounds right
19:25imirkin_: and transfer_unmap
19:27karolherbst: the samples=2 case is fun, because half of the read out pixels are correct
19:28imirkin_: iirc i tried to fix it up
19:28imirkin_: but it was non-trivial.
19:28imirkin_: and felt unimportant at the time, so i gave up
19:28karolherbst: mhhh, wondering if I actually need to put that stuff into nve4_m2mf_transfer_rect or not
19:28karolherbst: feels like the right place
19:29karolherbst: fun fact though: nvidia uses the 2X1_D3D ms_mode
19:30karolherbst: mhh, I am wondering
19:32imirkin_: like i said, it wasn't a trivial fix
19:32imirkin_: i went around in circles thinking "oh, is this the right place to put it"
19:33karolherbst: I made a diff from the mmt traces and there it looks rather trivial, now I am wondering if we actually miss to set some stuff as well
19:42karolherbst: imirkin_: do you know why nvidia uses those weirdo pitch values? like 0xfffffc28
19:43karolherbst: or is it the way how the handle mirrored stuff?
20:04imirkin_: pitch values?
20:07karolherbst: eg: GK104_COPY.DST_PITCH