[coreboot] eventlong & backtrace support
Rudolf Marek
r.marek at assembler.cz
Tue May 6 00:22:47 CEST 2014
Hi all,
I'm still suffering with following errors ONLY when using 4 core Trinity CPU on
the F2A85-M:
EventLog: EventClass = 2, EventInfo = 8040100.
Param1 = a00a, Param2 = 0.
Param3 = 0, Param4 = 0.
EventLog: EventClass = 2, EventInfo = 8040100.
Param1 = a00a, Param2 = 0.
Param3 = 0, Param4 = 0.
...
EventLog: EventClass = 2, EventInfo = 8040100.
Param1 = a00a, Param2 = 0.
Param3 = 0, Param4 = 0.
EventLog: EventClass = 2, EventInfo = 8040100.
Param1 = a00a, Param2 = 0.
Param3 = 0, Param4 = 0.
agesawrapper_amdinitpost failed: 4
Got past agesawrapper_amdinitpost
There is about 10? of them. System seems to boot fine. I still dont know what
those are but I decided to attack the problem via a backtrace.
I implemented a simple backtracer which I placed in the AGESA PutEventLog()
function. Once the function is visited I print:
agesawrapper_amdinitreset Fch OEM config in INIT RESET Done
EVENT BACKTRACE:
0xff82cfa7
0xff82f333
0xff82f377
0xff834e5a
0xff8349b2
0xff838bf3
0xff83663d
0xff837495
0xff861999
0xff8346f1
0xff82d661
0xff81db3c
0xff81a355
EVENT BACKTRACE:
...
Then with simple(stupid) script:
cat - | while read line ; do
unset A
if echo $line | grep ^0x > /dev/null ; then
A=`addr2line -e build/cbfs/fallback/romstage_xip.elf "$line" | tr -d "\n"`
fi
echo $line $A
done
It turns to:
agesawrapper_amdinitreset Fch OEM config in INIT RESET Done
EVENT BACKTRACE:
0xff82cfa7
/home/ruik/coreboot/src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c:662
0xff82f333
/home/ruik/coreboot/src/vendorcode/amd/agesa/f15tn/Proc/Common/S3SaveState.c:217
0xff82f377
/home/ruik/coreboot/src/vendorcode/amd/agesa/f15tn/Proc/Common/S3SaveState.c:256
0xff834e5a
/home/ruik/coreboot/src/vendorcode/amd/agesa/f15tn/Proc/GNB/Modules/GnbCommonLib/GnbLibPciAcc.c:96
0xff8349b2
/home/ruik/coreboot/src/vendorcode/amd/agesa/f15tn/Proc/GNB/Modules/GnbCommonLib/GnbLib.c:161
0xff838bf3
/home/ruik/coreboot/src/vendorcode/amd/agesa/f15tn/Proc/GNB/Modules/GnbInitTN/GnbRegisterAccTN.c:1241
0xff83663d
/home/ruik/coreboot/src/vendorcode/amd/agesa/f15tn/Proc/GNB/Modules/GnbInitTN/GfxLibTN.c:330
0xff837495
/home/ruik/coreboot/src/vendorcode/amd/agesa/f15tn/Proc/GNB/Modules/GnbInitTN/GnbEarlyInitTN.c:840
0xff861999
/home/ruik/coreboot/src/vendorcode/amd/agesa/f15tn/Proc/GNB/Common/GnbLibFeatures.c:99
0xff8346f1
/home/ruik/coreboot/src/vendorcode/amd/agesa/f15tn/Proc/GNB/GnbInitAtEarly.c:122
0xff82d661
/home/ruik/coreboot/src/vendorcode/amd/agesa/f15tn/Proc/Common/AmdInitEarly.c:270
0xff81db3c /home/ruik/coreboot/src/mainboard/asus/f2a85-m/agesawrapper.c:234
0xff81a355 /home/ruik/coreboot/src/mainboard/asus/f2a85-m/romstage.c:135
EVENT BACKTRACE:
It makes me wonder why we dont have such backtrace function available? Or did I
miss something? Anyway I'm attaching a diff how this was hacked in. I wont have
time for this for couple of days. It could be handy for someone else, or even
better make it a real feature :)
Thanks
Rudolf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: backtrace.patch
Type: text/x-diff
Size: 2760 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20140506/c3905aed/attachment.bin>
More information about the coreboot
mailing list