After testing multiple kernel versions I found the last good one: 3.9.11 wireless-testing does not have minor versions (3.9.x) , so I'm bisecting v3.9 and v3.10
git bisect startgit bisect good v3.9git bisect bad v3.10 Output: ➜ wireless-testing $ git bisect start ➜ wireless-testing $ git bisect good v3.9 ➜ wireless-testing $ git bisect bad v3.10 Bisecting: 7345 revisions left to test after this (roughly 13 steps) [20b4fb485227404329e41ad15588afad3df23050] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs What to do now? Can I skip some kernel compilations looking at commit logs? (it took me one hour to compile linux-mainline). On Sat, Feb 22, 2014 at 4:02 PM, Oleksij Rempel <li...@rempel-privat.de>wrote: > Am 22.02.2014 16:57, schrieb Marco André Dinis: > > I followed the instructions from the link you gave me (and this wiki > > entry from Arch > > Linux: > https://wiki.archlinux.org/index.php/Kernels/Compilation/Traditional) > > > > Everything went well on compilation, but the connection is still slow. > > > > > > Now I'll have to bisect the kernel right? That implies testing various > > versions from the known working version (in this case 3.2) > > Yes, it will be easier for you to use precompiled kernels from kernel > ppa to limit number of test you need to do. If you can say: kernel 3.2 > is working and 3.3 is not working it will be great advantage. > > PS: i still have some doubts that is is kernel regression. But may be > there is some thing different between your and my hardware. > > > -- > Regards, > Oleksij > >
_______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
