tree f0f9a1bd84561134dbbdcffc81fe534ab6f94bf4
parent 979ed1cce24fa0cffd4fe414b8a56e17ec032b14
author Nagaraju Goruganti <ngorugan@in.ibm.com> 1512029565 -0600
committer Nagaraju Goruganti <ngorugan@in.ibm.com> 1512131200 -0600

Roll errors after reaching Cap size

Fixes openbmc/openbmc#2687

-cap on error exists to deal with small flashes, right now the cap
is 100 for high severity errors and it is 10 for info(and below)
severity) errors.
-previous policy was to stop logging new errors once cap is reached
for high severity errors.
-based on feedback from field engineers, it's better to log new
errors, external tools will typically periodically read and store
errors, so we won't lose them.so the new policy now is to roll errors.

Change-Id: I18b509d81c076fcb80667300cbfda050027bb422
Signed-off-by: Nagaraju Goruganti <ngorugan@in.ibm.com>