From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Kristofer T. Karas" <ktk@enterprise.bidmc.harvard.edu>
Cc: ajoshi@kernel.crashing.org,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Radeon in LK 2.4.21pre7
Date: 22 Jul 2003 14:55:14 +0200 [thread overview]
Message-ID: <1058878512.532.10.camel@gaston> (raw)
In-Reply-To: <1058679793.10948.47.camel@ktkhome>
On Sun, 2003-07-20 at 07:43, Kristofer T. Karas wrote:
> Ben, Ani, et al,
>
> Just tried Linux kernels 2.4.21pre6 and pre7 with my Radeon 8500LEE and
> have had some dreadful corruption problems related to pixel clearing
> during scroll and ypan. This is probably old news to you; so <aol>me
> too</aol>. I first noticed this in the -ac kernels, but a variant is
> now in mainline -pre.
>
> Problem #1: When scrolling, radeonfb fails to erase the portion of the
> screen at the bottom, leaving all sorts of random pixels in the bottom
> line. Further scrolling propagates these pixels upwards.
> See http://enterprise.bidmc.harvard.edu/~ktk/temp/radeonfb/screen-1.jpg
> (Sorry for camera-shake; hand-held in dim room...)
This looks like erase not working properly... This usually happens
after switching back from X as X tends to leave some garbage in some
engine registers, and is usually cured by switching to another console
(this is why I tend to force-reinit the accel engine on console switch).
Since your problem seem to not depend on XFree, I suspect something
else hairy is going on with the engine, I don't know what yet though,
I'll try to find some clue.
In the meantime, can you send me a dmesg output ?
Thanks,
Ben.
next prev parent reply other threads:[~2003-07-22 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 5:43 Radeon in LK 2.4.21pre7 Kristofer T. Karas
2003-07-22 12:55 ` Benjamin Herrenschmidt [this message]
2003-07-25 2:03 ` Kristofer T. Karas
2003-08-01 10:43 ` Benjamin Herrenschmidt
2003-07-20 20:28 Lars Ehrhardt
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=1058878512.532.10.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=ajoshi@kernel.crashing.org \
--cc=ktk@enterprise.bidmc.harvard.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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).