linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org,
	linux-fbdev-devel@lists.sourceforge.net,
	benh@kernel.crashing.org
Subject: Re: Radeon framebuffer weirdness in -mm2
Date: Thu, 20 Jan 2005 20:05:30 -0800	[thread overview]
Message-ID: <20050120200530.4d5871f9.akpm@osdl.org> (raw)
In-Reply-To: <20050121035758.GH12076@waste.org>

Matt Mackall <mpm@selenic.com> wrote:
>
> Here are the symptoms:
> 
>  mm2: corruption of Tux logo at boot, corruption of display at
>  powerdown, lockup and LCD blooming on next warm boot when radeonfb
>  starts. Ben suggested I try some radeonfb options, but none seemed to
>  have any effect.
> 
>  mm1: no observed problems
> 
>  mm2 - above patches: corruption still occurs but no lockup on next
>  warm boot.

So we have multiple bugs?

Next suspects would be:

+cleanup-vc-array-access.patch
+remove-console_macrosh.patch
+merge-vt_struct-into-vc_data.patch

  reply	other threads:[~2005-01-21  4:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 23:21 Radeon framebuffer weirdness in -mm2 Matt Mackall
2005-01-20 23:39 ` Andrew Morton
2005-01-20 23:48   ` Matt Mackall
2005-01-21  0:01     ` Andrew Morton
2005-01-21  3:57       ` Matt Mackall
2005-01-21  4:05         ` Andrew Morton [this message]
2005-01-21  4:07           ` Andrew Morton
2005-01-21  6:09             ` Matt Mackall
2005-01-21 12:33               ` Roman Zippel
2005-01-21 16:36                 ` Antonino A. Daplas
2005-01-22  0:52                 ` Matt Mackall
2005-01-24  4:00               ` Benjamin Herrenschmidt
2005-01-21 16:36         ` Antonino A. Daplas
2005-01-21  0:03     ` Benjamin Herrenschmidt
2005-01-21  0:24       ` James Simmons
2005-01-21  0:03   ` Benjamin Herrenschmidt

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=20050120200530.4d5871f9.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).