Comment 25 for bug 1310823

Revision history for this message
Žygimantas Beručka (zygis) wrote :

Okay, I fooled around here with several mainline kernel versions, letting them run for a decent amount of time, just to make sure the bug is hit on resume.

3.13.0 – the bug IS triggered. I just booted, logged in and forgot about it. When I came back to it, it was sleeping; on resume the bug got triggered again.

3.12.19 (latest in 3.12 series) – the bug is NOT triggered. As a matter of fact, I am writing this after three suspend/resume cycles.

I suppose the bug was introduced early in the 3.13 series.