Hi,
I am (finally) playing a bit with coreboot. Thanks to the excellent work of Kyösti with the BBB I have USB output in place. Unfortunately what I see is not what I have hoped for... :)
coreboot-4.0-8859-gbfe1b41 Sun Apr 5 21:29:27 UTC 2015 ramstage starting... BS: BS_PRE_DEVICE times (us): entry 0 run 1 exit 0 BS: BS_DEV_INIT_CHIPS times (us): entry 0 run 2 exit 0 Enumerating buses... Mainboard IMB-A180 Enable. setup_bsp_ramtop, TOP MEM: msr.lo = 0xe0000000, msr.hi = 0x00000000 setup_bsp_ramtop, TOP MEM2: msr.lo = 0x20000000, msr.hi = 0x00000001 setup_uma_memory: uma size 0x20000000, memory start 0xc0000000 CPU_CLUSTER: 0 enabled DOMAIN: 0000 enabled memalign(boundary=8, size=96): failed: Tried to round up free_mem_ptr 00173190 to 001731f0 but free_mem_end_ptr is 0017318c
This is with level DEBUG/7... will recover tomorrow and can increase it if need be. I have not looked into it yet at all... but hints are welcome anyway :)
On Mon, 2015-04-06 at 02:15 +0200, Stefan Tauner wrote:
Hi,
I am (finally) playing a bit with coreboot. Thanks to the excellent work of Kyösti with the BBB I have USB output in place. Unfortunately what I see is not what I have hoped for... :)
coreboot-4.0-8859-gbfe1b41 Sun Apr 5 21:29:27 UTC 2015 ramstage starting... BS: BS_PRE_DEVICE times (us): entry 0 run 1 exit 0 BS: BS_DEV_INIT_CHIPS times (us): entry 0 run 2 exit 0 Enumerating buses... Mainboard IMB-A180 Enable. setup_bsp_ramtop, TOP MEM: msr.lo = 0xe0000000, msr.hi = 0x00000000 setup_bsp_ramtop, TOP MEM2: msr.lo = 0x20000000, msr.hi = 0x00000001 setup_uma_memory: uma size 0x20000000, memory start 0xc0000000 CPU_CLUSTER: 0 enabled DOMAIN: 0000 enabled memalign(boundary=8, size=96): failed: Tried to round up free_mem_ptr 00173190 to 001731f0 but free_mem_end_ptr is 0017318c
Hi
Same error was actually reported last week on #coreboot. Looks like our previous crossgcc toolchain with gcc-4.8.3 creates 0-sized heap segment.
$ grep heap build/cbfs/fallback/ramstage.map
Kyösti
On Mon, 06 Apr 2015 07:22:12 +0300 Kyösti Mälkki kyosti.malkki@gmail.com wrote:
On Mon, 2015-04-06 at 02:15 +0200, Stefan Tauner wrote:
Hi,
I am (finally) playing a bit with coreboot. Thanks to the excellent work of Kyösti with the BBB I have USB output in place. Unfortunately what I see is not what I have hoped for... :)
coreboot-4.0-8859-gbfe1b41 Sun Apr 5 21:29:27 UTC 2015 ramstage starting... BS: BS_PRE_DEVICE times (us): entry 0 run 1 exit 0 BS: BS_DEV_INIT_CHIPS times (us): entry 0 run 2 exit 0 Enumerating buses... Mainboard IMB-A180 Enable. setup_bsp_ramtop, TOP MEM: msr.lo = 0xe0000000, msr.hi = 0x00000000 setup_bsp_ramtop, TOP MEM2: msr.lo = 0x20000000, msr.hi = 0x00000001 setup_uma_memory: uma size 0x20000000, memory start 0xc0000000 CPU_CLUSTER: 0 enabled DOMAIN: 0000 enabled memalign(boundary=8, size=96): failed: Tried to round up free_mem_ptr 00173190 to 001731f0 but free_mem_end_ptr is 0017318c
Same error was actually reported last week on #coreboot. Looks like our previous crossgcc toolchain with gcc-4.8.3 creates 0-sized heap segment.
$ grep heap build/cbfs/fallback/ramstage.map
0017318c B _eheap 0017318c B _heap
yes, indeed. thanks.
http://review.coreboot.org/#/c/9283/19 fixed it for me
And with this I got my first coreboot hardware booting, yay.
As can be seen in the board status[1] the current code triggers the respective assertion: ASSERTION FAILED: file 'src/vendorcode/amd/agesa/f16kb/Proc/GNB/Modules/GnbInitKB/GfxSamuInitKB.c', line 165
There exists a related patch[2] in gerrit and it works for me (i.e., my IMB-A180-H boots and graphics still work but the error message is gone). I am unable to quickly determine any consequences... shall we merge it? Why wasn't it yet?
1: http://review.coreboot.org/gitweb?p=board-status.git;a=blob;hb=HEAD;f=asrock... 2: http://review.coreboot.org/#/c/5361/
-
Kyösti Mälkki -
Stefan Tauner