From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 24462] New: r600: spread spectrum: flickering screen (bisected)
Date: Wed, 8 Dec 2010 16:18:41 GMT [thread overview]
Message-ID: <bug-24462-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=24462
Summary: r600: spread spectrum: flickering screen (bisected)
Product: Drivers
Version: 2.5
Kernel Version: 2.6.37-rc5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: kronos.it@gmail.com
Regression: Yes
2.6.37-rc5 exhibits a slight screen (notebook panel) flickering, mostly
noticeable around text (e.g. white-on-black in xterm) with occasional
horizontal lines; using 2.6.36 as known "good" kernel I've bisected the issue
down to this commit:
ba032a58d1f320039e7850fb6e8651695c1aa571 is the first bad commit
commit ba032a58d1f320039e7850fb6e8651695c1aa571
Author: Alex Deucher <alexdeucher@gmail.com>
Date: Mon Oct 4 17:13:01 2010 -0400
drm/radeon/kms: rework spread spectrum handling
This patch reworks spread spectrum handling to enable it
properly on lvds and DP/eDP links. It also fixes several
bugs in the old spread spectrum code.
- Use the ss recommended reference divider if available
when calculating the pll
- Use the proper ss command tables on pre-DCE3 asics
- Avoid reading past the end of the ss info tables
- Enable ss on evergreen asics (lvds, dp, tmds)
- Enable ss on DP/eDP links
Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
:040000 040000 2017e6abb9a12586686bcddb61479f2b158c9d7c
7e6117db061ef286ab6822455c65cf5492de7eaa M drivers
Hardware is a M76:
01:00.0 VGA compatible controller: ATI Technologies Inc M76 [Radeon Mobility HD
2600 Series]
dmesg is attached.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF Dev2Dev email is sponsored by:
WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next reply other threads:[~2010-12-08 16:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 16:18 bugzilla-daemon [this message]
2010-12-08 17:11 ` [Bug 24462] r600: spread spectrum: flickering screen (bisected) bugzilla-daemon
2010-12-08 20:27 ` bugzilla-daemon
2010-12-08 20:39 ` bugzilla-daemon
2010-12-08 20:47 ` bugzilla-daemon
2010-12-08 21:14 ` bugzilla-daemon
2010-12-08 22:12 ` bugzilla-daemon
2010-12-08 22:32 ` bugzilla-daemon
2010-12-08 23:05 ` bugzilla-daemon
2010-12-09 20:12 ` bugzilla-daemon
2010-12-17 0:43 ` bugzilla-daemon
2010-12-20 6:57 ` bugzilla-daemon
2010-12-29 22:48 ` bugzilla-daemon
2011-02-11 6:57 ` bugzilla-daemon
2011-02-11 7:32 ` bugzilla-daemon
2011-02-11 16:09 ` bugzilla-daemon
2011-02-12 1:17 ` bugzilla-daemon
2011-02-14 13:56 ` bugzilla-daemon
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-24462-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).