From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 95054] New: KDE 5 / Plasma crashes with nouveau "fifo: gr engine fault on channel 2, recovering" or "gr: TRAP ch 2" Date: Thu, 21 Apr 2016 15:59:32 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1825333777==" Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============1825333777== Content-Type: multipart/alternative; boundary="14612543710.9F0ba9.22282"; charset="UTF-8" --14612543710.9F0ba9.22282 Date: Thu, 21 Apr 2016 15:59:31 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=95054 Bug ID: 95054 Summary: KDE 5 / Plasma crashes with nouveau "fifo: gr engine fault on channel 2, recovering" or "gr: TRAP ch 2" Product: xorg Version: 7.4 (2008.09) Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Reporter: matthias.h.nagel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org I upgraded from KDE 4 to KDE 5/Plasma. Since the nouveau driver keeps crashing and freezes everything. If I use the proprietary nvidia firmware (NvGrUseFw=1) together with the nouveau driver everything works fine. Normally, the crash heralds itself by some disrupted graphics (black boxes on the desktop) some seconds before everything freezes totally. The crash is usually triggered by some desktop effect if some item (menu/dialog/window) fades in or out ("transparency" effect). The crash usually occurs within the first five minutes after the login. Sometimes even the login crashes (sddm window manager) because the window manager uses the same fading effect and triggers the bug, too. My kernel version is 4.4.7. Graphic card: "ASUS GeForce GTX 660 PCI 3.0 2GB DDR5" uname: "Linux 4.4.7-gentoo #2 SMP Thu Apr 21 13:34:23 CEST 2016 x86_64 Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz GenuineIntel GNU/Linux" I also still suffer from bug #93629 and 93630 that also vanish if the proprietary firmware is used. But I decided to open a new bug, because the dmesg messages are different. -- You are receiving this mail because: You are the assignee for the bug. --14612543710.9F0ba9.22282 Date: Thu, 21 Apr 2016 15:59:31 +0000 MIME-Version: 1.0 Content-Type: text/html
Bug ID 95054
Summary KDE 5 / Plasma crashes with nouveau "fifo: gr engine fault on channel 2, recovering" or "gr: TRAP ch 2"
Product xorg
Version 7.4 (2008.09)
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component Driver/nouveau
Assignee nouveau@lists.freedesktop.org
Reporter matthias.h.nagel@gmail.com
QA Contact xorg-team@lists.x.org 

I upgraded from KDE 4 to KDE 5/Plasma. Since the nouveau driver keeps crashing
and freezes everything. If I use the proprietary nvidia firmware (NvGrUseFw=1)
together with the nouveau driver everything works fine.

Normally, the crash heralds itself by some disrupted graphics (black boxes on
the desktop) some seconds before everything freezes totally. The crash is
usually triggered by some desktop effect if some item (menu/dialog/window)
fades in or out ("transparency" effect). The crash usually occurs within the
first five minutes after the login. Sometimes even the login crashes (sddm
window manager) because the window manager uses the same fading effect and
triggers the bug, too.

My kernel version is 4.4.7.

Graphic card: "ASUS GeForce GTX 660 PCI 3.0 2GB DDR5"

uname: "Linux 4.4.7-gentoo #2 SMP Thu Apr 21 13:34:23 CEST 2016 x86_64 Intel(R)
Xeon(R) CPU E3-1230 v3 @ 3.30GHz GenuineIntel GNU/Linux"

I also still suffer from bug #93629 and 93630 that also vanish if the
proprietary firmware is used. But I decided to open a new bug, because the
dmesg messages are different.

You are receiving this mail because:
  • You are the assignee for the bug.
--14612543710.9F0ba9.22282-- --===============1825333777== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg== --===============1825333777==--