From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 22956] New: nv50: kms, random screen blinkage
Date: Sun, 26 Jul 2009 20:32:54 -0700 (PDT) [thread overview]
Message-ID: <bug-22956-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=22956
Summary: nv50: kms, random screen blinkage
Product: xorg
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: kamilkss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=28020)
--> (http://bugs.freedesktop.org/attachment.cgi?id=28020)
dmesg
when kms is off everything is fine, but with kms on screen seems to blink
randomly from time time whether I'm in shell~tty1 or when X is running. it
almost seems like a crtc timing issue. along with the screen blink there's one
horizontal bar/artifact at the same level as the cursor, both true for
shell~tty1 and xorg~gui. also upon entering xorg~gui I noticed fuzzy fonts as
if vert refresh rate was off but it was at 60Hz which happens to the max of my
lcd.
--
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-27 3:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 3:32 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-22956-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-07-27 3:34 ` [Bug 22956] nv50: kms, random screen blinkage bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-27 3:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-27 3:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-27 3:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-27 20:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-29 6:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-29 7:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-29 9:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-29 11:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-29 11:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-29 11:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-30 21:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-07-31 1:21 ` 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-22956-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.