#10462 NORM -: XO-1 - On F14, sometimes rebooting of the system does not complete

[Zarro Boogs per Child]

#10462: XO-1 - On F14, sometimes rebooting of the system does not complete
------------------------------------+---------------------------------------
           Reporter:  mikus         |       Owner:                                   
               Type:  defect        |      Status:  new                              
           Priority:  normal        |   Milestone:                                   
          Component:  not assigned  |     Version:  Development build as of this date
         Resolution:                |    Keywords:  F14                              
        Next_action:  never set     |    Verified:  0                                
Deployment_affected:                |   Blockedby:                                   
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by mikus):

 Replying to [comment:1 dsd]:
 > So the system fails to boot, but you can't tell us what is on the
 screen?
 > Is that because you've got a full-on stream of never ending messages?
 COMMENT:

 I am reminded of when work started on F11 - then too, boot would often not
 complete (then it was a matter of problems accessing the root device).
 Since I encountered some "incomplete reboots" with xo1 os2, I wanted to go
 on record with "for me, booting F14 on XO-1 is not 100% reliable" -- as a
 potential place for problems.  [My systems have external USB devices
 plugged in - I suspect their presence affects internal timings - whenever
 I have a failure to boot, my first reaction is to unplug USB cables and
 try again.]

 Yes, I can't tell you what's on screen because the "where it left the
 tracks" has already scrolled off.  As I implied in the initial ticket
 description, if the system stalls it seems to be at a point (just?) before
 the "service started - [OK]" information.  In that situation, I believe
 the actual final lines that I see occur when the system does 'modprobe'.
 But, since what did scroll by (and is no longer on the screen) sometimes
 looks like an "invocation trace" output, I believe the problem lies in
 "unable to proceed" rather than within "the last thing shown".

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