Re: 2.6.9-mm1 : compile error & question

[remi . colinet]

Selon Vivek Goyal <vgoyal@xxxxxxxxxx>:

> Hi Remi,
>
> On Mon, 2004-10-25 at 03:30, Remi Colinet wrote:
>
> > Sections:
> > Idx Name          Size      VMA       LMA       File off  Algn
> >  0 .text         0037d80e  c0100000  00100000  00001000  2**12
> > <-- something wrong here for LMA used to be 0xc010 000
>
>
> This has been changed so that LMA (Load memory address) reflects the
> physical address where sections shall be loaded. This is required to
> make sure that a kexec boot can load a vmlinux image.

Does it mean that the .text LMA start address is going to be definitively 0010
0000, even for those who disable kexec in their .config file?

>
>
>
> >                  CONTENTS, ALLOC, LOAD, DATA
> > 26 .bss          0006dfa0  c06c6000  c06c6000  005c7000  2**12     <--
> > somthing wrong with LMA for .bss.
> >                  CONTENTS, ALLOC, LOAD, DATA
> > 27 .comment      0000c36f  00000000  00000000  00634fa0  2**0
> >                  CONTENTS, READONLY
> > 28 .debug_line   0021497b  00000000  00000000  0064130f  2**0
> > ...
> >
> > This is very strange. The .text LMA of the vmlinux file is at 0x__0__010
> > 0000 whereas, it used to be at  0x__c__010 0000.  But then, the .bss LMA
> > of the vmlinux file suddenly jump at 0x__c__06c 6000 instead of
> > 0x__0__06c 6000 which would have seemed more natural -0).  What can
> > cause this offset? I have look for the .bss section content. It contains
> > .bss data and .bss.page_aligned. The later seems to be the root of the
> > .bss LMA offset.  .bss.page_aligned contains then empty_zero_page and
> > the  swapper_pg_dir.
>
> This looks like a problem with the older binutils package. I had faced
> similar problem on one of the machines but it was resolved as soon as I
> switched to a newer binutils package.

My distro is effectively becoming old (FC1). Going to upgrade it.

Thanks
Remi


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/