Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752242AbZI0NBw (ORCPT ); Sun, 27 Sep 2009 09:01:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751622AbZI0NBv (ORCPT ); Sun, 27 Sep 2009 09:01:51 -0400 Received: from mail-out.m-online.net ([212.18.0.10]:39347 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751420AbZI0NBu (ORCPT ); Sun, 27 Sep 2009 09:01:50 -0400 From: Andreas Schwab To: Geert Uytterhoeven Cc: Tim Abbott , Roman Zippel , linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org, Sam Ravnborg Subject: Re: [PATCH v2 2/2] m68k: Cleanup linker scripts using new linker script macros. References: <1253119466-19488-1-git-send-email-tabbott@ksplice.com> <1253119466-19488-3-git-send-email-tabbott@ksplice.com> <10f740e80909270258o6bde0f3dk720bd5b5c091ed2f@mail.gmail.com> X-Yow: The appreciation of the average visual graphisticator alone is worth the whole suaveness and decadence which abounds!! Date: Sun, 27 Sep 2009 15:01:51 +0200 In-Reply-To: <10f740e80909270258o6bde0f3dk720bd5b5c091ed2f@mail.gmail.com> (Geert Uytterhoeven's message of "Sun, 27 Sep 2009 11:58:06 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1339 Lines: 34 Geert Uytterhoeven writes: > On Wed, Sep 16, 2009 at 18:44, Tim Abbott wrote: >> Signed-off-by: Tim Abbott >> Cc: Geert Uytterhoeven >> Cc: Roman Zippel >> Cc: linux-m68k@lists.linux-m68k.org >> Cc: Sam Ravnborg > > 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." -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/