From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 22786] New: NV30: X hangs with KMS enabled in certain cases
Date: Wed, 15 Jul 2009 12:24:43 -0700 (PDT) [thread overview]
Message-ID: <bug-22786-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=22786
Summary: NV30: X hangs with KMS enabled in certain cases
Product: xorg
Version: 7.4
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: patmandin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
- With Option "EXAPixmaps" "on"
When enabled, X simply hangs at startup, just get a black screen with visible
mouse cursor.
- With Mesa/gallium nv30 backend (I know, unsupported, just in case it is the
same issue):
progs/trivial/tri hangs X somewhere in libdrm. gdb show me it is when
nouveau_pushbuf_flush() is called. The specific instruction seems to be
drmCommandWrite(..., DRM_NOUVEAU_GEM_PUSHBUF, ...). Not the first time it is
called, but the 3rd or 4th.
In both cases, disabling agp (nouveau.noagp=1) makes no change, X still hangs.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2009-07-15 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 19:24 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-22786-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-07-30 17:46 ` [Bug 22786] NV30: X hangs with KMS enabled in certain cases bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-08-16 12:11 ` 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-22786-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.