01:18 imirkin_: TimurTabi: iirc dmem.c is all the svm/hmm stuff
01:18 imirkin_: no clue what 'd' stands for
01:19 imirkin_: maybe "distributed memory"?
01:19 imirkin_: oh, no -- i bet it's "device memory"
01:19 imirkin_: yeah, i'm putting at least 5c on that bet.
16:25 karolherbst: imirkin_: is there anything I should test your blitter fix on?
16:26 imirkin_: no, i'm pretty sure it's an improvement over the current situation
16:26 imirkin_: it's not a perfect fix to blitting, but it wasn't intended to be
16:27 karolherbst: I guess you didn't encounter any regressions in piglit or the CTS, right?
16:27 imirkin_: i only ran CTS - no regressions
16:27 karolherbst: I plan to do some piglit runs next week, I can test your patch as well
16:27 imirkin_: (actually ... hm... i may not have run _all_ of CTS, since it hangs part-way when you run the full thing)
17:54 pounce: look at what i found at work https://files.catbox.moe/3pfuuf.jpg
17:54 pounce: sorry for bad pic
18:04 karolherbst: \o/
18:04 karolherbst: ddr2 or gddr3?
18:13 pounce: idk
18:17 imirkin_: that's probably a G96 with DDR2 - i have a similar board
18:20 karolherbst: imirkin_: both variants are g96 afaik
18:20 imirkin_: hm, probably
18:26 TimurTabi: imirkin_, so by "device memory", you're saying it means that large framebuffer memory that's visible to the GPU and the CPU?
18:28 imirkin_: TimurTabi: well, it's in reference to being able to address GPU memory through CPU mappings
18:28 imirkin_: so the CPU process would have memory in its address space that's both RAM and VRAM
18:28 imirkin_: TimurTabi: and it's all a bit special, since consistent MMU mappings are maintained between CPU and GPU
18:29 imirkin_: so the (virtual) address of a particular page are the same in both places, which allows you to have pointers and whatnot
18:29 imirkin_: this is used as part of SVM
19:31 maccraft321: hey my geforce 8300 gpu hangs when trying to run any game like portal 2
19:31 maccraft321: doesn't happen with glxgears
19:31 maccraft321: complete system lockup happens, i can't go to tty, can't toggle capslock
19:32 maccraft321: i am using 2 monitors, one lcd on dvid(hdmi-2 in linux), and one crt on vga
19:39 imirkin_: can you ssh in?
19:39 imirkin_: and if so, do you see DMA_PUSHER errors?
19:40 maccraft321: imirkin_: DMA_PUSHER where?
19:40 imirkin_: also what's 8300 again? is it like a G84? or a MCP79 or something
19:40 imirkin_: errors in dmesg
19:40 maccraft321: imirkin_: MCP78S is my chipset
19:40 imirkin_: ok
19:41 maccraft321: i have dmesg running now
19:41 imirkin_: over ssh
19:41 imirkin_: otherwise you may not see the errors
19:41 maccraft321: nothing in dmesg
19:41 maccraft321: on ssh
19:41 imirkin_: and it's currently hung?
19:41 maccraft321: yep
19:42 imirkin_: hrmph
19:42 imirkin_: mind pastebin'ing the whole dmesg?
19:42 maccraft321: https://bpaste.net/XTDA
19:42 maccraft321: oh
19:42 maccraft321: only gpu is hung
19:42 imirkin_: that's expected
19:43 imirkin_: hrmph
19:43 imirkin_: surprisingly silent
19:43 maccraft321: and it has unhung and hung itself
19:43 imirkin_: probably not a hang, but it's waiting for something dumb
19:43 imirkin_: you can just kill the portal process, i bet it'll recover
19:43 maccraft321: ps ax useful?
19:43 imirkin_: nah
19:44 imirkin_: this is unusual though
19:44 imirkin_: normally there'd be errors of some sort
19:45 maccraft321: xorg log useful?
19:47 imirkin_: nope
19:47 imirkin_: i mean ... maybe
19:48 imirkin_: unrelated, but fyi, you can adjust clock speeds on that GPU if you want more speed
19:48 imirkin_: i.e. crash faster :)
19:48 maccraft321: https://bpaste.net/W5NQ
19:48 imirkin_: via /sys/kernel/debug/dri/0/pstate
19:48 imirkin_: yeah, nothing too odd in there
19:48 maccraft321: killing game has worked at unhanging the gpu
19:49 imirkin_: something's probably waiting on a fence that never happens? dunno.
19:54 maccraft321: imirkin_: if i put radeon pcie gpu and run opengl on it
19:54 maccraft321: with prime
19:54 maccraft321: it still hangs
19:57 imirkin_: maybe the game is busted?
19:57 imirkin_: dunno
19:57 imirkin_: i gtg shortly though
20:03 maccraft321: imirkin_: it also happens with xonotic
20:03 maccraft321: both glx and sdl
20:23 imirkin_: maccraft321: almost sounds like interrupts stop happening
20:23 imirkin_: although ... then killing the game wouldn't help
20:23 maccraft321: it helps after some time
20:24 maccraft321: not immideatly
20:24 imirkin_: right, there are some additional timeouts probably
20:24 imirkin_: you could try DRI3, see if that magically helps things
20:24 imirkin_: that requires you to add a Option "DRI" "3" in your Driver section in xorg.conf
20:24 maccraft321: i have no xorg.conf
20:25 imirkin_: you definitely do
20:25 imirkin_: you just don't know it :)
20:25 maccraft321: nope
20:25 imirkin_: fragments in /etc/X11/xorg.conf.d/ ? no?
20:25 imirkin_: also in /usr somewhere
20:25 maccraft321: no
20:25 imirkin_: for stuff like default mouse/touchpad/etc things
20:27 maccraft321: yes
20:27 maccraft321: in /usr
20:27 maccraft321: forgot about it
20:27 maccraft321: but no nouveau parts
20:27 imirkin_: yeah
20:28 imirkin_: so ... time to add one :)
20:28 imirkin_: just need a Driver section, nothing else
20:28 maccraft321: Device?
20:28 imirkin_: yes, sorry
20:28 imirkin_: Section "Device"\nOption "Driver" "nouveau"\nOption "DRI" "3"\nEndSection
20:29 maccraft321: yea i have it now
20:30 maccraft321: trying xonotic
20:30 maccraft321: doesn't help with hangs
21:07 maccraft321: imirkin_: any idea now?
21:08 imirkin_: none
21:10 maccraft321: imirkin_: if i put nouveau.debug=warn into kernel command line would it help?
21:11 maccraft321: or debug
21:13 imirkin_: not really
21:13 imirkin_: the dfeault level is info btw
21:13 imirkin_: so warn would get you fewer messages
21:16 maccraft321: would disabling MSI help?
21:16 imirkin_: maybe? i don't remember any MSI issues on nvaa, but my memory is hazy
21:16 imirkin_: btw - i didn't look - but you don't have a SUPER ancient kernel, do you?
21:16 imirkin_: there were some fixes ages ago for nvaa/nvac
21:16 maccraft321: i run latest testing arch linux kernel
21:16 imirkin_: in the early 4.x's i think
21:16 imirkin_: ok yeah
21:17 maccraft321: 5.4.7 linux
21:17 imirkin_: pmoreau is not around, but he did the nvaa/nvac thing a while back - some macbook
21:17 imirkin_: perhaps he's aware of any lingering issues
21:18 imirkin_: but sure - try nouveau.config=NoMSI=1
21:18 maccraft321: ok after update ends
21:18 imirkin_: or rather NvMSI=0
21:19 maccraft321: he is on #dri-devel
21:19 imirkin_: ah ok
21:30 maccraft321: imirkin_: didn't fix it
21:37 maccraft321: imirkin_: when i launch xonotic
21:38 maccraft321: it gives me "1024x768x16x0.00hz"
21:38 maccraft321: is that related?
21:38 maccraft321: it may be not refreshing the screen
21:45 imirkin_: heh
21:45 imirkin_: what gives you that?
21:45 maccraft321: xonotic-glx
21:45 imirkin_: i haven't run it in ages, dunno. could just be that it's not detecting the monitor's settings
21:45 imirkin_: mind running 'xrandr'?
21:46 maccraft321: xrandr is picking correct modes
21:46 maccraft321: on both monitors
21:46 maccraft321: bpaste.net/G44A
21:46 maccraft321: note that dvid output is detected as hdmi
21:47 maccraft321: forcing crt to use 60hz doesn't fix the issue
21:47 imirkin_: probably hdmi under the hood
21:47 imirkin_: i wonder if the 1366x768 mode is causing troubles
21:47 imirkin_: that's a weird mode.
21:47 maccraft321: that is my lcd display
21:47 imirkin_: could you, temporarily, flip it to 1280x720?
21:47 imirkin_: 1366 isn't a multiple of 8
21:47 imirkin_: it's just a really weird mode.
21:48 maccraft321: doesn't change the output of xonotic
21:48 imirkin_: lots of hacks to support that mode
21:48 maccraft321: it is widened 1024x768
21:48 imirkin_: i get the idea
21:50 imirkin_: the offset of the second monitor in the overall fb isn't a multiple of 8 now though
21:50 imirkin_: which i can imagine can cause issues.
21:51 maccraft321: ok now i have disconnected dvi monitor physically
21:53 maccraft321: oh hey guess what
21:53 maccraft321: imirkin_: no changes
21:53 imirkin_: hehe
21:53 imirkin_: well, i'm pretty much out of ideas, sorry :(
21:54 imirkin_: you can try forcing the "modeset" driver - perhaps that'll magically make things better?
21:54 imirkin_: on average, imo, it makes things worse, but perhaps some sync thing works better?
21:54 maccraft321: modeset?
21:54 imirkin_: instead of Driver "nouveau", do Driver "modeset"
21:54 imirkin_: er no
21:54 imirkin_: Driver "modesetting"
21:58 maccraft321: imirkin_: no change
21:58 imirkin_: check your xorg log, make sure it says "modeset" instead of "NOUVEAU"
21:58 maccraft321: it says that
22:02 imirkin_: i've said it before, and i'll say it again ... i've got nothin' ... sorry
22:29 maccraft321: imirkin_: i connected nv46 gpu
22:29 maccraft321: and it works fine
22:29 maccraft321: although performance is shit
22:35 imirkin_: now nv46 -- iirc that's where MSI is actually broken :)
22:35 imirkin_: or was, at least
22:35 imirkin_: that's G70, right?
22:39 maccraft321: dunno
23:30 maccraft321: imirkin_: when i use proprietary drivers xonotic still displays refresh rate as 0hz
23:31 maccraft321: but it runs fine
23:31 maccraft321: at least it displays title screen
23:39 maccraft321: imagine having working gpu
23:39 maccraft321: this post was made by nvidia gang