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 20144] New: 2D images broken on nv28 (EXA failure?)
Date: Mon, 16 Feb 2009 11:43:45 -0800 (PST)	[thread overview]
Message-ID: <bug-20144-8800@http.bugs.freedesktop.org/> (raw)

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

           Summary: 2D images broken on nv28 (EXA failure?)
           Product: xorg
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: pq-X3B1VOXEql0@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Created an attachment (id=22992)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22992)
Screencapture of broken 2D

bisected:
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.".


-- 
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:[~2009-02-16 19:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 19:43 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-20144-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-02-16 19:58   ` [Bug 20144] 2D images broken on nv28 (EXA failure?) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-16 20:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-16 20:44   ` 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-20144-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.