From: Sean MacLennan <smaclennan@pikatech.com>
To: Denys Vlasenko <vda.linux@googlemail.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>,
Tim Abbott <tabbott@ksplice.com>, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: section .data..init_task
Date: Mon, 12 Jul 2010 20:34:35 -0400 [thread overview]
Message-ID: <20100712203435.08a3e90f@lappy.seanm.ca> (raw)
In-Reply-To: <20100628005900.28d4a8e0@lappy.seanm.ca>
On Mon, 28 Jun 2010 00:59:00 -0400
Sean MacLennan <smaclennan@pikatech.com> wrote:
> Anybody else seeing these messages?
>
> ppc_4xxFP-ld: .tmp_vmlinux1: section .data..init_task lma 0xc0374000
> overlaps previous sections ppc_4xxFP-ld: .tmp_vmlinux2:
> section .data..init_task lma 0xc03a2000 overlaps previous sections
> ppc_4xxFP-ld: vmlinux: section .data..init_task lma 0xc03a2000
> overlaps previous sections
>
> Or does anybody know what they mean? They started showing up in
> 2.6.35.
>
> Very easy to reproduce, so don't hesitate to ask for more info.
I had a bit of time, so I tracked this down. This patch seems to be
the culprit: http://lkml.org/lkml/2010/2/19/366
Specifically, this code:
/* The initial task and kernel stack */
- .data.init_task : AT(ADDR(.data.init_task) - LOAD_OFFSET) {
- INIT_TASK_DATA(THREAD_SIZE)
- }
+ INIT_TASK_DATA_SECTION(THREAD_SIZE)
If I change it back to:
/* The initial task and kernel stack */
.data..init_task : AT(ADDR(.data..init_task) - LOAD_OFFSET) {
INIT_TASK_DATA(THREAD_SIZE)
}
not only do the warnings go away, but the kernel now boots again!
Cheers,
Sean
next prev parent reply other threads:[~2010-07-13 0:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 4:59 section .data..init_task Sean MacLennan
2010-07-13 0:34 ` Sean MacLennan [this message]
2010-07-13 8:54 ` Sam Ravnborg
2010-07-13 15:26 ` Sean MacLennan
2010-07-13 15:33 ` Sam Ravnborg
2010-07-13 9:50 ` [ Sam Ravnborg
2010-07-22 22:27 ` [ Sean MacLennan
2010-07-22 22:33 ` [ Benjamin Herrenschmidt
2010-07-22 23:50 ` [PATCH] powerpc: fix .data..init_task output section Sean MacLennan
2010-07-23 13:58 ` Sam Ravnborg
2010-07-23 22:16 ` Benjamin Herrenschmidt
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=20100712203435.08a3e90f@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sam@ravnborg.org \
--cc=tabbott@ksplice.com \
--cc=vda.linux@googlemail.com \
/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).