ECO/7.1.2

Software ECO, 1/2/08

Title: Memory over-run; touchpad issues; include OFW

Trac items:

• 5800 - summary bug
  • 5744, 5719, 5317 - filling NAND
  • 5799 - mouse jumps to lower right of display

Description

1. If you create a large file that affectively fills the NAND memory, you will not be able to boot the laptop.
   • Critical bug as data is lost
   • Root cause:
2. Sometimes when you touch the touchpad, the mouse will jump to the lower right of the display. (Note that this bug fix will not fix ALL problems with jumpy mouse or touchpad issues).
   • Some laptops touchpads are so sensitive as to be un-usable.
   • Root cause:
3. We inadvertently included an earlier version of the firmware with the OS image in 653; so this build will include the latest firmware, which helps to recover if the internal battery is dislodged.
   • When the laptop is moved or shipped there is a possibility that the battery will be dislodged and the laptop will no longer boot.

Proposed Fix(es) Patches for Memory and Touchpad issues are included in the trac items.

Reviewers should include: Bernie, Andres, Jim, Scott

Testing:

1. Specific tests include creating the NAND memory problem following the description in the Trac item.
2. The touchpad must continue to work after upgrade; and should NOT show any jumping to lower right of display. This can only be a negative test since it is not possible to force this behavior.
3. Automated upgrading - this needs to be tested on a small number of laptops in house and then on a larger number of developers laptops; then finally rolled out, possibly in a controlled fashion.
4. The build must be installed on MP, CTest and B4 systems successfully
5. Upgrades from the previous release are successful.
6. A Fresh install (as mfg) is successful.
7. The 1 Hour Smoke Test must be performed, both using a fresh installation and an upgraded installation, looking specifically for regressions from the release reports, and thinking about possible interactions a fix might cause.
8. More than one SKU and keyboard type are to be used during this testing, to catch regressions in keyboard identification.
9. Any new hardware support must be tested explicitly (e.g. new keyboard type, new revision of a component).
10. When time permits, test builds should be used for testing by developers in the field to confirm the fixes.

Rollout:

In manufacturing this should be dropped in as quickly as possible.
In the field this should be part of an automated upgrade when released.