It seems I'm unable to narrow down the commit. I can assure (because I have tested this twice) the last bad kernel is
3.17.0-rc7-utopic (http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.17-rc7-utopic/) and the first good one 3.17.0-utopic (http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.17-utopic/) I did all the steps to spot the good commit. Here is the bisect log from git: git bisect start # good: [fe82dcec644244676d55a1384c958d5f67979adb] Linux 3.17-rc7 git bisect good fe82dcec644244676d55a1384c958d5f67979adb # bad: [bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9] Linux 3.17 git bisect bad bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9 # bad: [abc40bd2eeb77eb7c2effcaf63154aad929a1d5f] mm: numa: Do not mark PTEs pte_numa when splitting huge pages git bisect bad abc40bd2eeb77eb7c2effcaf63154aad929a1d5f # bad: [17c9c8232663a47f074b7452b9b034efda868ca7] ematch: Fix matching of inverted containers. git bisect bad 17c9c8232663a47f074b7452b9b034efda868ca7 # bad: [445f7f4d62628cb2971db884084d162ecb622ec7] r8152: fix the carrier off when autoresuming git bisect bad 445f7f4d62628cb2971db884084d162ecb622ec7 # bad: [6c0fd0df0c44d1129ab65fc28d17f23a1c006a0c] qlcnic: Remove __QLCNIC_DEV_UP bit check to read TX queues statistics. git bisect bad 6c0fd0df0c44d1129ab65fc28d17f23a1c006a0c # bad: [4324414f8ccae4997dd1e91646683679a4436959] qlcnic: Use qlcnic_83xx_flash_read32() API instead of lockless version of the API. git bisect bad 4324414f8ccae4997dd1e91646683679a4436959 # bad: [d61746b2e71bf612fb397b00242de5df5ba7f29a] ip_tunnel: Don't allow to add the same tunnel multiple times. git bisect bad d61746b2e71bf612fb397b00242de5df5ba7f29a # first bad commit: [d61746b2e71bf612fb397b00242de5df5ba7f29a] ip_tunnel: Don't allow to add the same tunnel multiple times. Built and tested all the commits, but none of them worked. Any ideas ? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386695 Title: [3.16.0-23] Resume from suspend/hibernation, GPU lock - possible regression To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1386695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
