Hi, Paul, I made a timestamp log by the following steps. 1. 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. Joe From: paulepan...@users.sourceforge.net To: coreboot@coreboot.org Date: Sat, 23 Jan 2016 12:49:45 +0100 Subject: [coreboot] [RFH] Board status upload of AGESA board like ASUS F2A85-M (other than ASRock E350M1) (was: [regression] Increased romstage boot time on ASRock E350M1 (AMD Family 14h)) Dear coreboot users, to rule out that the longer boot time issue with GCC 5 is related to AGESA, could users of an AGESA board please make an upload of the latest state with CBMEM time stamp collection enabled to board status? Please run with `make V=1` and maybe even upload that log or attach it to a reply to my message. That would be very helpful! (Also for the upcoming 4.3 release.) ASUS F2A85-M (LE), PC Engines APU1, and the AMD reference boards come to my mind. Thanks, Paul -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
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
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
