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 32933] New: Screen corruption with drm-nouveau-next
Date: Sun,  9 Jan 2011 02:37:31 -0800 (PST)	[thread overview]
Message-ID: <bug-32933-8800@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=32933

           Summary: Screen corruption with drm-nouveau-next
           Product: xorg
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Created an attachment (id=41786)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=41786)
Example of screen corruption

If I use drm-nouveau-next instead of master I get massive screen corruption
after some minutes working with X. The corruption never appears directly after
starting X, it takes several minutes to show up.

Restarting X hides the problem for a few minutes before the corruption
reappears.

DDX and libdrm are from git as of 08-Jan-2011.

I tried to use "EXAOptimizeMigration" "off" in xorg.conf, but this has no
effect.

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

             reply	other threads:[~2011-01-09 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-09 10:37 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-32933-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-01-09 11:09   ` [Bug 32933] Screen corruption with drm-nouveau-next bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-09 11:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-09 17:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-15  9:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-23 16:40   ` 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-32933-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.