Re: "m68k: Cleanup linker scripts using new linker script macros." and old binutils (was: Re: [PATCH] m68k: Atari EtherNAT - Nicolas Pitre has a new email address)

From: Andreas Schwab
Date: Sun Jan 10 2010 - 07:44:38 EST


Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> writes:

> On Sun, Jan 10, 2010 at 05:56, Michael Schmitz
> <schmitz@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>>> > > I'll verify that on the new tree, and start bisecting. Sigh.
>>> >
>>> > Good luck!
>>>
>>> 7c5fd5619dc89fb52d2c2cf144fc6e4365427b86 is first bad commit
>>> commit 7c5fd5619dc89fb52d2c2cf144fc6e4365427b86
>>> Author: Tim Abbott <tabbott@xxxxxxxxxxx>
>>> Date: Â Sun Sep 27 13:57:55 2009 -0400
>>>
>>> Â Â m68k: Cleanup linker scripts using new linker script macros.
>>>
>>> Â Â Signed-off-by: Tim Abbott <tabbott@xxxxxxxxxxx>
>>> Â Â Tested-by: Andreas Schwab <schwab@xxxxxxxxxxxxxx>
>>> Â Â Cc: Roman Zippel <zippel@xxxxxxxxxxxxxx>
>>> Â Â Cc: Sam Ravnborg <sam@xxxxxxxxxxxx>
>>> Â Â Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
>>>
>>> :040000 040000 5bdbf7ce5dd4ea2f23669c6a6ec11192865b5bfa
>>> d3b7397533b0af6261747ccef3cff9cd40f6baf9 M Â Âarch
>>
>> Backing out that commit on the top of the tree results in a bootable
>> 2.6.33-rc2 for me
>>
>> The order of symbols in the system map is different (as you would expect)
>> but I don't see what implicit assumption would be violated.
>
> Tim, any clues? Michael is using gcc 3.3.6 and binutils 2.16.
> It works fine with my 4.1.2/2.18 vombo.

Most likely an alignment issue so that the bootinfo structure is not
found. At least that was the issue with previous incarnations of the
patch.

Andreas.

--
Andreas Schwab, schwab@xxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/