From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 33165] Nouveau + nvidia GT240 = unworkable
Date: Tue, 19 Jun 2012 18:56:16 +0000 [thread overview]
Message-ID: <bug-33165-8800-qZuKqBEuq6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-33165-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=33165
--- Comment #5 from Maarten Maathuis <madman2003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2012-06-19 11:56:16 PDT ---
You might want to actually post a recent kernel log showing your problem,
because the developers won't get anywhere with vague descriptions.
--
Configure bugmail: https://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:[~2012-06-19 18:56 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 19:06 [Bug 33165] New: Nouveau + nvidia GT240 = unworkable bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-33165-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-01-17 16:53 ` [Bug 33165] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-31 18:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19 18:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19 18:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19 18:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2012-06-19 21:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-22 5:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-22 19:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-20 18:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:19 ` [Bug 33165] [NVA3] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 20:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 22:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 9:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 9:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 14:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 14:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 15:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 15:48 ` [Bug 33165] [NVA3, NVA8] gpu lockup during driver probe bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 17:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 14:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 22:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-17 20:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 11:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 11:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 13:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 16:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 16:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 22:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-12 2:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-04 8:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-15 3:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-16 20:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-17 8:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-17 8:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-18 16:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-18 16:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-20 0:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-14 17:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-14 17:05 ` [Bug 33165] [NVA3] GDDR5 vram -> flickering screen (previously GPU lockup) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:25 ` 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-33165-8800-qZuKqBEuq6@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.