From: Greg KH <greg@kroah.com>
To: Torrey Hoffman <thoffman@arnor.net>
Cc: ajoshi@kernel.crashing.org,
James Simmons <jsimmons@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] 2.5.70-bk15: RadeonFB dies at boot, and is undocumented
Date: Fri, 13 Jun 2003 17:03:06 -0700 [thread overview]
Message-ID: <20030614000306.GA2563@kroah.com> (raw)
In-Reply-To: <1055546532.1256.19.camel@torrey.et.myrio.com>
On Fri, Jun 13, 2003 at 04:22:13PM -0700, Torrey Hoffman wrote:
> With the Radeon framebuffer driver compiled in, 2.5.70-bk15 oopses very
> early during the boot process. The oops is visible in text mode but
> scrolls off the screen. (I really need to set up a serial console!)
Try a later -bk version, -bk17 fixes this I think, but to be safe, use
-bk18
thanks,
greg k-h
next prev parent reply other threads:[~2003-06-13 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 23:22 [OOPS] 2.5.70-bk15: RadeonFB dies at boot, and is undocumented Torrey Hoffman
2003-06-14 0:03 ` Greg KH [this message]
2003-06-16 18:42 ` Torrey Hoffman
2003-06-16 20:29 ` James Simmons
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=20030614000306.GA2563@kroah.com \
--to=greg@kroah.com \
--cc=ajoshi@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thoffman@arnor.net \
/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).