From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 54129] New: [bisected] Kernel 3.5.0 breaks KMS on Radeon RV250
Date: Mon, 27 Aug 2012 19:38:00 +0000 [thread overview]
Message-ID: <bug-54129-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=54129
Bug #: 54129
Summary: [bisected] Kernel 3.5.0 breaks KMS on Radeon RV250
Classification: Unclassified
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: mariofutire@googlemail.com
Created attachment 66187
--> https://bugs.freedesktop.org/attachment.cgi?id=66187
Screenshot of bad rendering
I run Fedora 17 and since they have shipped a kernel 3.5.X I have a lot of
artefacts when I log in KDE.
Kernel 3.4.6 works ok.
My hardware in a Thinkpad laptop with a
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility
FireGL 9000] (rev 02)
and I load the R200 microcode.
Basically, as soon as I log on KDE I have a lot of rectangular areas which are
left black.
They are 100% reproducible always with the same pattern (at least in the few
seconds before I logoff again), and they move around when I click or windows
are displayed.
If I pass the option radeon.modeset=0 to the kernel (in grub) there are no
artefacts, but of course XV support is not there so this is not really an
option as video player struggle a lot.
I managed to bisect the issue to the following commits:
bad ========= 3b7a2b2 drm/radeon: rework fence handling, drop fence list v7
skip ======== bb63556 drm/radeon: convert fence to uint64_t v4
good ======== d6999bc drm/radeon: replace the per ring mutex with a global one
"skip" here means that the kernel does not boot: after the linux penguin logo
is displayed on the top left of the screen, nothing else happens, even though I
am able to reboot pressing Ctrl-Alt-Del.
So there are 2 commits that could be responsible.
Please, let me know if there is anything I can provide on top of that.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-08-27 19:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 19:38 bugzilla-daemon [this message]
2012-08-27 19:38 ` [Bug 54129] [bisected] Kernel 3.5.0 breaks KMS on Radeon RV250 bugzilla-daemon
2012-08-27 20:04 ` bugzilla-daemon
2012-08-27 20:19 ` bugzilla-daemon
2012-08-27 20:26 ` bugzilla-daemon
2012-08-28 20:26 ` bugzilla-daemon
2012-08-28 21:06 ` bugzilla-daemon
2012-09-03 15:17 ` bugzilla-daemon
2012-09-03 15:22 ` bugzilla-daemon
2012-09-03 20:19 ` bugzilla-daemon
2012-09-08 6:48 ` bugzilla-daemon
2012-09-08 15:39 ` bugzilla-daemon
2012-09-09 9:47 ` 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-54129-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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