The reverse bisect indicates the following commit fixes the suspend
issue:
commit c1a15d08f497150a91ba4e61bab54b8f5c8b49b9
Author: Roger Pau Monne <[email protected]>
Date: Wed Apr 17 20:18:55 2013 +0200
xen-blkback: print stats about persistent grants
That really doesn't make sense, but we can check it out. I can build a
3.11-rc1 and 3.11-rc2 kernel with this commit to now bisect for the original
bug.
Before starting the second bisect, can you give the latest mainline kernel a
test, to see if the issue was already resolved? It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty/
v3.13-rc4 is the current mainline kernel, but it has issues with
building, so a test kernel is not available for it. Depending on when
you read this comment, the 3.13-rc5 kernel may be available, since it is
released on Fridays:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc5-trusty/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252266
Title:
Corrupted low memory after resume from suspend after updating to saucy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1252266/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
