#9611 NORM Not Tri: Page fault on USB activity

[Zarro Boogs per Child]

#9611: Page fault on USB activity
---------------------------------+------------------------------------------
 Reporter:  wmb at firmworks.com    |                 Owner:  wmb at firmworks.com                
     Type:  defect               |                Status:  new                              
 Priority:  normal               |             Milestone:  Not Triaged                      
Component:  ofw - open firmware  |               Version:  Development build as of this date
 Keywords:                       |           Next_action:  code                             
 Verified:  0                    |   Deployment_affected:                                   
Blockedby:                       |              Blocking:                                   
---------------------------------+------------------------------------------
 This is very difficult to reproduce - I have seen it once in many hundreds
 of reboots - but fortunately I did a deep post-mortem when it happened.  I
 think I have found the root cause.  More details later...


 {{{
 USB2 devices:
 /pci/usb at 10,4/scsi at 1,0
 /pci/usb at 10,4/scsi at 1,0/disk
 USB1 devices:
 OLPC D1, 1 GiB memory installed, S/N SHF12345678
 OpenFirmware  CL1   Q3A15c Q3A

 Type the Esc key to interrupt automatic startup
 Page Fault
 ok ftrace
 l@                Called from remove-qh                 at  ff8e95c8
 remove-qh         Called from done-bulk-out             at  ff8ebcd0
 done-bulk-out     Called from bulk-out                  at  ff8ebdf4
 execute           Called from $call-self                at  ff82a80c
 $call-self        Called from $call-method              at  ff82a8ec
  ff9d45d8
 $call-method      Called from $call-parent              at  ff82a914
 $call-parent      Called from bulk-out                  at  ff8f5874
 bulk-out          Called from (execute-command)         at  ff8f6538
 (execute-command)  Called from execute-command          at  ff8f6700
         0
 execute-command   Called from retry-command?            at  ff8f6fe4
 retry-command?    Called from no-data-command           at  ff8f7120
 execute           Called from $call-self                at  ff82a80c
 $call-self        Called from $call-method              at  ff82a8ec
  ff9d4580
 $call-method      Called from $call-parent              at  ff82a914
 $call-parent      Called from no-data-command           at  ff8f79bc
 no-data-command   Called from unit-ready?               at  ff8f7dc8
 unit-ready?       Called from open                      at  ff8f8168
 execute           Called from $vexecute?                at  ff82841c
    Catch frame - SP: ff9fcf58   my-self: ff9d4580   handler: ff9fcbd8
 catch             Called from apply-method              at  ff82af88
 apply-method      Called from (apply-method)            at  ff82b2f8
 (apply-method)    Called from (open-node)               at  ff82b32c
 (open-node)       Called from open-node                 at  ff82b370
 open-node         Called from (open-dev)                at  ff82b5b8
    Catch frame - SP: ff9fcf9c   my-self: 0   handler: ff9fcbdc
 }}}

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