[coreboot] ASUS KGPE-D16: Increase in boot time by 1 second

[Timothy Pearson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/03/2016 01:31 PM, Paul Menzel wrote:
> Dear Timothy, dear Damien,
> 
> 
> looking through the board status data, I noticed the boot time
> increased by one second for the ASUS KGPE-D16.
> 
> ```
> asus/kgpe-d16/4.3-584-gcc9963e/2016-03-25T19_52_04Z/coreboot_timestamps.txt:Total Time: 18,389,685
> asus/kgpe-d16/4.3-587-gec38c3d/2016-03-26T21_40_56Z/coreboot_timestamps.txt:Total Time: 19,425,140
> ```
> 
> Did the hardware configuration change, or did commit ec38c3d9
> (nb/amd/amdmct: Select max_lanes based on ECC presence or absence) [1]
> do that?
> 
> Maybe the command below shows you some pointers in the board status
> repository.
> 
> ```
> diff -ru asus/kgpe-d16/4.3-584-gcc9963e/2016-03-25T19_52_04Z asus/kgpe-d16/4.3-587-gec38c3d/2016-03-26T21_40_56Z/
> ```
> 
> 
> Thanks,
> 
> Paul

No, the hardware itself was not changed.  The patch was relatively
innocuous so I'm surprised the timestamps changed at all, let alone that
much.

To make diagnostics easier in the future, perhaps it would make sense to
add timestamped stages to the RAM initialization phase?  The problem
there is that there are multiple nodes starting up so there would need
to be a way to add each stage timestamp for a specific node.

- -- 
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
http://www.raptorengineeringinc.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJXAobdAAoJEK+E3vEXDOFbgwwH/0k9QhFGYdIWFVBeuwrdbgAe
b8CtweURRqTVwPcXGGKSB6xd0m/Y8LF/Wf2FccJsE2KDQlXj2WhlbHvDopkAY8Zn
2qYIWCWM0Xle5NFctH4tlC7IucygWrrglPd0G2ntYHgMR7jTrQsH07W7Et6aU73o
WpoWvC5UfO/tI6XYIdM8FPOFx97GI+xwAqrIPRwBttAC5QSjOdtCEjH+MgrEMrMU
28tahj9fwG6+cRwfE5H7FM3gdnxZjUnK9JNb6a9ZZGZP2L8AQNWgGXvYPVGN/cN+
hkpHDjxsCjo5VhW2WtXqQxQVbzXwcMH8kwkuwuS4buzg/NwiH6zJ0lfCKDceV/c=
=o/YF
-----END PGP SIGNATURE-----