On Tue, Mar 27, 2012 at 8:39 PM, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > On Mon, Mar 26, 2012 at 10:31 PM, Brian Gerst <brgerst@xxxxxxxxx> wrote: >> >> Yes, I see that commit. It looks like I have a different bug that is >> preventing the current head from booting then. Bisecting brought me >> to this commit instead. > > So try first just forcing DCACHE_WORD_ACCESS off (easily done by just > removing the "select" line in arch/x86/Kconfig). > > If that fixes things, it really is the word access code. > > But if the problem persists and it's a different bug, try to bisect it > with that DCACHE_WORD_ACCESS config option always forced off, just to > avoid any mixing of issues, exactly because we did have that one bug > that already got fixed that looked somewhat similar.. > > I'll test the current -git kernel on a F16 machine I have, just to > check. But I'm also assuming that there is something specific about > your setup, because otherwise I'd have expected many more reports > about this... > > Linus Commit f132c5be05e40 did fix this particular problem for me. There is another bug causing boot failure (seems to be in the DRM code), but bisecting initially fingered this patch. It was just looking at kernels in between this patch and the later fix. Sorry for the confusion. -- Brian Gerst -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
