OK, I tried hard to trigger the bug and it does not. At the risk of cutting things short, I try the following:
git bisect good 5e01dc7b26d9f24f39abace5da98ccbd6a5ceb52 output: Bisecting: 12903 revisions left to test after this (roughly 14 steps) [8cf126d92791381632818df862fdbc89ab6f7572] Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip 14 steps. That means that if I keep my usage pattern of the past seven weeks, it can take up to 28 weeks to nail down the specific commit that (re)introduced the bug I am experiencing. The bug triggers after a combination of lid close/open and connecting/disconnecting power, so I will be artificially increasing the number of such events in an attempts to precipitate the bug faster. next: make -j `getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-custom cd .. mkdir second mv *.deb second/ cd second sudo dpkg -i linux-* it is building now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368908 Title: [Sony VAIO SVP13215CDB] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1368908/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
