#11471 HIGH 1.75-so: Crash in mmp2_pcm_open and related code

[Zarro Boogs per Child]

#11471: Crash in mmp2_pcm_open and related code
-------------------------------------+--------------------------------------
           Reporter:  greenfeld      |       Owner:  saadia                           
               Type:  defect         |      Status:  new                              
           Priority:  high           |   Milestone:  1.75-software                    
          Component:  kernel         |     Version:  Development build as of this date
         Resolution:                 |    Keywords:                                   
        Next_action:  test in build  |    Verified:  0                                
Deployment_affected:                 |   Blockedby:                                   
           Blocking:                 |  
-------------------------------------+--------------------------------------

Comment(by corbet):

 Sigh.  So the original problem is not 100% solved either.  Over 140 s/r
 cycles I got a few of the original "nobody cared" messages last night.  I
 know what is going on: if no process has the device open, the IRQ handler
 is not registered, so there's no way for the driver to respond to spurious
 interrupts.

 At this point it's an annoyance; it won't happen during actual operation
 of the device, and, thus, won't interfere with that operation like it did
 before.  But, as annoyances go, it's *really* annoying.

 I know by now how to paper it over completely so we never see that message
 again; it won't be that hard.  But that's still not getting us any closer
 to understanding why the hardware is doing this.

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