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 69827] [NVC1] Uneven, jerky mouse movement, increasing CPU usage
Date: Wed, 18 Nov 2015 21:03:37 +0000	[thread overview]
Message-ID: <bug-69827-8800-LMnv59SUQ2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-69827-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #24 from James Moe <jimoe-zgPZrQL6nFyVmwMjj6irZQ@public.gmane.org> ---
> Please get debug symbols
>
Which symbol set(s)? I already have the kernel-syms.

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

[-- Attachment #1.2: Type: text/html, Size: 1114 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-18 21:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26  1:56 [Bug 69827] New: Uneven, jerky mouse movement, increasing CPU usage bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-69827-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-09-26 23:54   ` [Bug 69827] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-26 23:55   ` [Bug 69827] [NVC1] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-06  5:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-06  5:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-26  5:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-01  0:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-01  6:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-01  6:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-15 19:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-15 20:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-03 19:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 17:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 19:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 22:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 22:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 22:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 22:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 23:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-16 23:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-17 17:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-17 17:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-17 17:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-17 23:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-17 23:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-18 21:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-06-30 10:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-01 20:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-01 20:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:37   ` 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-69827-8800-LMnv59SUQ2@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.