XO-1.75/Kernel/Issues: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
(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)
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== hang, mmp2-pcm-audio.0 resume ==
== hang, SET_BLOCK_COUNT ==


This is a hang with the last serial console message:
This is a hang with a repeating message:
mmcblk0: error -110 sending SET_BLOCK_COUNT command, response 0x0, card status 0x700
mmp2-pcm-audio mmp2-pcm-audio.0: resume


<trac>11137</trac>
No FIQ. No SysRq. Always preceeded by a ''PM: Some devices failed to suspend''.
<trac>11525</trac>

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

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.

Instances:
* http://dev.laptop.org/~quozl/z/1RiDms.txt
* http://dev.laptop.org/~quozl/z/1RiEIr.txt

== hang, mmp2_pm_finish: Enable audio island ==

This is a hang shortly after the serial console message:
mmp2_pm_finish: Enable audio island

The time period may vary.

Only occurs with SUS_TIME not set to 3000.

Instances:

* http://dev.laptop.org/~quozl/z/1RiHT6.txt (75.904ms)
* http://dev.laptop.org/~greenfeld/temp/175bringup/os23-26f404e/screenlog.6-resumehang.bz2 (2.683ms)
* http://dev.laptop.org/~greenfeld/temp/175bringup/os23-26f404e/screenlog.3-ecfail1.bz2 (72.616ms)
* http://dev.laptop.org/~quozl/z/1Rhvmt.txt
* http://dev.laptop.org/~quozl/z/1RhvpV.txt

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>