similar to: [Bug 92971] [GF110] KDE plasma locks randomly due to crash of nouveau driver

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #5 from Philippe Condé <conde.philippe at skynet.be> --- hello, it is kde5 (KF5). With opensuse Tumbleweed we do a global update (snapshot). Difficult to see thereafter if this is due to KDE or the kernel. Three examples from journalctl: the very first error after the boot message: the lock occurred during reactivation of

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #8 from Philippe Condé <conde.philippe at skynet.be> --- Hello, I desactivated kscreenlocker which resolve the reactivate problem. But the problem of corrupt screen when starting different programs remains and is worst since the last zypper dup. I found this error still related to nouveau when the two screen got corrupted ov

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #7 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to Philippe Condé from comment #6) > Hello, > > I tested with the non Xen kernel vmlinux-4.3.0-1-default. > The crash exists also with this kernel > > here the journalctl output with a crash when loading a page in the browser: > The screen was

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #6 from Philippe Condé <conde.philippe at skynet.be> --- Hello, I tested with the non Xen kernel vmlinux-4.3.0-1-default. The crash exists also with this kernel here the journalctl output with a crash when loading a page in the browser: The screen was totally corrupted but I succeeded to go the the console CTRL Alt F1 and

https://bugs.freedesktop.org/show_bug.cgi?id=92971 Philippe Condé <conde.philippe at skynet.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Philippe Condé

https://bugs.freedesktop.org/show_bug.cgi?id=92971 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[GF100] KDE plasma locks |[GF110] KDE plasma locks |randomly due to crash of |randomly due to crash of

https://bugs.freedesktop.org/show_bug.cgi?id=92971 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|DRM/other |Drivers/DRI/nouveau Version|XOrg git |unspecified Assignee|dri-devel at

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #2 from Philippe Condé <conde.philippe at skynet.be> --- Hello here the output: Mesa version # rpm -aq Mesa* Mesa-libGLESv2-2-11.0.4-125.1.x86_64 Mesa-libEGL1-11.0.4-125.1.x86_64 Mesa-libglapi0-32bit-11.0.4-125.1.x86_64 Mesa-32bit-11.0.4-125.1.x86_64 Mesa-libGL1-11.0.4-125.1.x86_64 Mesa-libGL-devel-11.0.4-125.1.x86_64

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #3 from Philippe Condé <conde.philippe at skynet.be> --- Created attachment 119718 --> https://bugs.freedesktop.org/attachment.cgi?id=119718&action=edit output of dmesg -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. -------------- next part --------------

https://bugs.freedesktop.org/show_bug.cgi?id=92971 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|KDE plasma locks randomly |[GF100] KDE plasma locks |due to crash of nouveau |randomly due to crash of

https://bugs.freedesktop.org/show_bug.cgi?id=111110 Bug ID: 111110 Summary: Nvidia quadro + nouveau : second terminal wake up but doesn't more display Product: Mesa Version: 19.1 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=92504 Bug ID: 92504 Summary: [NVA5] Corruption in Plasma 5 on resume after changing screen configuration Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

So there's a register in Render Targets called Array Mode: https://github.com/envytools/envytools/blob/master/rnndb/graph/gf100_3d.xml#L289 We've witnessed values of 1 and 6 (array mode -> layers) but we can't tell their meaning. Do you guys got any related info? Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL:

So I have been going on over the documentation trying to figure out the exact layout of Pitch Linear Textures and find some missing values. First Question: What's the correct layout of pitch linear textures in memory? Is padding of the pitch added at start or at the end? Do they have some kind of header? Currently I see them as a normal texture matrix with just pitch at the end of each row

So we are currently doing tests and complying with them in our Emulator. Currently the conditional rendering test does not pass (no wonder we not even implement it). I've been looking at the current documentation https://github.com/envytools/envytools/blob/master/rnndb/graph/gf100_3d.xml#L796 So far I don't understand how the cond address is used and to what it's compared.

NVIDIA provided the documentation for mp error 0x10, INVALID_ADDR_SPACE, which apparently happens when trying to use an atomic operation on local or shared memory (instead of global memory). Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drm/nouveau/nvkm/engine/gr/gf100.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drm/nouveau/nvkm/engine/gr/gf100.c

These patches are adding support for outputting 2560x1440 at 56 over HDMI. This needs a pixel clock of 225 MHz which was not supported before. This was tested in a dual monitor setup with a GF114 (GTX 560 TI) and one HDMI monitor running with 2560x1440 at 56 and one DVI monitor running with 1920x1200 at 60. This still needs testing on other graphics cards and with dual link DVI. There is no

Alright, so I have no issues getting Plasma Pong started...as long as I run it through the command line. ie: Code: wine "C:\Plasma Pong\Plasma Pong.exe"[quote] That example works fine...as long as it's done in a terminal. However, the game seems to not like being ran without a terminal. (I can't just click on the .exe file to run it). I'm wondering if there's a way

Hi, I'm trying to get Plasma Pong 1.3c (www.plasmapong.com) running, and according to the appdb, 1.3b works with 0.9.33. However, I can't get it to work right now with 0.9.37 or 0.9.40. I get the following error: Error: Could not open the scoreboard file: '/scores.ini' An error has occured in the sound sub-system: (52) Error initializing output device. The FMOD sound system

https://bugs.freedesktop.org/show_bug.cgi?id=107501 Bug ID: 107501 Summary: System hangs on attempt to login to Plasma (Wayland) Product: Mesa Version: 18.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/nouveau