XO-1.75/Kernel/Issues: Difference between revisions

From OLPC
Jump to navigation Jump to search
(the dpm_resume hang was proven to be caused by the serial driver not properly handling suspend and resume, workaround is to remove no_console_suspend)
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== hang, mmp2-pcm-audio mmp2-pcm-audio.0: resume ==
== hang, SET_BLOCK_COUNT ==


This is a hang with a repeating message:
No FIQ. No SysRq. Last console message ''mmp2-pcm-audio mmp2-pcm-audio.0: resume''. Always preceeded by a ''PM: Some devices failed to suspend''.
mmcblk0: error -110 sending SET_BLOCK_COUNT command, response 0x0, card status 0x700


<trac>11137</trac>
Jon Nettleton says known problem. Caused by interrupted suspend, and during the unwind of the resume it hangs.
<trac>11525</trac>

<trac>11528</trac>
Can be worked around by removing the audio driver from the kernel.

Disabling runin-sound has no effect.

Seen within half an hour if SUS_TIME is set to 3000. Rarely or never seen if SUS_TIME is set to 10000.

Theory: once a suspend takes too long, the RTC alarm goes off before suspend has finished, and the suspend is interrupted, leading to this issue.

Impact: may trigger also with other wake sources, leading to a failed runin.

Latest revision as of 05:41, 13 January 2012

hang, SET_BLOCK_COUNT

This is a hang with a repeating message:

mmcblk0: error -110 sending SET_BLOCK_COUNT command, response 0x0, card status 0x700

<trac>11137</trac> <trac>11525</trac> <trac>11528</trac>