public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, adaplas@pol.net
Subject: Re: Radeon FB troubles with recent kernels
Date: Tue, 15 Feb 2005 09:38:43 +1100	[thread overview]
Message-ID: <1108420723.12740.17.camel@gaston> (raw)
In-Reply-To: <20050214203902.GH15058@waste.org>

On Mon, 2005-02-14 at 12:39 -0800, Matt Mackall wrote:
> On my Thinkpad T30 with a Radeon Mobility M7 LW, I get interesting
> console video corruption if I start GDM, switch back to text mode,
> then stop it again. X is Xfree86 from Debian/unstable or X.org 6.8.2.
> 
> The corruption shows up whenever the console scrolls after X has been
> shut down and manifests as horizontal lines spaced about 4 pixel rows
> apart containing contents recognizable as the X display. Switch from
> vt1 to vt2 and back or visual bell clears things back to normal, but
> corruption will reappear on the next scroll.
> 
> This has appeared in at least 2.6.11-rc3-mm2 and rc4.

Appeared ? hah... that's strange. X is known to fuck up the chip when
quit, but I wouldn't have expected any change due to the new version of
radeonfb. From what you describe, it looks like an offset register is
changed by X, or the surface control.

My patch did not change any of radeonfb accel code though...

I'll catch up with you on IRC ...

Ben.



  reply	other threads:[~2005-02-14 22:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 20:39 Radeon FB troubles with recent kernels Matt Mackall
2005-02-14 22:38 ` Benjamin Herrenschmidt [this message]
2005-02-14 23:08   ` Benjamin Herrenschmidt
2005-02-15  0:02     ` Antonino A. Daplas
2005-02-15  0:20     ` Matt Mackall
2005-02-15  1:07       ` Benjamin Herrenschmidt
2005-02-15  6:06         ` Matt Mackall
     [not found] <3xVku-kH-15@gated-at.bofh.it>
2005-02-15  3:14 ` Vincent C Jones
2005-02-15 12:46   ` Benjamin Herrenschmidt
2005-02-15 12:50   ` Benjamin Herrenschmidt
     [not found] <3y1SR-5K6-1@gated-at.bofh.it>
     [not found] ` <3yatk-4mE-29@gated-at.bofh.it>
2005-02-15 15:07   ` Vincent C Jones
2005-02-15 22:02     ` Benjamin Herrenschmidt
2005-02-16  1:53       ` Vincent C Jones
2005-02-16  2:41         ` Benjamin Herrenschmidt
2005-02-16 14:39           ` Vincent C Jones
  -- strict thread matches above, loose matches on Subject: below --
2005-02-16 10:08 tvrtko.ursulin

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=1108420723.12740.17.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=adaplas@pol.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    /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