From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 33887] nouveau causes graphic corruption were you cant do anything
Date: Mon, 14 Feb 2011 10:17:08 -0800 (PST) [thread overview]
Message-ID: <20110214181708.ABDC42DC101@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-33887-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=33887
Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org
--- Comment #34 from Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org> 2011-02-14 10:17:07 PST ---
I was experiencing a similar problem with GeForce 6150SE nForce 430. After
rebuilding my kernel with https://bugs.freedesktop.org/attachment.cgi?id=43011
applied, and the problem went way.
More details in the downstream bug report: http://bugs.debian.org/613078
--
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:[~2011-02-14 18:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 3:15 [Bug 33887] New: nouveau causes graphic corruption were you cant do anything bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-33887-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-02-04 13:59 ` [Bug 33887] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 6:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 7:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 9:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 13:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 13:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 14:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 14:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 14:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 14:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 21:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 21:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 22:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 11:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 12:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 14:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 20:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 21:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 22:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 23:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 4:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 5:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 10:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 10:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 10:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-08 5:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-08 5:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 15:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 15:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 15:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 16:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-11 7:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-11 10:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-14 18:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2011-02-22 11:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-22 11:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-04-30 21:29 ` 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=20110214181708.ABDC42DC101@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 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.