#11471 HIGH 1.75-so: Crash in mmp2_pcm_open and related code
Zarro Boogs per Child
bugtracker at laptop.org
Mon Dec 12 16:48:44 EST 2011
#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):
OK, forcing a resume with a keystroke did (the second time) give me a
storm of about 80 of those messages - without any 5ms gaps. Interesting.
I ran runin overnight (and more) with the suspend interval cut to a couple
of minutes and never saw this. Like my teenage daughter, the XO seems to
respond poorly to being awakened ahead of schedule. That said, I've only
seen it happen once, having now been through several s/r cycles.
Also interesting is that the interrupt does eventually go away, long
before it gets to the point of triggering the core kernel's spurious
interrupt handler. So my hack still works, it just takes a little longer
sometimes.
So we *could* maybe take the printk() out and declare victory. I didn't
do that before because I don't like sweeping weird problems like this
under the rug. It would really be nice to figure out why the hardware is
responding in such a strange way and fix the real problem.
(Also, sorry if my previous response seemed intemperate; I've had more
coffee and feel better now...)
--
Ticket URL: <http://dev.laptop.org/ticket/11471#comment:14>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list