[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))

[Zheng Bao]

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: paulepanter at users.sourceforge.net
To: coreboot at 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 at coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20160124/a0df1ec1/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: timestamp_olivehill_gcc5.2.log
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20160124/a0df1ec1/attachment.log>