04:10 rhyskidd: any reviewers for TU106 / RTX 2070 envytools support? https://github.com/envytools/envytools/pull/173
04:10 HdkR: =o
04:11 rhyskidd: the travis-ci warning is incorrect, the ci was having backend problems yesterday
04:14 rhyskidd: imirkin: thanks
04:14 imirkin: np
04:17 rhyskidd: i've got a few other small tweaks and doc fixes coming, cleaning up patches from code written on the flight
04:17 rhyskidd: little nits that had been annoying for a while. some dedicated time let them be worked on
04:29 imirkin: skeggsb: any idea about https://bugs.freedesktop.org/show_bug.cgi?id=108500 ? very odd...
04:29 imirkin: looks like MCP89 uses the same mmu as g84
04:48 imirkin: skeggsb: looks like nv50_vmm_valid will reject compressed allocations in stolen vram? i don't think that's right...
04:52 imirkin: skeggsb: also i don't see anywhere where mmu->func->vmm.global might get set
07:19 rhyskidd: karolherbst,skeggsb: any comments on this Pascal, Volta and Turing compute wip series? https://github.com/envytools/envytools/compare/master...Echelon9:feature/compute-improvements
07:20 rhyskidd: i'm also going back and adding some Maxwell and earlier compute methods, which will be a better base for the volta and turing changes (eg some undocumented methods are now deprecated)
07:28 masterboy: Hi guys, could you help me - the driver hangs my system after minimal use. I am using NV4C here is the dmesg https://paste.gnome.org/pqgx9isye
07:28 gnarface: nv4c/
07:28 gnarface: ?
07:28 masterboy: i set aside 256mb memory for it
07:28 masterboy: hi gnarface :) yes
07:28 masterboy: ubuntu shows me that it is nv4c :)
07:28 masterboy: the driver was unusable with 64mb of shared ram but 256 makes it work for a while...
07:29 masterboy: i updated the bios to the latest 2006 one :)
07:31 masterboy: tell me if any other logs should i provide :)
07:33 masterboy: it is a amd cpu with nvidia chipset-integrated gpu
07:33 masterboy: athlon II 2.9ghz ;)
07:35 masterboy: btw i am using this system now :) It seems if i load more programs the gpu will crash
07:41 masterboy: any idea what those errors mean?
07:43 gnarface: you mean this? nouveau 0000:00:0d.0: bus: MMIO write of 010a0001 FAULT at 00b010
07:43 masterboy: yes :)
07:43 gnarface: got a picture of the screen corruption?
07:44 gnarface: i don't know if it's bad software or bad hardware, but you can sometimes tell by the type of screen corruption
07:44 masterboy: I can photo it but I would call it snow. I can draw it too :)
07:45 gnarface: certain types of screen corruption are indicative of bad ram. does it look like letter glyphs are corrupted, even on the bios or POST boot screen?
07:45 gnarface: if it's a problem with the driver, it won't be able to affect the bios screen or the early boot screens
07:45 masterboy: ok i will hang the system and reboot and show the picture. no everything is fine, even now. until i load some more programs
07:46 gnarface: bad ram would also fit that pattern
07:46 gnarface: it won't all go bad at once
07:46 gnarface: just a little bit
07:46 gnarface: so the quickest way to find the bad spot is to use it all
07:46 masterboy: i could try memtest in grub ubuntu?
07:47 gnarface: that would test the system dram but i don't know if it's complaining about video ram here or not
07:47 gnarface: and memtest won't test the video ram
07:47 gnarface: so it'd be useless for that
07:47 gnarface: still, couldn't hurt
07:47 masterboy: gnarface, it is an integrated gpu it has only ddr2 ram
07:47 gnarface: ooooh, right
07:47 gnarface: hmm
07:47 gnarface: well
07:48 gnarface: intel integrated gpus do that, but i'm not actually sure the nvidia ones all do
07:48 gnarface: it might have it's own ram
07:48 gnarface: either way, it won't hurt to run memtest on it unless it's already damaged
07:49 masterboy: it does not - i can see the total ram is 256 less :)
07:49 masterboy: thanks i will try
07:49 masterboy: and get back to you :)
08:42 masterboy: hi again i put the pictures here https://drive.google.com/open?id=1tdmM-WKD69umDdvdqTTAUI03zQSVsJL_
08:42 masterboy: i hope the link works gnarface :)
08:42 masterboy: the ram is fine according to memtest
08:44 gnarface: are you sure it doesn't have like maybe 1 or 2MB dedicated ram?
08:45 gnarface: oh
08:45 masterboy: i will google it now. What about the pictures?
08:45 gnarface: i just realized, memtest probably wouldn't test the part of the ram that is dedicated to the video card in the bios
08:46 gnarface: you'd have a better chance of memtest finding a bad spot if you set the gpu to use less ram i think...
08:46 gnarface: because the first picture definitely looks like bad ram
08:46 gnarface: second one does too really
08:47 gnarface: but i think in theory even the compositor or window manager could corrupt the screen this way
08:47 gnarface: i don't really know how to know for sure without seeing a bios screen also corrupted
08:47 masterboy: bios screen is fine
08:47 masterboy: i set 32 video ram and tested then it is ok
08:47 masterboy: [ 1.906130] nouveau 0000:00:0d.0: NVIDIA C61 (04c000a2)
08:47 masterboy: [ 1.915641] nouveau 0000:00:0d.0: bios: version
08:47 masterboy: [ 1.916739] nouveau 0000:00:0d.0: fb: 256 MiB of unknown memory type
08:47 masterboy: [ 1.965913] nouveau 0000:00:0d.0: DRM: VRAM: 253 MiB
08:47 masterboy: [ 1.965915] nouveau 0000:00:0d.0: DRM: GART: 512 MiB
08:47 gnarface: did you set the optional tests too?
08:47 masterboy: maybe dmesg shows if it has integrated ram?
08:48 gnarface: i don't really know sorry
08:48 gnarface: that looks like it's saying 256MB
08:49 gnarface: or 253?
08:49 gnarface: maybe
08:49 masterboy: gnarface, no i don't know what optional tests to choose i id the basic test for 15 minutes and the output was no errors
08:49 gnarface: maybe it's 3...
08:49 masterboy: yes i set it in bios to 256
08:49 gnarface: i forget where the other tests are
08:50 masterboy: so the error messages in dmesg show that it is a memory error?
08:50 gnarface: there's like 6 or 7 normal tests that will all run in a series by default, and there's a couple extra extended tests that catch slipperier failures
08:50 gnarface: i don't know for sure if those dmesg errors are memory errors, i just think they probably are
08:51 masterboy: okay thanks :)
08:51 gnarface: combined with this behavior, which i've seen before, it seems likely
08:52 gnarface: when this happens, can you still get a network connection to the machine?
08:52 gnarface: will it still respond to ping or ssh?
08:53 masterboy: gnarface, i have to set it up to be able to ssh to it? never done this before on a just installed ubuntu
08:53 gnarface: i don't know for sure
08:54 gnarface: i think ssh may or may not be enabled by default depending on how you installed?
08:54 gnarface: i don't use ubuntu but with debian it depends on your installation options
08:54 masterboy: ok thanks, i will try to harvest crash logs
08:55 gnarface: well, to be clear, you can easily add the ssh service
08:55 gnarface: you don't have to reinstall or anything
08:55 gnarface: just install openssh-server
08:58 gnarface: you can always uninstall it or disable it later too
09:00 masterboy: ok it works
09:00 masterboy: now i have to hang the system
09:00 masterboy: see you in a bit
09:01 gnarface: see if you can hang it with a ssh client still connected
09:01 gnarface: then see if the ssh client hangs too
09:01 gnarface: or disconnects
09:01 masterboy: aye :)
09:01 masterboy: i got some more errors
09:01 masterboy: [ 1522.558100] nouveau 0000:00:0d.0: bus: MMIO write of 03440001 FAULT at 00b020
09:01 masterboy: [ 1522.560850] nouveau 0000:00:0d.0: bus: MMIO write of 03440001 FAULT at 00b020
09:01 masterboy: [ 1529.825541] nouveau 0000:00:0d.0: bus: MMIO write of 0db70001 FAULT at 00b030
09:01 masterboy: [ 1532.795493] nouveau 0000:00:0d.0: bus: MMIO write of 00000000 FAULT at 00b030
09:03 gnarface: write fault
09:03 gnarface: seems bad
09:04 gnarface: seems like it failed to write to ram or something
09:04 gnarface: seems like it could be having a problem with the wrong addresses too
09:04 gnarface: might be software or hardware, i'm not a driver developer, i should be clear about that
09:05 gnarface: does it freeze up instantly then?
09:05 gnarface: or at least corrupt visibly?
09:05 gnarface: oh i guess that's a yes
11:16 masterboy: gnarface, now i see that C61 is not supported by nouveau
11:16 masterboy: only c51
11:17 masterboy: i installed the nvidia drivers and now it works fine
11:17 masterboy: i guess the problem is there is no support for c61 in the first place
11:17 gnarface: masterboy: oh, bummer. well that's unfortunate. i was going to suggest trying the ram sticks individually with memtest, but it sounds like that would be pointless now
11:21 masterboy: i guess there is no chance to get GeForce 6150SE nForce 430/integrated/SSE2/3DNOW! in nouveau? :P
11:21 masterboy: i tried ssh but the machine was unusable
11:23 masterboy: the errors i get are FAULT at 00b000 FAULT at 00b010 FAULT at 00b020 FAULT at 00b030
11:23 masterboy: before the hang...
11:27 gnarface: i'm the wrong guy to ask about it
11:27 gnarface: try imirkin maybe
11:28 masterboy: GeForce 6150SE
11:28 masterboy: Quadro NVS 210s / nForce 430 mhm it is supported.. i am getting confused. :)
11:28 masterboy: gnarface, thanks for all the help :)
11:28 gnarface: i don't have any way to know if they've even tested that particular board
11:28 gnarface: or how recently if they have
11:29 masterboy: thnaks for support anyway
11:29 masterboy: :)
11:34 gnarface: no problem, sorry i couldn't be of more help
11:48 masterboy: it seems the nvidia 304 driver is eol and does not support ubuntu 16 lts 4.15 kernel heh and 4.4 kernel lags...
11:49 masterboy: now i need to install a different kernel...
11:50 masterboy: the ubuntu guys missed the nvidia 304 driver support in their lts :D
12:08 masterboy: The Linux 304.* legacy driver series is the last to support the NV4x and G7x GPUs and motherboard chipsets based on them. Support for new Linux kernels and X servers, as well as fixes for critical bugs, will be included in 304.* legacy releases through the end of 2017.
12:08 masterboy: so i have to find a lts kernel or get nouveau working :)
12:09 gnarface: i think Steam requires 340
12:09 gnarface: so if you're doing this to play on Steam, it'll have to be nouveau
12:10 gnarface: hmm, i wonder if it's something simple like you just need to specify the right amount of ram
12:11 gnarface: if you can use the legacy driver package installer with a newer kernel i think that would be better
12:12 masterboy: the nvidia drivers show i am using 151 MB (59% so i need to set 256 mb for sure :)
12:12 masterboy: i will try now to install lts kernels and see if i can get 4.14 :P
12:13 masterboy: it seems debian has a patch to make it work on 4.15 and up kernels... have to install debian then...
12:14 masterboy: Building the kernel module has been tested up to Linux 4.15. Debian
12:16 gnarface: in theory you could add the patch to your own kernel too
12:17 gnarface: that might be more trouble than just patching and rebuilding though
12:28 imirkin: masterboy: those 0b000 faults are nothing to worry about
12:29 masterboy: hi imirkin well something hangs the nvidia c61 :(
12:29 imirkin: <masterboy> [ 1.916739] nouveau 0000:00:0d.0: fb: 256 MiB of unknown memory type
12:29 imirkin: that's surprising.
12:30 imirkin: skeggsb: --^
12:30 masterboy: imirkin, it is ddr2 800mhz :)
12:31 imirkin: well, the point is that it should say "stolen memory"
12:31 imirkin: having "unknown memory type" is likely to lead to other issues
12:33 masterboy: thanks imirkin for the clarification. :) How can I help?
12:33 imirkin: i'd try an older kernel ... something in the 4.0 vintage, pre-4.3
12:34 gnarface: my bad
12:34 imirkin: if that works better, then we can figure out which of the VMM rewrites screwed it up
12:34 imirkin: if it doesn't, then it's likely a userspace issue
12:35 masterboy: imirkin i will try now and see if nvidia drivers work on 4.15 with the latest patches to 403 and then i will try an older kernel thanks. :)
12:36 imirkin: nvidia drivers will work MUCH better on a nv4x
12:36 imirkin: nouveau has a number of known issues with that hw
12:36 masterboy: i have time on my hands now so i check :)
12:37 masterboy: but it seems lag is fixed only in kernel 4.5
12:38 imirkin: the 6150SE is particularly vexing as many of them have a DVI port that we just can't drive.
12:38 masterboy: Your issue is probably related to this. You need to enable PRIME Synchronization but that requires Kernel 4.5+ and X.org 1.19 (ABI 23) which are not available in Ubuntu 16.04 by default. Either use some ppa which include those versions or switch to another distro which comes with newer packages..
12:38 imirkin: PRIME won't work with nv4x
12:38 masterboy: oh i see
12:39 masterboy: imirkin, my mobo does not have a dvi, only vga
12:39 imirkin: ah ok
12:39 imirkin: some had a DVI port sitting on an external encoder
12:39 imirkin: we never figured out how to drive that external encoder
12:40 masterboy: imirkin, maybe there is a problem because of amd declaring the memory as unganged?
12:41 masterboy: it is a amd thing
12:41 imirkin: doubtful
12:41 masterboy: okay i will check older kernels :)
12:41 imirkin: at this point i don't even know what your issue is...
12:41 imirkin: does glxgears work?
12:41 imirkin: and just heavier stuff dies eventually?
12:41 masterboy: imirkin, everything works until it hangs
12:42 masterboy: see my photos
12:42 imirkin: ;)
12:42 masterboy: https://drive.google.com/open?id=1tdmM-WKD69umDdvdqTTAUI03zQSVsJL_
12:42 imirkin: hmmmmm
12:43 imirkin: that could just be nouveau being buggy
12:43 masterboy: 256mb pc hang
12:43 imirkin: rather than anything more sinister
12:43 masterboy: imirkin, ah and the unity dash is not transparent on nouveau
12:43 masterboy: but on nvidia it is
12:44 masterboy: maybe nouveau cant handle the 3d bling of unity mhmhm
12:45 imirkin: that's highly likely
12:45 imirkin: even likelier that unity detects nouveau and stops doing pointless things
12:45 masterboy: hehehehe
12:46 masterboy: as if gnome would be better :D
12:48 imirkin:likes windowmaker
12:48 masterboy:likes windowlicker
12:53 masterboy: reboot
13:35 masterboy: imirkin, it seems nouveau does not crash on ubuntu kernel 4.4 but does crash on 4.15
13:36 masterboy: 4.4 and 4.15 being the only official options
13:36 masterboy: i get the same errors but it does not crash at least :)
13:38 masterboy: 4.4 log https://paste.gnome.org/p3expuxzd
13:39 masterboy: [ 1.888423] nouveau 0000:00:0d.0: fb: 256 MiB of unknown memory type
13:39 masterboy: [ 1.947981] nouveau 0000:00:0d.0: DRM: VRAM: 253 MiB
13:39 masterboy: [ 1.947983] nouveau 0000:00:0d.0: DRM: GART: 512 MiB
13:39 karolherbst: imirkin: regarding that MCP89 mmu thing. We have this issue for months now and I am under the impression that skeggsb told me that he is sure that the set mmu class is correct. I have the same issue on one of my machines and using the mcp77 one just works though
13:40 masterboy: vram should be 256 not 253 maybe? :P
13:47 masterboy: i will try debian 4.9 now and see if it is a userspace thing
14:16 masterboy: okay debian 9 with kernel 4.9 works fine too. so it is a ubuntu thing with 4.15 kernel...
15:13 crmlt: Does this Option "AccelMethod" "glamor"
15:13 crmlt: work?
20:46 selk: Hello, is the gt 1050ti well-supported by nouveau?
20:49 RSpliet: selk: What do you consider well-supported?
20:49 RSpliet: I'd say no, but it's a bit subjective
20:50 selk: if it is full supported..
20:50 RSpliet: oh hah, no that definitely not
20:51 selk: which is the best card for nouveau?
20:51 selk: in terms of support, compatibility
20:51 RSpliet: 780 Ti I think
20:51 RSpliet: or Titan
20:51 selk: oh, I will check
20:52 RSpliet: Anything newer than that (on the high end at least) is not going to let you bring clocks to the cards full potential - you'll just have a crippled experience
20:52 HdkR: Kepler woo
20:53 RSpliet: Also unsure whether we can do HW video decoding on anything beyond kepler (and the first gen maxwell, but that's all low-end cards)
20:53 RSpliet: Equally, we can't change clocks on the Fermi gen cards, so don't get stuff older than say a GTX 680 or 690
21:07 HdkR: RSpliet: I assume Maxwell/Pascal reclocking isn't implemented even if you snag the firmwares from the blob?
21:15 pmoreau: karolherbst: I remember there was a discussion somewhere about that (either SPIRV-LLVM-Translator or SPIRV-Tools), and I think the answer was: yes. But I’d need to double-check the spec.
21:16 selk: 1060 and 1070 are supported?
21:16 selk: according to https://nouveau.freedesktop.org/wiki/CodeNames/ is supported
21:17 selk: but on the bottom, i have the doubt.
21:17 HdkR: selk: Supported isn't the same as your original ask of "fully supported"
21:17 HdkR: Things will run, but perf will be garbage and isn't bound to change anytime soon
21:17 selk: well.. i am going to bought a card, basically i want to know if it will work with nouveau
21:18 HdkR: Card will run at idle clocks, which is <100mhz on those cards. Probably hit other issues that aren't just perf related too...
21:20 pmoreau: HdkR: Reclocking works for GM20x but isn’t enabled as fan speed cannot be changed. Pascal doesn’t work as you need to be in secure mode to change the voltage. (IIRC)
21:20 HdkR: ow
21:21 pmoreau: Since no one has been able to find the PMU firmwares, no clue if that would be enough to get reclocking working or if more RE is needed.
21:21 karolherbst: HdkR: idle clocks aren't that low :D
21:22 karolherbst: HdkR: GPUs tend to boot on max clocks from the lowest perf level, which is round about 300-500 MHz or something
21:23 karolherbst: pmoreau: well, we would need to re the PMU interface
21:23 pmoreau: True, there is that
21:23 karolherbst: but I think this is more of a setup the PMU and let it do its work kind of thing
21:24 HdkR: karolherbst: Ah, maybe I'm too used to laptop idle clocks being super low
21:25 HdkR: Or...Tegra?
21:25 HdkR:can't remember what idled at 78Mhz
21:26 karolherbst: well
21:26 karolherbst: nvidia does odd things on idle
21:27 karolherbst: practically going below the lowest cstate
21:27 karolherbst: which... more or less doesnt change much as you are stuck with the same voltage
21:28 HdkR: Also just noticed this GPU I was using was idling in P0 state. No wonder idle amount for this PC was insane
21:28 HdkR: idle power consumption*
22:26 selk: HdkR: can I ask what card are you using for nouveau?
22:35 HdkR: selk: I'm not using Nouveau
22:36 HdkR: I need to get karolherbst supporting cuda first
22:36 karolherbst: :D
22:36 karolherbst: be careful what you wish for :D
22:36 HdkR: lol
22:37 HdkR: Alright, and need Turing support :P
22:51 pmoreau: HdkR: I would ask for RTX support, personally. ;-)
22:53 pmoreau: Getting VK_NV_raytracing on my Pascal would be nice.
22:53 pmoreau: And with Nouveau, I could then play with improving the BVH quality and build speed. Lots of fun in perspective!
22:58 HdkR: pmoreau: Sure, implementing the extension would be a fun time consuming task
22:58 HdkR: Somthing as a common codebase in mesa would be neat
23:57 imirkin: selk: buy amd
23:57 imirkin: *way* better supported
23:57 HdkR: ^
23:58 imirkin: not even close.
23:58 imirkin: not even comparable, that's how much better.
23:59 imirkin: karolherbst: mcp89 using g84_mmu seems fine. the issue is that it doesn't let you do compression, and fails nouveau_bo_new. that's not cool.