From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 26733] Full-screen XV causes graphics lockup
Date: Wed, 24 Feb 2010 08:50:59 -0800 (PST) [thread overview]
Message-ID: <20100224165059.9DD30130102@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-26733-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
http://bugs.freedesktop.org/show_bug.cgi?id=26733
--- Comment #1 from Tavian Barnes <tavianator-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2010-02-24 08:50:59 PST ---
A drm module I compiled on the 21st works fine, so it looks to me like this
commit caused it: 966a2b2e31b4d7fd72733ebb78a74bf0054a3f85. And sadly that
commit fixes suspend for me, so I either get working full-screen XV or working
suspend.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-02-24 16:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 15:56 [Bug 26733] New: Full-screen XV causes graphics lockup bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-26733-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-02-24 16:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2010-02-25 4:48 ` [Bug 26733] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-03-20 23:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-03-24 14:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-03-29 13:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-01 4:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-01 9:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-08 17:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-08 18:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-08 18:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-08 18:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-10 12:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-14 14:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-17 19:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-18 5:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-19 11:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-28 19:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-26 11:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-26 12:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-06-22 5:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-05 2:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-10 18:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-11 4:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-11 20:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-13 19:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-13 21:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-20 15:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-23 14:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-29 16:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-09-04 13:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-10-13 19:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-02-12 23:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 3:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 15:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-01 16:01 ` 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=20100224165059.9DD30130102@annarchy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox