From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: can't boot 2.6.0-test11
Date: Fri, 05 Dec 2003 01:36:46 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107058830818353@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107057525104512@msgid-missing>
2.6.0-test11 boots fine on my tiger4 machine, with or without David's
test11-ia64-031126 patch. Apparently the prime suspect of "percpu data
segment" doesn't do any damage to me.
My readelf -e looks like:
Program Headers:
Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flags Align
LOAD 0x0000000000010000 0xa000000100000000
0x0000000004000000
0x00000000004eef20 0x00000000004eef20 R E 10000
LOAD 0x0000000000500000 0xa0000001004f0000
0x00000000044f0000
0x0000000000088b00 0x0000000000088b00 RWE 10000
LOAD 0x0000000000590000 0xffffffffffff0000
0x0000000004580000
0x00000000000081d0 0x00000000000081d0 RW 10000
LOAD 0x00000000005a0000 0xa000000100590000
0x0000000004590000
0x00000000000625e4 0x0000000000096dd8 RW 10000
IA_64_UNWIND 0x00000000004801b0 0xa0000001004701b0
0x00000000044701b0
0x0000000000025e18 0x0000000000025e18 R 8
Bill Nottingham (notting@redhat.com) said:
>> > The AllocatePages() says you are trying to allocate
3377699721561477
>> > 4KB pages. Clearly not something you want. Is the output of readelf
-e
>> > on vmlinux decent?
>>
>> As much as I can tell, it is. Not that that means much from me.
>
>Comparing readelf output, one big difference is where it loads the
>percpu data segment:
>
>2.6.0-test11:
>
>Program Headers:
> Type Offset VirtAddr PhysAddr
> FileSiz MemSiz Flags Align
> LOAD 0x0000000000010000 0xa000000100000000
0x0000000004000000
> 0x00000000005a0c00 0x00000000005a0c00 RWE 10000
> LOAD 0x00000000005c0000 0xffffffffffff0000
0x00000000045b0000
> 0x00000000000084a8 0x00000000000084a8 RW 10000
> LOAD 0x00000000005d0000 0xa0000001005c0000
0x00000000045c0000
> 0x00000000000a3004 0x0000000000131e48 RW 10000
> IA_64_UNWIND 0x00000000004c8568 0xa0000001004b8568
0x00000000044b8568
> 0x0000000000029898 0x0000000000029898 R 8
next prev parent reply other threads:[~2003-12-05 1:36 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
2003-12-05 1:19 ` Stephane Eranian
2003-12-05 1:36 ` Chen, Kenneth W [this message]
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-107058830818353@msgid-missing \
--to=kenneth.w.chen@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