#12516 NORM Not Tri: Reimaging with fs-update fails if USB keyboard attached to other XO-4 USB port

[Zarro Boogs per Child]

#12516: Reimaging with fs-update fails if USB keyboard attached to other XO-4 USB
port
-------------------------------------------+--------------------------------
           Reporter:  greenfeld            |       Owner:  Quozl                            
               Type:  defect               |      Status:  new                              
           Priority:  normal               |   Milestone:  Not Triaged                      
          Component:  ofw - open firmware  |     Version:  Development build as of this date
         Resolution:                       |    Keywords:                                   
        Next_action:  diagnose             |    Verified:  0                                
Deployment_affected:                       |   Blockedby:                                   
           Blocking:                       |  
-------------------------------------------+--------------------------------

Comment(by Quozl):

 I have tested continuous XO-1.5 fs-update with the USB keyboard interrupt
 handler enabled, for 20 hours straight, with no exceptions reported.   A
 USB keyboard was directly attached.

 I have tested XO-1.5 fs-update with a USB keyboard and USB drive attached
 via a hub.  Failures occur, including:
  * a hang [http://dev.laptop.org/~quozl/z/1U2ZQO.txt 1],
 [http://dev.laptop.org/~quozl/z/1U2ZbK.txt 2], (keyboard works, drive
 doesn't work, USB ERROR),
  * a [http://dev.laptop.org/~quozl/z/1U2ZWt.txt Page Fault] (keyboard
 works, drive works),
  * a ''Bad hash for eblock#'', and
  * two instances of ''Short read of zdata file''.

 I have tested XO-1.5 fs-update with a USB keyboard attached via a hub, and
 a USB drive directly attached.  Failures occur, including:
  * a hang [http://dev.laptop.org/~quozl/z/1U2Zeg.txt 3], (keyboard works,
 drive doesn't work, USB ERROR),

 I have tested XO-1.5 fs-update with a USB drive attached via a hub, and a
 USB keyboard directly attached.  No failures occur, over 29 cycles.

 I have tested XO-4 fs-update with a USB bar code scanner attached.  The
 scanner appears as a keyboard.  No failures occur, over 24 cycles.

 Therefore the problem relates to the re-entrancy of the USB stack, or the
 interrupt handler, when specific models of USB keyboard or bar code
 scanner are used on XO-1.75 or XO-4, or attached via a hub on XO-1.5.

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