Bug 27288

Summary: EXA corruption on small pixmaps
Product: xorg Reporter: Martin Peres <martin.peres>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: p.freedesktop, svenjoac
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Snapshot of the screen from my camera
none
What screenshots look like none

Description Martin Peres 2010-03-24 05:38:31 UTC
Created attachment 34401 [details]
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
Comment 1 Martin Peres 2010-03-24 05:38:52 UTC
Created attachment 34402 [details]
What screenshots look like
Comment 2 Sven Joachim 2012-11-20 17:38:41 UTC
Is this still a problem? I had noticed corruption of small pixmaps myself back in 2010 (usually after a suspend/resume cycle), but they have long been gone.
Comment 3 Martin Peres 2012-11-20 17:46:46 UTC
Yes Joachim. It was fixed a long time ago.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.