[coreboot] STACK_SIZE pcengines apu1

[Aaron Durbin]

On Thu, Sep 10, 2015 at 4:34 PM, Maxime de Roucy
<maxime.deroucy at gmail.com> wrote:
> Le jeudi 10 septembre 2015 à 09:02 -0500, Aaron Durbin a écrit :
>> That's quite the stack usage.  It'd be interesting to know what's
>> using all that stack. Could you apply this patch and run w/ it? It'd
>> help narrow down at what point in the boot where the stack gets used
>> up.
>
> You will find the spew log of the modified coreboot you asked.
> (it's a reboot, not a boot… I don't know if that's change something).

BS: BS_DEV_INIT times (us): entry 0 run 358353 exit 0
CPU0: stack: 00148000 - 0014a000, lowest used address 00149a2c, stack
used: 1492 bytes
CBMEM:
IMD: root @ dffff000 254 entries.
IMD: root @ dfffec00 62 entries.
Moving GDT to dfffea00...ok
Finalize devices...
Devices finalized
agesawrapper_amdinitlate() returned AGESA_SUCCESS
agesawrapper_amdS3Save() returned AGESA_SUCCESS
SF: Detected MX25L1605D with sector size 0x1000, total 0x200000
SF: Successfully erased 4096 bytes @ 0xffff1000
SF: Detected MX25L1605D with sector size 0x1000, total 0x200000
SF: Successfully erased 4096 bytes @ 0xffff0000
BS: BS_POST_DEVICE times (us): entry 9377 run 3502 exit 113447
CPU0: stack: 00148000 - 0014a000, lowest used address 00148d34, stack
used: 4812 bytes

So I'd get either agesawrapper_amdinitlate() or
agesawrapper_amdS3Save(). In either case it's in AGESA.

> --
> Regards
> Maxime