#5391 BLOC Never A: Q2D05/6 bricks machines with bad RTC data

[Zarro Boogs per Child]

#5391: Q2D05/6 bricks machines with bad RTC data
----------------------------------+-----------------------------------------
  Reporter:  wmb at firmworks.com    |       Owner:  wmb at firmworks.com
      Type:  defect               |      Status:  new              
  Priority:  blocker              |   Milestone:  Never Assigned   
 Component:  ofw - open firmware  |     Version:  Q2D05            
Resolution:                       |    Keywords:                   
  Verified:  0                    |  
----------------------------------+-----------------------------------------

Comment(by wmb at firmworks.com):

 Fixed by svn 752.  Will be released as q2d07.

 This release needs to be deployed as soon as possible.  In manufacturing,
 it is critical to use this instead of Q2D05 or Q2D06.  In the field, it
 can wait until the next convenient update time.  If the machine has Q2D04
 or earlier, this bug will not be present.  If the machine has Q2D05 or
 Q2D06, everything will be okay so long as the RTC does not lose its data.
 The only ways in which the bug would manifest on a field machine would be
 if

 a) The RTC battery were to be removed (requires system dissassembly) or to
 fail (should not happen for several years).

 or

 b) Someone explicitly sets the RTC month field to 0 (not easy to do from
 Linux; could be done from OFW if you went out of your way).

-- 
Ticket URL: <http://dev.laptop.org/ticket/5391#comment:1>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system