On Tue, Jul 1, 2014 at 10:45 AM, Kees Cook <keescook@xxxxxxxxxxxx> wrote: > On Fri, Jun 27, 2014 at 3:53 PM, John Stultz <john.stultz@xxxxxxxxxx> wrote: >> On Fri, Jun 27, 2014 at 1:37 PM, Kees Cook <keescook@xxxxxxxxxxxx> wrote: >> I've been continuing to try to bisect this down with >> 8d94b54d99ea968a9d188ca0e68793ebed601220 and >> e7f3d22289e4307b3071cc18b1d8ecc6598c0be4 reverted each step. It seems >> like it pops up somewhere between 3.15-rc6 and 3.15-rc7, but the >> bisection results are really inconsistent. I suspect it actually >> shows up earlier, its just its harder to trip the problem with the >> patches reverted, so I'm marking good commits that are actually bad. >> >> If you are seeing this on every bootup, it might be worth trying to do >> the bisection with the two commits above reverted to see if you can >> narrow it down any better? > > And now I can't reproduce it! I think I was being tricked by > filesystem corruption that spanned some of my test boots. I'm going to > start this over and try again. Yea. :( I've been starting over and over on this quite a bit as well. With those two patches reverted, it gets harder to reproduce reliably, but I'm still seeing trobule. Bisecting is still not pointing to anything obvious, my current earliest bad commit right now is: 2aafe1a4d451866e3e7b476e2fa0813b69b313c1. I'm still working on it, but its slow going. thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
