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 25966] New: nv25 : rxvt scrolling is very slow
Date: Sat,  9 Jan 2010 09:36:44 -0800 (PST)	[thread overview]
Message-ID: <bug-25966-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=25966

           Summary: nv25 : rxvt scrolling is very slow
           Product: xorg
           Version: 7.5
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: castet.matthieu-GANU6spQydw@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Hi,

using rxvt 2.7.10 (from debian sid) has some issue with nouveau :
- opening a new terminal, 
- filling it with data (dmesg for example), 
- and then scrolling with the mouse is :
  - slow (we can see a latency)
  - Xorg eat 100% of cpu

There no such problem with nvidia blob (and nv driver IRRC).


Oprofile give me :

    62336 51.8948 libpixman-1.so.0.16.4
    22927 19.0867 libfb.so
    16548 13.7762 no-vmlinux
     6297  5.2423 Xorg

unfortunately I don't have debug symbol.


May be it is related to https://bugzilla.redhat.com/show_bug.cgi?id=538467 ?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-01-09 17:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09 17:36 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-25966-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-01-12 12:39   ` [Bug 25966] nv25 : rxvt scrolling is very slow bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-13 17:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-13 17:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-13 17:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-13 19:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-13 20:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-15 18:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-15 19:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-23 10:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-23 11:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-23 13:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-23 17:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-23 17:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-26 21:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-27 16:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-27 16:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-12 13:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-12 18:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-12 18:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-12 19:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09   ` 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-25966-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.