I didnot enable the serial output. So the booting is fast. Do you need me to add it back and try again?
Zheng
From: paulepanter@users.sourceforge.net To: fishbaoz@hotmail.com Date: Sun, 24 Jan 2016 22:15:24 +0100 Subject: [coreboot] Incorrect time stamps on Olive Hill (was: Board status upload of AGESA board like ASUS F2A85-M) CC: coreboot@coreboot.org
Dear Zheng,
Thank you very much!
Am Sonntag, den 24.01.2016, 07:28 +0000 schrieb Zheng Bao:
Hi, Paul, I made a timestamp log by the following steps.
- Build coreboot with check "Create a table of timestamps collected
during boot ". Run coreboot. 2. build cbmem on target machine. 3. run "cbmem -t"
The log seems to be not enough. Is that what you want? If yes, I will do it with gcc 4.9 again.
It looks like something else regressed on Olive Hill. At least I doubt that ramstage just takes 184 ms.
``` 12 entries total:
0:1st timestamp 2,284 10:start of ramstage 2,284 (0) 30:device enumeration 2,284 (0) 40:device configuration 2,302 (17) 50:device enable 2,366 (63) 60:device initialization 2,388 (22) 70:device setup done 2,430 (41) 75:cbmem post 2,430 (0) 80:write tables 2,430 (0) 90:load payload 2,443 (13) 15:starting LZMA decompress (ignore for x86) 2,445 (1) 16:finished LZMA decompress (ignore for x86) 2,473 (27) 99:selfboot jump 2,473 (0)
Total Time: 184 ```
In the past it looked like below.
``` $ more amd/olivehill/4.0-7005-gb9a0809/2014-10-08T13:44:17Z/coreboot_timestamps.txt 10 entries total:
10:start of ramstage 3,738 30:device enumeration 14,178 (10,439) 40:device configuration 479,198 (465,020) 50:device enable 2,381,475 (1,902,276) 60:device initialization 2,689,928 (308,453) 70:device setup done 3,440,623 (750,694) 75:cbmem post 5,244,342 (1,803,719) 80:write tables 5,249,290 (4,948) 90:load payload 5,574,542 (325,251) 99:selfboot jump 5,674,034 (99,491) ```
So I am actually not able to see if there is the same problem with Olive Hill as with the ASRock E350M1.
Thanks,
Paul