From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27206] Blurred screen with latest drm-next-radeon and KMS
Date: Sat, 20 Mar 2010 12:38:16 -0700 (PDT) [thread overview]
Message-ID: <20100320193816.4F5ED1300AB@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-27206-502@http.bugs.freedesktop.org/>
http://bugs.freedesktop.org/show_bug.cgi?id=27206
--- Comment #6 from DF5JT <ke4unq@bloatware.de> 2010-03-20 12:38:15 PST ---
(In reply to comment #5)
> Created an attachment (id=34264)
--> (http://bugs.freedesktop.org/attachment.cgi?id=34264) [details]
> dmesg from garbled screen
>
> Kernel is compiled from up to date git drm-next-radeon on x86 platform with
> Fedora 12 userland.
Plus all patches from:
http://people.freedesktop.org/~agd5f/pm2/
which could all be applied cleanly.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next prev parent reply other threads:[~2010-03-20 19:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 14:21 [Bug 27206] New: Blurred screen with latest drm-next-radeon and KMS bugzilla-daemon
2010-03-20 14:27 ` [Bug 27206] " bugzilla-daemon
2010-03-20 14:52 ` bugzilla-daemon
2010-03-20 15:10 ` bugzilla-daemon
2010-03-20 18:46 ` bugzilla-daemon
2010-03-20 19:36 ` bugzilla-daemon
2010-03-20 19:38 ` bugzilla-daemon [this message]
2010-03-21 1:09 ` bugzilla-daemon
2010-03-21 15:26 ` bugzilla-daemon
2010-03-22 7:59 ` bugzilla-daemon
2019-11-19 8:11 ` 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=20100320193816.4F5ED1300AB@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.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