From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Matt Mackall <mpm@selenic.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
ajoshi@shell.unixbox.com,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Radeon framebuffer weirdness in -mm2
Date: Fri, 21 Jan 2005 11:03:14 +1100 [thread overview]
Message-ID: <1106265794.18397.17.camel@gaston> (raw)
In-Reply-To: <20050120153921.11d7c4fa.akpm@osdl.org>
On Thu, 2005-01-20 at 15:39 -0800, Andrew Morton wrote:
> Matt Mackall <mpm@selenic.com> wrote:
> >
> > I'm seeing radeonfb on my ThinkPad T30 go weird on reboot (lots of
> > horizontal lines) and require powercycling to fix. Worked fine with 2.6.10.
>
> Which radeon driver? CONFIG_FB_RADEON_OLD or CONFIG_FB_RADEON?
>
> (cc Ben, who is the likely cuprit ;)
>
> Which -mm2, btw? 2.6.10-mm2 or 2.6.11-rc1-mm2?
>
> Did you try the corresponding -mm1?
/me curses possible BIOS crap ...
radeonfb tries to restore initial mode when the module is closed, which
wouldn't work for a VGA text thing in fact... I suspect something cause
driver remove() routines to be called on reboot, can you confirm ? Or is
it a module that gets removed ? It may well be a problem that has always
been there (regardless of the radeon driver version) and just triggered
by something the kernel does on reboot...
Ben.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
prev parent reply other threads:[~2005-01-21 0:04 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
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 [this message]
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=1106265794.18397.17.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=ajoshi@shell.unixbox.com \
--cc=akpm@osdl.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).