gene, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1067895/comments/10 : >"Christopher, 3.4.17-030417 is from >http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4.17-quantal/";
Thank you for clearing this up. >"A far as that bisection analysis with of those kernels is concerned, it's quite a few kernels to try. BTW, can't we exclude some of them? Like 3.3 and 3.5 are marked as EOL on kernel.prg, so I don't see any reason trying any of those." The fact a kernel is marked EOL on kernel.org is not a reason to not test it. One reverse bisects for the purposes of narrowing down the commit space in the fastest way possible. For more on reverse bisecting and it's benefits, please see https://wiki.ubuntu.com/Kernel/KernelBisection . >"As with the other ones, why would one try an earlier version, say 3.6.1 after 3.6.5" See above. Once the commit is identified, ideally the commit is applied verbatim to the downstream Ubuntu kernel so your problem is resolved. >", since it's almost always recommended to upgrade to the newest version anyways?" The fact one should be using the newest downstream Ubuntu kernel available for critical and security updates has nothing to do with reverse bisecting. >"However, if it is so important to find out where this particular fix was committed, I could instead try working through my local git repository. Switching, say, to 3.2 and comparing what it misses from the rtlwifi commits of master and other working branches. I'll try that, if you don't mind." While what you choose to do is up to you, I have provided you the fastest method to finding the commit that fixes your problem. So, consulting http://kernel.ubuntu.com/~kernel-ppa/mainline/ we now have: v3.2.33-precise/ v3.3-precise/ v3.3-rc1-precise/ v3.3-rc2-precise/ v3.3-rc3-precise/ v3.3-rc4-precise/ v3.3-rc5-precise/ v3.3-rc6-precise/ v3.3-rc7-precise/ v3.3.1-precise/ v3.3.2-precise/ v3.3.3-precise/ v3.3.4-precise/ v3.3.5-precise/ v3.3.6-precise/ v3.3.7-precise/ v3.3.8-quantal/ v3.4-precise/ v3.4-quantal/ v3.4-rc1-precise/ v3.4-rc2-precise/ v3.4-rc3-precise/ v3.4-rc4-precise/ v3.4-rc5-precise/ v3.4-rc6-precise/ v3.4-rc7-precise/ v3.4.1-quantal/ v3.4.2-quantal/ v3.4.3-quantal/ v3.4.4-quantal/ v3.4.5-quantal/ v3.4.6-quantal/ v3.4.7-quantal/ v3.4.8-quantal/ v3.4.9-quantal/ v3.4.10-quantal/ v3.4.11-quantal/ v3.4.12-quantal/ v3.4.13-quantal/ v3.4.14-quantal/ v3.4.15-quantal/ v3.4.16-quantal/ v3.4.17-quantal/ Hence, could you please test http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.4-rc2-precise/ ? Once complete, could you continue to reverse bisect mainline kernel versions until the last bad upstream kernel version, followed consecutively in version by the first good one is found? Thank you for your understanding. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067895 Title: 10ec:8176 rtl8192ce fails to recover after resume without shut down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1067895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
