<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi, Paul,<br>I made a timestamp log by the following steps.<br>1. Build coreboot with check "Create a table of timestamps collected during boot ". Run coreboot.<br>2. build cbmem on target machine.<br>3. run "cbmem -t"<br><br>The log seems to be not enough. Is that what you want?<br>If yes, I will do it with gcc 4.9 again.<br><br>Joe<br><br><div>From: paulepanter@users.sourceforge.net<br>To: coreboot@coreboot.org<br>Date: Sat, 23 Jan 2016 12:49:45 +0100<br>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))<br><br><pre>Dear coreboot users,<br> <br> <br>to rule out that the longer boot time issue with GCC 5 is related to<br>AGESA, could users of an AGESA board please make an upload of the<br>latest state with CBMEM time stamp collection enabled to board status?<br> <br>Please run with `make V=1` and maybe even upload that log or attach it<br>to a reply to my message.<br> <br>That would be very helpful! (Also for the upcoming 4.3 release.)<br> <br>ASUS F2A85-M (LE), PC Engines APU1, and the AMD reference boards come<br>to my mind.<br> <br> <br>Thanks,<br> <br>Paul<br></pre><br>--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot</div> </div></body>
</html>