Comment 34 for bug 1252266

> The reverse bisect indicates the following commit fixes the suspend
> issue:
>
> commit c1a15d08f497150a91ba4e61bab54b8f5c8b49b9
> Author: Roger Pau Monne <email address hidden>
> 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.

That can't be, I have no xen modules in use and this commit only
changes xen-blkback/blkback.c

Maybe it's easier to see what the first commit between 3.10 and
3.11-rc1 is that introduces an issue.
I could probably bisect this too, but make-kpkg takes an awful lot of
time because it always seems to rebuild everything - is there a way
around that?

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

This one won't wake up anymore, probably a kernel panic but the display
won't get initialized again, no network and nothing written to the log.

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

Nothing there yet, may try again later.