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 23741] New: Driver pixmaps cause pushbuf validation failure on mode change (nv28, KMS)
Date: Sun,  6 Sep 2009 04:20:01 -0700 (PDT)	[thread overview]
Message-ID: <bug-23741-8800@http.bugs.freedesktop.org/> (raw)

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

           Summary: Driver pixmaps cause pushbuf validation failure on mode
                    change (nv28, KMS)
           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


Roughly latest git of ddx, drm and libdrm. Xorg-server git version some weeks
old. Confirmed with a full nouveau/linux-2.6 git kernel.

NV28, KMS active. Issuing the command 'xrandr -s 800x600' resulted in a kernel
hang, a live lock one might say. This was worked around in nouveau/linux-2.6 in
the commit "drm/nouveau: bail out if validation fails repeatedly", which allows
the kernel to fail gracefully, killing only X instead of the whole system.

When 'xrandr -s 800x600' fails, monitor loses signal completely. With the
kernel workaround in place, X can be restarted and everything is good again.
Note, that sysRq force-fb does restore the mode, but not the virtual console
image.

Setting Option "EXAPixmaps" "false" in xorg.conf disables the bug, so it is
driver pixmap specific. Likely it does not affect NV50 family, or someone would
have noticed it.


-- 
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-09-06 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-06 11:20 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-23741-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-09-06 11:24   ` [Bug 23741] Driver pixmaps cause pushbuf validation failure on mode change (nv28, KMS) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-09-06 11:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-09-17 19:35   ` 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-23741-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.