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 92971] [GF110] KDE plasma locks randomly due to crash of nouveau driver
Date: Mon, 16 Nov 2015 22:18:16 +0000	[thread overview]
Message-ID: <bug-92971-8800-FXxeFCj9DB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92971-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

https://bugs.freedesktop.org/show_bug.cgi?id=92971

--- Comment #4 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
Nov 14 19:06:12 hpprol2 kernel: nouveau 0000:0a:00.0: fifo: PBDMA0: 80000000 []
ch 30 [007e6ab000 kscreenlocker_g[4257]] subc 6 mthd 2878 data a0c02020

A few things wrong with this picture... first off, nouveau never uses
subchannel 6.

Method 2878 is: lookup -a c8 -d SUBCHAN -- -v obj-class GF100_3D 2878
TFB_VARYING_LOCS[0][0x1e] => 0

But those are all emitted in one fell swoop, starting from 2800. No way
something could get into the middle of that and screw up the channel on just
that one. (Since they don't have independent begin clauses). So this has to
have come from elsewhere.... but where?

Is this the first error? The first error is always the most important... the
rest can often happen as a result of the earlier ones.

Are you sure the kernel update is what brought this about and not a KDE update?
Is this KDE4 or KDE5?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.

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

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

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

  parent reply	other threads:[~2015-11-16 22:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92971-8800@http.bugs.freedesktop.org/>
     [not found] ` <bug-92971-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-11-16 20:25   ` [Bug 92971] KDE plasma locks randomly due to crash of nouveau driver bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 21:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 21:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 21:15   ` [Bug 92971] [GF100] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 21:59   ` [Bug 92971] [GF110] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 22:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-11-16 23:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-17 12:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-17 13:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-21  7:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-22  7:56   ` 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-92971-8800-FXxeFCj9DB@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.