[coreboot] [patch] RE: Fam10 breakage

Myles Watson mylesgw at gmail.com
Fri Feb 26 15:14:18 CET 2010

On Fri, Feb 26, 2010 at 5:56 AM, Patrick Georgi <patrick at georgi-clan.de>wrote:

> Am 26.02.2010 03:48, schrieb Bao, Zheng:
> > This bug leads to the fact that we can not allocate enough space of
> > stack for each core. Then the data in the memory will be covered by AP
> > stack which doesnt know anything.
> >
> > That is the fact I can find. It is a bug in the linker. But we can not
> > fix each linker on coreboot developer, not to mention the fact I have
> > no idea how to submit the bug. The bug will be fixed in the
> > future. But when the fixed linker will come into our machine? So I
> > believe we need the workaround patch to avoid this problem.
> Just to make sure what the patch does: It simply removes the separate
> section and reserves an area at the same place, of the same size, just
> in a way that works with the linker?
I would like to double check this before it gets committed.  I only tried it
once, and the difference was very large.  3M of stack doesn't seem right.

diff -urN 5152/coreboot_ram.map build/coreboot_ram.map
--- 5152/coreboot_ram.map    2010-02-24 16:05:19.000000000 -0700
+++ build/coreboot_ram.map    2010-02-25 08:11:33.000000000 -0700
@@ -924,10 +924,10 @@
 002284a0 A _ebss
 002284a0 A _end
 00230000 A _stack
-00240000 A _estack
-00240000 A _heap
-00300000 A _eheap
-00300000 A _eram_seg
+00530000 A _estack
+00530000 A _heap
+005f0000 A _eheap
+005f0000 A _eram_seg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20100226/d2032647/attachment.html>

More information about the coreboot mailing list