From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
Date: Fri, 20 May 2011 12:12:04 GMT [thread overview]
Message-ID: <201105201212.p4KCC4as018162@demeter1.kernel.org> (raw)
In-Reply-To: <bug-34772-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=34772
--- Comment #6 from Michel Dänzer <michel@daenzer.net> 2011-05-20 12:11:38 ---
(In reply to comment #1)
> Anyway, things are *way* better with 2.6.38 than with 2.6.39, as with 2.6.39
> the kernel doesn't even get the colors correctly---everything that should be
> red becomes blue and so forth (any kind of endianness problem?).
That's probably nothing to do with the kernel directly but endianness bugs in
the X driver when acceleration is not available.
It would be interesting if you could bisect what broke acceleration with
radeon.agpmode=-1. Note that you should boot with radeon.no_wb=1 as well for
this, as CP writeback was only fixed during the 2.6.39 cycle (in commit
dc66b325f161bb651493c7d96ad44876b629cf6a).
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-05-20 12:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 23:26 [Bug 34772] New: [radeon] [R300] GPU lockups with when KMS is enabled bugzilla-daemon
2011-05-19 20:34 ` [Bug 34772] " bugzilla-daemon
2011-05-19 20:36 ` bugzilla-daemon
2011-05-19 20:37 ` bugzilla-daemon
2011-05-19 20:38 ` bugzilla-daemon
2011-05-19 20:38 ` bugzilla-daemon
2011-05-20 12:12 ` bugzilla-daemon [this message]
2011-05-20 14:31 ` bugzilla-daemon
2011-05-20 20:58 ` bugzilla-daemon
2011-05-21 9:16 ` bugzilla-daemon
2011-05-21 9:23 ` bugzilla-daemon
2011-05-21 9:34 ` bugzilla-daemon
2011-05-21 9:42 ` bugzilla-daemon
2011-05-21 9:47 ` bugzilla-daemon
2011-05-21 9:50 ` bugzilla-daemon
2011-05-21 9:56 ` bugzilla-daemon
2011-05-21 14:54 ` bugzilla-daemon
2011-05-21 15:34 ` bugzilla-daemon
2011-05-21 15:38 ` bugzilla-daemon
2011-05-21 15:42 ` bugzilla-daemon
2011-05-21 16:47 ` bugzilla-daemon
2011-05-21 16:59 ` bugzilla-daemon
2012-08-23 14:05 ` bugzilla-daemon
2012-10-28 18:51 ` bugzilla-daemon
2014-06-25 2:02 ` bugzilla-daemon
2014-06-28 10:45 ` 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=201105201212.p4KCC4as018162@demeter1.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).