#9249 NORM Not Tri: XO doesn't boot with Q2E32

[Zarro Boogs per Child]

#9249: XO doesn't boot with Q2E32
--------------------------+-------------------------------------------------
 Reporter:  mikus         |                 Owner:                                   
     Type:  defect        |                Status:  new                              
 Priority:  normal        |             Milestone:  Not Triaged                      
Component:  not assigned  |               Version:  Development build as of this date
 Keywords:                |           Next_action:  never set                        
 Verified:  0             |   Deployment_affected:                                   
Blockedby:                |              Blocking:                                   
--------------------------+-------------------------------------------------
 I have one "hardware weak" XO.  By that I mean -- sometimes when I install
 a new Joyride build on that XO I have trouble booting that new build --
 for example there is a jffs2 error that hangs the boot process.  This XO
 currently has four external USB devices.  My usual "bypass" when booting
 will not complete is to unplug some of the USB devices - that somehow
 avoids the occurrence of such a boot hang.  (I plug the devices back in
 after the system is up;  normally subsequent boots do not have trouble.)
 Once in a while even booting without USB devices has problems - I
 typically re-install the build (or even re-flash the entire nand) and then
 am able to again boot that XO.

 Most recently, that XO was running (and booting fine) with Joyride 2649
 and firmware Q2E30.  When I manually flashed (at the ok prompt) the
 firmware to Q2E32, the XO would *not* boot.  Went back to Q2E30 - the XO
 would still not boot.  Ended up installing Joyride 2650 (with Q2E31) - now
 it boots.

 [I suspect that particular XO either has a "weak" nand, or has "circuit
 timing" that differs from my other XOs (which don't give me trouble
 booting - I installed Q2E32 on them without a problem).]

 --------

 Manually transcribed output extracts from text console:

 {{{
 JFFS2 error: (321) jffs2_build_inode_pass1: child dir 'root' (ino #772782)
 of dir #722781 appears to be a hard link

 <Mikus note:  I've seen this message when booting did not hang;  I believe
 I've also seen it with other XOs.>

 ...

 | JFFS2 warning: (320) jffs2_get_inode_nodes: Eep. No valid nodes for ino
 #722782.
 | JFFS2 warning: (320) jffs2_do_read_inode_internal: no data nodes found
 for ino #722782
 | iget() failed for  ino #722782

 Installing tree 'f827...33e2' with mode 'thawed'.
 Wiping old /version/run/f827...33e2.

  <same three messages as marked with '|' above, but has (326)>

 rm: cannot stat '/sysroot/versions/run/f827...33e2':  Input/output error.
 Shallow-copy /versions/pristine/f827...33e2 into /versions/run/f827...33e2

  <same three messages as marked with '|' above>

  <and after a minute:>

 Traceback (most recent cmd last):
 File "/init", line 135, in <module>
   (ease_writer, run_init)
 File "/antitheft.py", line 31, in run
   return run_init_callback()
 File "/init", line 116, in run_int
   current = frob_symlink(boot_backup)
 File "/initutil.py", line 293, in frob_synlink
   tree_install('/sysroot')
 File "/upfs.py", line 66, in install
   getattr(self, self.mode, self.unknown_mode)(root)
 File "upfs.py", line 91, in thawed
   join(root, 'versions', 'run', x))

 OSError: [Error 5]  Input/output error
 }}}

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