From: "Suzuki K. Poulose" <suzuki@in.ibm.com>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: Christian Kujau <lists@nerdbynature.de>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: 3.4.0-rc1: No init found
Date: Fri, 06 Jul 2012 10:50:26 +0530 [thread overview]
Message-ID: <4FF6759A.3010901@in.ibm.com> (raw)
In-Reply-To: <CAOZdJXVhtxoiY0kvsC+zgrETgd_MxTR+nf+6JDMV5Y-osqVqaw@mail.gmail.com>
On 07/06/2012 04:06 AM, Tabi Timur-B04825 wrote:
> On Wed, Apr 4, 2012 at 7:36 AM, Suzuki K. Poulose <suzuki@in.ibm.com> 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
next prev parent reply other threads:[~2012-07-06 5:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 7:20 3.4.0-rc1: No init found Christian Kujau
2012-04-03 8:08 ` Benjamin Herrenschmidt
2012-04-03 17:18 ` Christian Kujau
2012-04-03 18:53 ` Christian Kujau
2012-04-04 12:36 ` Suzuki K. Poulose
2012-04-04 16:45 ` Christian Kujau
2012-04-10 7:23 ` Benjamin Herrenschmidt
2012-04-10 16:56 ` Christian Kujau
2012-07-05 22:36 ` Tabi Timur-B04825
2012-07-06 5:20 ` Suzuki K. Poulose [this message]
2012-04-10 5:47 ` Christian Kujau
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=4FF6759A.3010901@in.ibm.com \
--to=suzuki@in.ibm.com \
--cc=B04825@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lists@nerdbynature.de \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).