XO-1.75/Kernel/Issues: Difference between revisions

Revision as of 02:06, 4 January 2012

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.

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.

Revision as of 02:05, 4 January 2012 (view source) Quozl (talk \| contribs) (→‎hang, mmp2-pcm-audio mmp2-pcm-audio.0: resume) ← Older edit		Revision as of 02:06, 4 January 2012 (view source) Quozl (talk \| contribs) (→‎hang, mmp2-pcm-audio mmp2-pcm-audio.0: resume) Newer edit →
Line 12:		Line 12:

	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.		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.