similar to: [Bug 58378] [NV86] Distorted graphics on NVIDIA GeForce 8400M G after upgrade the kernel to 3.7.0 version

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #60 from Andreas Loew <awl1 at gmx.net> --- > There was a bug in nvapeek/poke (it was using the wrong address space by > default), can you update your pull and try again? [That explains why you saw > 'S' in the output.] Of course - here you are: The version I used is from the "Download ZIP" button in

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #55 from Andreas Loew <awl1 at gmx.net> --- > > [aloew at aloew-lap envytools-master]$ ./nva/nvapoke 10200c 10 > > WARN: Can't probe 0000:01:00.0 > > PCI init failure! > You need to run these as root. Ouch - sorry - could have indeed had this idea myself... :-( Here are the results as root: [aloew at

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #69 from Andreas Loew <awl1 at gmx.net> --- > Could you provide the output of > > nvapeek 154c > nvapeek 1540 > > Those registers specify which engines are there. I think we're ignoring them > in nouveau... OK - that might indeed explain the issues seen... Here you are: [aloew at aloew-lap nva]$ sudo

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #58 from Andreas Loew <awl1 at gmx.net> --- > > [aloew at aloew-lap envytools-master]$ sudo ./nva/nvapeek 10200c 10 > > 0010200c: SS SS SS SS SS SS SS SS SS SS SS SS SS SS SS SS > > nvapeek 10200c without the 10. (Not sure what that does.... maybe reads out > 0x10 regs) yes - seems to read 10 registers:

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #52 from Andreas Loew <awl1 at gmx.net> --- Hello again, Ilia, > Can you grab envytools (https://github.com/envytools/envytools) and run bad news (or maybe expected from what we have been seeing earlier): [aloew at aloew-lap envytools-master]$ ./nva/nvapeek 10200c WARN: Can't probe 0000:01:00.0 PCI init failure!

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #57 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #55) > > > [aloew at aloew-lap envytools-master]$ ./nva/nvapoke 10200c 10 > > > WARN: Can't probe 0000:01:00.0 > > > PCI init failure! > > > You need to run these as root. > > Ouch - sorry - could have indeed

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #54 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #52) > Hello again, Ilia, > > > Can you grab envytools (https://github.com/envytools/envytools) and run > > bad news (or maybe expected from what we have been seeing earlier): > > [aloew at aloew-lap envytools-master]$

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #34 from Andreas Loew <awl1 at gmx.net> --- Bad news once again... I applied the following single-line patch to a stock 3.12.4 kernel in order to switch to the NV50 fence: diff -Nrpu linux-3.12.4.orig/drivers/gpu/drm/nouveau/nouveau_drm.c linux-3.12.4/drivers/gpu/drm/nouveau/nouveau_drm.c ---

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #61 from Andreas Loew <awl1 at gmx.net> --- Hmm... Looking at the code for nvapeek, I fear that nva_rd(...) still did not return any meaningful data, as it look like we get s == 0...!? int s = 0; for (i = j = 0; i < 16 && i < b; i+=rs.regsz, j++) { e[j] =

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #65 from Andreas Loew <awl1 at gmx.net> --- Oops - I just remembered that I am booting my kernel with "nouveau.config=PCRYPT=0" in the meantime... Does this make any difference, i.e. do I need to retry the nvapeek/nvapoke sequence without this kernel option? Sorry & thanks, Andreas -- You are receiving this

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #82 from Andreas Loew <awl1 at gmx.net> --- Hi Thomas, > I have the same NVIDIA GeForce NVS 130M with the disabled functions. > I checked with nvapeek: > 0000154c: 0000009c > 00001540: b1010001 great - finally somebody who confirms this issue. > uname -a delivers > Linux mobuntu 3.11.0-15-generic #23-Ubuntu

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #64 from Andreas Loew <awl1 at gmx.net> --- Yes, we indeed see the same well-known: nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00010000 FAULT at 0x10200c at any nvpeek read attempt, and nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000010 FAULT at 0x10200c at any nvpoke attempt... :-( BR, Andreas -- You are

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #59 from Ilia Mirkin <imirkin at alum.mit.edu> --- There was a bug in nvapeek/poke (it was using the wrong address space by default), can you update your pull and try again? [That explains why you saw 'S' in the output.] -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #51 from Ilia Mirkin <imirkin at alum.mit.edu> --- So actually I'm told that pcrypt is on the main clock, so that theory is out. Can you grab envytools (https://github.com/envytools/envytools) and run nvapeek 10200c nvapoke 10200c 10 nvapeek 10200c and see what's in dmesg?Do you see additional MMIO read/write failures,

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #67 from Ilia Mirkin <imirkin at alum.mit.edu> --- Could you provide the output of nvapeek 154c nvapeek 1540 Those registers specify which engines are there. I think we're ignoring them in nouveau... -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #29 from Andreas Loew <awl1 at gmx.net> --- OK, finally I have some more encouraging news: It now looks like the issue indeed started much earlier than initially thought, namely already between the 3.4 and 3.5 kernel series!!! Results from my testing with stock kernels obtained from kernel.org (I've never ever before

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #77 from Andreas Loew <awl1 at gmx.net> --- Sorry that it took me longer to get back here - I needed an additional rpmbuild run due to running out of disk space for my first attempt... But I can give an all clear signal - at least for my machine, AFAIK, everything seems to be fine: Kernel command line: ro

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #43 from Andreas Loew <awl1 at gmx.net> --- Hello again, so it looks like I have now tracked the issue down. The "offending" commit seems to be: 4c193d254ee94da02857b9670e815b1765a9579b (the first commit which showed the issue - I tried for more than half an hour with its direct predecessor

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #45 from Andreas Loew <awl1 at gmx.net> --- Hmm... While my card definitely is not at all defective (it works the exact same way it always has), I indeed also have some issues that make it impossible for me to still use the "blob" even on an attic distro like RHEL6: The most recent version of the NVidia proprietary

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #66 from Andreas Loew <awl1 at gmx.net> --- A Happy New Year to everybody! :-) Just wondering whether you intend to simply close this issue down with the workaround "solution" for me to set kernel option nouveau.config=PCRYPT=0 or whether you are still interested in finding out *why* my Quadro NVS 130M and other