Bug 20144 - 2D images broken on nv28 (EXA failure?)
Summary: 2D images broken on nv28 (EXA failure?)
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
Depends on:
Reported: 2009-02-16 11:43 UTC by Pekka Paalanen
Modified: 2009-02-16 12:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Screencapture of broken 2D (32.78 KB, image/png)
2009-02-16 11:43 UTC, Pekka Paalanen
no flags Details
Xorg log (37.10 KB, text/plain)
2009-02-16 11:58 UTC, Pekka Paalanen
no flags Details

Description Pekka Paalanen 2009-02-16 11:43:44 UTC
Created attachment 22992 [details]
Screencapture of broken 2D

d97e993072dc773ecfeb80b5e138b5e4598a1c3d is first bad commit
"exa: preparation for reintroducing driver-controlled pixmaps"

As you see from the screen capture, which oddly enough looks just like what I saw with my eyes, the 2d rendering is quite broken. More specifcally, pixmap handling, it seems. I should have a nice background picture, and only one aterm window drawn. There really is just one aterm, I moved it a few times.

With commit 60c8bb1391a51188a4981b4936c190c149b79b7f "default to autodetecting whether to enable the driver's kms paths", I tried to disable UTS, DFS and EXA render, but none of them changed anything.

Currently I'm running happily with commit 1e00c7d1e6edb7f6b4e6d12ef227d27413948f8f "shadowfb: clip copied regions to frontbuffer size.".
Comment 1 Pekka Paalanen 2009-02-16 11:58:24 UTC
Created attachment 22993 [details]
Xorg log

The Xorg log. The kernel log has no errors.
Comment 2 Maarten Maathuis 2009-02-16 12:32:36 UTC
Does 7b25a3019beba6342505fa16327a5bcd43669f90 fix it?
Comment 3 Pekka Paalanen 2009-02-16 12:44:13 UTC
Fixed in commit:

commit 7b25a3019beba6342505fa16327a5bcd43669f90
Author: Maarten Maathuis <madman2003@gmail.com>
Date:   Mon Feb 16 21:23:56 2009 +0100

    nv04: unbreak copy

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.