All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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	[thread overview]
Message-ID: <bug-95054-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1852 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 3372 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2016-04-21 15:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 15:59 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-95054-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-04-21 16:00   ` [Bug 95054] KDE 5 / Plasma crashes with nouveau "fifo: gr engine fault on channel 2, recovering" or "gr: TRAP ch 2" bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-21 16:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-21 16:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-01  8:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-01  9:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-01  9:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-01  9:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-06 10:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-30  9:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-11 22:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-11 22:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-95054-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.