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 27288] New: EXA corruption on small pixmaps
Date: Wed, 24 Mar 2010 05:38:31 -0700 (PDT)	[thread overview]
Message-ID: <bug-27288-8800@http.bugs.freedesktop.org/> (raw)

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

           Summary: EXA corruption on small pixmaps
           Product: xorg
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: martin.peres-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Created an attachment (id=34401)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=34401)
Snapshot of the screen from my camera

Hello,

I've had this bug for a long time now and I finally decided to report this bug
today.

There seem to have a transfer issue between the graphic ram and the computer's
ram (vram <--> gtt ?).

The problem usually appears on small pixmaps (download from screen ?), never
bigger than about 200*200.

But, it also occurs when doing screen captures. That's why I made a picture of
small pixmap corruption with my camera and also added the same picture, but
using a screenshot.

$ lspci|grep VGA                                                                
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1)

$ dmesg
Nothing interesting there. If it is a transfer issue, we won't see anything
there, right ?

Keep up the good work,

Martin


-- 
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-03-24 12:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 12:38 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-27288-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-03-24 12:38   ` [Bug 27288] EXA corruption on small pixmaps bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-20 17:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-20 17:46   ` 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-27288-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.