From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 44800] Radeon HD 6450 CAICOS screen corruption and kernel crashes
Date: Mon, 16 Jan 2012 19:43:20 +0000 [thread overview]
Message-ID: <bug-44800-502-oWafsBzdAP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-44800-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #9 from Marko Kohtala <marko.kohtala@gmail.com> 2012-01-16 11:43:20 PST ---
Created attachment 55651
--> https://bugs.freedesktop.org/attachment.cgi?id=55651
Artefacts in X, screencapture
This capture was with the enable_mtrr_cleanup mtrr_spare_reg_nr=1 to kernel.
Here I started the X server from command line and only an xterm and a window
manager.
The artefacts appear to the window while I scroll the window pressing enter.
There was some constantly running horizontal artefacts, but they were
flickering and got erased immediately thus leaving no mark. Seems like it could
be ramdac reading bad for some scanlines, but more likely it goes on in the
framebuffer. The blue part lower in the window could be one of those caught. I
wonder if the squares in the xterm window are a result of that flickering, but
due to scrolling it does not get erased.
The blue and green spots came one by one slowly while doing something else in
the xterm. They stayed.
This happens only with this CAICOS card (I have an older radeon X300 that has
no problems, as well as a nVidia card goes without these problems). So I'd
expect whatever memory corruption there is, it is somehow in the CAICOS support
in kernel.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-01-16 19:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 13:53 [Bug 44800] New: Radeon HD 6450 CAICOS screen corruption and kernel crashes bugzilla-daemon
2012-01-15 6:00 ` [Bug 44800] " bugzilla-daemon
2012-01-15 13:55 ` bugzilla-daemon
2012-01-15 13:56 ` bugzilla-daemon
2012-01-15 13:57 ` bugzilla-daemon
2012-01-15 13:58 ` bugzilla-daemon
2012-01-15 14:13 ` bugzilla-daemon
2012-01-15 14:13 ` bugzilla-daemon
2012-01-16 11:23 ` bugzilla-daemon
2012-01-16 19:26 ` bugzilla-daemon
2012-01-16 19:43 ` bugzilla-daemon [this message]
2012-08-10 20:07 ` bugzilla-daemon
2012-08-14 13:16 ` bugzilla-daemon
2012-08-14 15:44 ` bugzilla-daemon
2012-08-19 18:09 ` bugzilla-daemon
2014-06-15 8:13 ` bugzilla-daemon
2014-06-16 4: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-44800-502-oWafsBzdAP@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;
as well as URLs for NNTP newsgroup(s).