From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 113891] New: [radeon] Display jitter
Date: Mon, 07 Mar 2016 14:29:01 +0000 [thread overview]
Message-ID: <bug-113891-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=113891
Bug ID: 113891
Summary: [radeon] Display jitter
Product: Drivers
Version: 2.5
Kernel Version: 4.4.4
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: jdelvare@suse.de
Regression: No
Since updating to kernel v4.4.4 (from v4.4.3), I get vertical jitter on my
display with almost every boot. The picture moves up and down with black
horizontal stripes. This makes the system pretty much unusable.
I bisected it to the following commit:
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.4.y&id=a83b349814dee660caff0a40a22ac2f166c94a8b
drm/radeon/pm: adjust display configuration after powerstate
I am now running v4.4.4 with this commit reverted and so far so good. My
hardware:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (Sapphire HD 6670)
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-03-07 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 14:29 bugzilla-daemon [this message]
2016-03-07 14:29 ` [Bug 113891] [radeon] Display jitter bugzilla-daemon
2016-03-08 8:46 ` bugzilla-daemon
2016-03-08 10:08 ` bugzilla-daemon
2016-03-08 16:33 ` bugzilla-daemon
2016-03-09 9:42 ` bugzilla-daemon
2016-07-18 8:58 ` 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-113891-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).