From: Matthew Wilcox <matthew@wil.cx>
To: linux-ia64@vger.kernel.org
Subject: Re: elilo.efi causing Kernel Panic
Date: Thu, 09 Nov 2006 13:19:04 +0000 [thread overview]
Message-ID: <20061109131903.GM16952@parisc-linux.org> (raw)
In-Reply-To: <20061109124221.GL16952@parisc-linux.org>
On Thu, Nov 09, 2006 at 06:40:59PM +0530, Karthik Gopalakrishnan wrote:
> When I booted from the original elilo.efi binary, the console log was
> a bit different. I have listed it below. My efi binary seems to have
> detected some RAM Disk when this one doesn't. Hope this helps.
Yep, this is a known bug in some versions of elilo. 3.6 should have
this fixed ... if not, let us know.
next prev parent reply other threads:[~2006-11-09 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 12:42 elilo.efi causing Kernel Panic Matthew Wilcox
2006-11-09 12:46 ` Karthik Gopalakrishnan
2006-11-09 12:55 ` Karthik Gopalakrishnan
2006-11-09 12:59 ` Andreas Schwab
2006-11-09 13:12 ` Karthik Gopalakrishnan
2006-11-09 13:14 ` Karthik Gopalakrishnan
2006-11-09 13:19 ` Matthew Wilcox [this message]
2006-11-09 13:22 ` Karthik Gopalakrishnan
2006-11-09 13:32 ` Karthik Gopalakrishnan
2006-11-09 14:27 ` Karthik Gopalakrishnan
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=20061109131903.GM16952@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-ia64@vger.kernel.org \
/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