From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: can't boot 2.6.0-test11
Date: Thu, 04 Dec 2003 22:55:09 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107057901709452@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107057525104512@msgid-missing>
>>>>> On Thu, 4 Dec 2003 16:56:20 -0500, Bill Nottingham <notting@redhat.com> said:
Bill> Trying to boot a 2.6test ia64 kernel here, I'm getting:
Bill> Loadin vmlinux...Loading Linux...
Bill> alloc.c(line 132):allocator: AllocatePages(2, 2, 3377699721561477, 0x40000000) failed (Not Found)
Bill> plain_loader.c(line 291):plain_elf64: AllocatePages(3377699721561477, 0x40000000) for kernel failed
Bill> Is the kernel just horribly misbuilt somehow, or is something else
Bill> going on?
In case it helps, attached is what the program headers of a good
vmlinux-2.6.0-test11 kernel should look like.
--david
Program Headers:
Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flags Align
LOAD 0x0000000000010000 0xa000000100000000 0x0000000004000000
0x000000000082e9b0 0x000000000082e9b0 R E 10000
LOAD 0x0000000000840000 0xa000000100830000 0x0000000004830000
0x000000000005cb80 0x000000000005cb80 RWE 10000
LOAD 0x00000000008a0000 0xffffffffffff0000 0x0000000004890000
0x0000000000008428 0x0000000000008428 RW 10000
LOAD 0x00000000008b0000 0xa0000001008a0000 0x00000000048a0000
0x0000000000169360 0x00000000001bc8b8 RW 10000
IA_64_UNWIND 0x0000000000781c58 0xa000000100771c58 0x0000000004771c58
0x000000000002e5f0 0x000000000002e5f0 R 8
Section to Segment mapping:
Segment Sections...
00 .text __ex_table .data.patch.vtop .data.patch.mckinley_e9 .IA_64.unwind_info .IA_64.unwind .rodata __ksymtab __ksymtab_gpl __kcrctab __kcrctab_gpl __ksymtab_strings .opd
01 .init.text .init.data .init.ramfs .init.setup __param .initcall.init .con_initcall.init .data.init_task .data.page_aligned .data.cacheline_aligned
02 .data.percpu
03 .data .got .sdata .sbss .bss
04 .IA_64.unwind
next prev parent reply other threads:[~2003-12-04 22:55 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 [this message]
2003-12-04 23:31 ` David Mosberger
2003-12-05 0:54 ` Luck, Tony
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-107057901709452@msgid-missing \
--to=davidm@napali.hpl.hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.