Re: 3.4.0-rc1: No init found

[Suzuki K. Poulose]

On 07/06/2012 04:06 AM, Tabi Timur-B04825 wrote:
> On Wed, Apr 4, 2012 at 7:36 AM, Suzuki K. Poulose <suzuki@xxxxxxxxxx> wrote:
>
> > > Not sure if this is related, but at the end of each kernel compilation,
> > > the following messages are printed:
> > >
> > > ------------
> > >     SYSMAP  System.map
> > >     SYSMAP  .tmp_System.map
> > >     WRAP    arch/powerpc/boot/zImage.pmac
> > > INFO: Uncompressed kernel (size 0x6e52f8) overlaps the address of the
> > > wrapper(0x400000)
> > > INFO: Fixing the link_address of wrapper to (0x700000)
> > >     WRAP    arch/powerpc/boot/zImage.coff
> > > INFO: Uncompressed kernel (size 0x6e52f8) overlaps the address of the
> > > wrapper(0x500000)
> > > INFO: Fixing the link_address of wrapper to (0x700000)
> > >     WRAP    arch/powerpc/boot/zImage.miboot
> > > INFO: Uncompressed kernel (size 0x6d4b80) overlaps the address of the
> > > wrapper(0x400000)
> > > INFO: Fixing the link_address of wrapper to (0x700000)
> > >     Building modules, stage 2.
> > >     MODPOST 24 modules
> > > ------------
> > >
> > > I started to see these messages in January (around Linux 3.2.0), but never
> > > investigated what it was since the produced kernels continued to boot just
> > > fine.
> >
> >
> > The above change was added by me. The message is printed when the 'wrapper'
> > script finds that decompressed kernel overlaps the 'bootstrap code' which
> > does the decompression. So it shifts the 'address' of the bootstrap code to
> > the next higher MB. As such it is harmless.
>
> I see this message every time when I build the kernel.  I know it's
> harmless, but is this something that can be "fixed"?  That is, can we
> change some linker script (or whatever) to make 0x700000 the default
> value?

You could do this by setting the link_address by checking your platform,
like some of the other platforms (e.g, pseries, ps3 ).

Or

we could add a parameter to the wrapper script to set the link_address ?

Ben, Josh,
What do you think ?

 Or maybe modify the wrapper script to just automatically find
> the right spot without printing a message?

We need the message there for people who have restriction of a fixed 
link address. This would help them to handle the situation accordingly
than blindly failing on boot.

Thanks
Suzuki

--
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/