From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Tim Abbott <tabbott@ksplice.com>,
Roman Zippel <zippel@linux-m68k.org>,
linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v2 2/2] m68k: Cleanup linker scripts using new linker script macros.
Date: Sun, 27 Sep 2009 15:01:51 +0200 [thread overview]
Message-ID: <m2ocowwngg.fsf@igel.home> (raw)
In-Reply-To: <10f740e80909270258o6bde0f3dk720bd5b5c091ed2f@mail.gmail.com> (Geert Uytterhoeven's message of "Sun, 27 Sep 2009 11:58:06 +0200")
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> On Wed, Sep 16, 2009 at 18:44, Tim Abbott <tabbott@ksplice.com> wrote:
>> Signed-off-by: Tim Abbott <tabbott@ksplice.com>
>> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
>> Cc: Roman Zippel <zippel@linux-m68k.org>
>> Cc: linux-m68k@lists.linux-m68k.org
>> Cc: Sam Ravnborg <sam@ravnborg.org>
>
> This patch must do something wrong, as it now fails to boot on ARAnyM:
>
> | CPU: Double bus fault detected !
> | CPU: Halting
>
> Haven't investigated why yet, though...
The problem is that _end no longer matches the end of the load segment.
Previously, the .data.init_task section was the last allocated item in
the linker script, now the last item is an align. This align does not
affect the memsize of the segment. The startup code expects the boot
info to be placed at _end, but the boot loader puts it at the end of the
load segment, which is the best it can do.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-09-27 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 16:44 [PATCH v2 0/2] Linker script cleanup patches for m68k Tim Abbott
2009-09-16 16:44 ` [PATCH v2 1/2] m68k: Make thread_info.h usable from assembly Tim Abbott
2009-09-27 9:55 ` Geert Uytterhoeven
2009-09-27 11:58 ` Sam Ravnborg
2009-11-20 7:56 ` Geert Uytterhoeven
2009-09-16 16:44 ` [PATCH v2 2/2] m68k: Cleanup linker scripts using new linker script macros Tim Abbott
2009-09-27 9:58 ` Geert Uytterhoeven
2009-09-27 13:01 ` Andreas Schwab [this message]
2009-09-27 17:57 ` Tim Abbott
2009-09-29 17:12 ` Andreas Schwab
2009-09-30 6:53 ` Sam Ravnborg
2009-10-04 8:32 ` Geert Uytterhoeven
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=m2ocowwngg.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tabbott@ksplice.com \
--cc=zippel@linux-m68k.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