From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: can't boot 2.6.0-test11
Date: Fri, 05 Dec 2003 00:54:19 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107058568316184@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107057525104512@msgid-missing>
What does:
# objdump -fp vmlinux
say?
What version of elilo are you running? (Run "elilo -v" from the EFI prompt, I think).
-Tony
> -----Original Message-----
> From: linux-ia64-owner@vger.kernel.org
> [mailto:linux-ia64-owner@vger.kernel.org]On Behalf Of Bill Nottingham
> Sent: Thursday, December 04, 2003 1:56 PM
> To: linux-ia64@vger.kernel.org
> Subject: can't boot 2.6.0-test11
>
>
> Trying to boot a 2.6test ia64 kernel here, I'm getting:
>
> Loadin vmlinux...Loading Linux...
> alloc.c(line 132):allocator: AllocatePages(2, 2,
> 3377699721561477, 0x40000000) failed (Not Found)
> plain_loader.c(line 291):plain_elf64:
> AllocatePages(3377699721561477, 0x40000000) for kernel failed
>
> Is the kernel just horribly misbuilt somehow, or is something else
> going on?
>
> Bill
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2003-12-05 0:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 21:56 can't boot 2.6.0-test11 Bill Nottingham
2003-12-04 22:06 ` Stephane Eranian
2003-12-04 22:18 ` Bill Nottingham
2003-12-04 22:25 ` Bill Nottingham
2003-12-04 22:49 ` David Mosberger
2003-12-04 22:55 ` David Mosberger
2003-12-04 23:31 ` David Mosberger
2003-12-05 0:54 ` Luck, Tony [this message]
2003-12-05 1:19 ` Stephane Eranian
2003-12-05 1:36 ` Chen, Kenneth W
2003-12-05 2:37 ` Bill Nottingham
2003-12-05 2:43 ` Bill Nottingham
2003-12-05 4:15 ` David Mosberger
2003-12-05 15:23 ` Bill Nottingham
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=marc-linux-ia64-107058568316184@msgid-missing \
--to=tony.luck@intel.com \
--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