battery eeprom corruption during s/r test

[pgf]

i was running a suspend/resume test from os56. autowack-delay was set to d# 1000, and linux was doing:

while sleep 1
do
echo mem > /sys/power/state
done

some time (hours?) after this was started, the battery went into error mode -- red-light flashing. cause is "FF count", which implies eeprom corruption. the outlet into which the laptop was plugged didn't have a solid connection, so i'm not sure whether it was powered or not. watch-battery reports 67% charge.

eeprom contents:

ok watch-battery
AC:on  Battery: BYD LiFePO4  67% 6.86V 0.00A 29C error
FF count
ok
ok bat-dump-banks

Regs
           8  9  a  b  c  d  e  f   0  1  2  3  4  5  6  7  89abcdef01234567
ff9ecde8  ff 6a ff ff ff ff ff 38  ba ff ff ff 58 28 00 02  .j.....8:...X(..
ff9ecdf8  15 b6 ff ff ff ff ff ff  1c 89 00 01 ff ff ff ff  .6..............

Bank 0
           8  9  a  b  c  d  e  f   0  1  2  3  4  5  6  7  89abcdef01234567
ff9ecde8  ff ff ff ff ff de ff ff  ff ff ff ff ff 42 00 50  .....^.......B.P
ff9ecdf8  00 6a ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  .j..............

Bank 1
           8  9  a  b  c  d  e  f   0  1  2  3  4  5  6  7  89abcdef01234567
ff9ecde8  00 00 00 00 00 00 00 00  00 00 00 00 00 00 01 00  ................
ff9ecdf8  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 22  ..............."

Bank 2
           8  9  a  b  c  d  e  f   0  1  2  3  4  5  6  7  89abcdef01234567
ff9ecde8  09 08 1f 00 00 00 01 00  13 14 00 02 18 00 02 11  ................
ff9ecdf8  00 af 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ./..............
ok

[Quozl]

Ticket moved out of 1.5-software-final to 1.5-software-update as a result of a software manufacturing release triage meeting. Per ed, dsd, cjb, reuben, quozl.

[rsmith]

Latest release can detect corruption and recover.

[Quozl]

Discussed on IRC. Fix is in EC 2.0.1. Impractical to test, closing.