On Tue, 2 Dec 2014 14:10:33 -0800 Linus Torvalds <torva...@linux-foundation.org> wrote:
> So it appears that you can recreate this much more quickly than DaveJ > can recreate his issue. > > The two issues may be entirely unrelated, but the it is certainly > quite possible that they have some relation to each other, and the > timing is intriguing, in that 3.17 seems to be the first kernel > release this happened in. > > So at this point I think I'd ask you to just go back to your bisection > that you apparently already started earlier. I take it 3.16 worked > fine, and that's what you used as the good base for your bisect? > > Even if it's something else than what DaveJ sees (or perhaps > *particularly* if it's something else), bisecting when it started > would be very worthwhile. > > There's 13k+ commits in between 3.16 and 3.17, so a full bisect should > be around 15 test-points. But judging by the timing of your emails, > you can generally reproduce this relatively quickly.. No problem Linus. I'll try the full bisect and I post here later with the final result. -- Linux 3.17.0-dirty: Shuffling Zombie Juror http://www.youtube.com/DanielFragaBR http://exchangewar.info Bitcoin: 12H6661yoLDUZaYPdah6urZS5WiXwTAUgL -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/