Re: frequent lockups in 3.18rc4
From: Dave Jones
Date: Thu Dec 11 2014 - 09:55:08 EST
On Fri, Dec 05, 2014 at 11:29:05AM -0800, Linus Torvalds wrote:
> So it must be some very particular corruption. I still vote for "let's
> see if Dave can narrow it down with bisection".
I vote for "plane ticket to drinking island".
So I've been continuing the bisect, leaving the 'good' cases running for
as long as a day and a half, and it's taking me down a path of staging
commits again (which is crap, as I don't even have that enabled).
git bisect start
git bisect bad 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9
git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6
git bisect bad ae045e2455429c418a418a3376301a9e5753a0a8
git bisect bad 53ee983378ff23e8f3ff95ecf99dea7c6c221900
git bisect good 2042088cd67d0064d18c52c13c69af2499907bb1
git bisect good 98959948a7ba33cf8c708626e0d2a1456397e1c6
git bisect bad 6f929b4e5a022c3ca806c1675ccb833c42086853
So either one of those 'good's actually wasn't, or I'm just cursed.
I'm going to lose access to this machine next week, so unless I see
this on different hardware in the new year, I'm running out of options.
(on the bright side, having people stare at various suspect code
throughout this thread does some to have yielded some good from all of
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/