#9108 NORM Not Tri: Laptop stops booting after second dot

Zarro Boogs per Child bugtracker at laptop.org
Wed Dec 10 22:29:19 EST 2008


#9108: Laptop stops booting after second dot
--------------------------+-------------------------------------------------
 Reporter:  wad           |                 Owner:               
     Type:  defect        |                Status:  new          
 Priority:  normal        |             Milestone:  Not Triaged  
Component:  not assigned  |               Version:  not specified
 Keywords:                |           Next_action:  diagnose     
 Verified:  0             |   Deployment_affected:               
Blockedby:                |              Blocking:               
--------------------------+-------------------------------------------------
 On a production XO laptop from Uruguay, which has been activated, boot
 refuses to proceed past the second dot.

 If the check gamepad key is held down, however, the system boots fine,
 prompting for a nickname.

 If a developer key is provided, either on USB or SD card, the system shows
 the OFW countdown, then goes to pretty boot and stops after the second
 dot.  (The kernel has finished booting and has passed control to the
 initrd boot script.)

 This laptop arrived from the factory, was imaged with Uruguay's 656 build
 (and q2d16 firmware) and activated.  It then failed to boot properly
 (possibly with this problem, possibly with another) and was set aside.
 At a later date, it was upgraded to q2e18 firmware, and the current
 problem was seen.   The motherboard was removed and brought back to 1CC
 for analysis.

 The manufacturing data is perfectly normal for an Uruguay laptop.

 Interrupting the OFW countdown and booting manually result in a hang after
 the second dot.

 Looking at the console at that time, antitheft.py is failing to do
 something because mount is complaining that it can't find /sysroot in
 /etc/fstab or /etc/mtab.

 The NAND image was taken from this laptop and transferred to another
 laptop using save-nand and copy-nand, followed by reactivation of the
 cloned laptop.  This laptop operates fine.

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


More information about the Bugs mailing list