From: Ingo Molnar on 8 Jul 2010 03:20 * Mathieu Desnoyers <mathieu.desnoyers(a)efficios.com> wrote: > * Ma, Ling (ling.ma(a)intel.com) wrote: > > Hi Mathieu > > > > I did git revert as bellow > > Revert "x86, mem: Optimize memcpy by avoiding memory false dependece" > > > > This reverts commit 77ff5e49c20bb72a99a12bfb00dbf90b2302f087. > > And I found the machine will crash with your config file > > > > Could you revert the patch : 77ff5e49c20bb72a99a12bfb00dbf90b2302f087 on your > > machine, and check it again ? > > Hi Ling, > > I just successfully booted my machine 3 times in a row with a revert of > commit a1e5278e40f16a4611264f8da9e557c16cb6f6ed from -tip. This is actually > the same as reverting commit 77ff5e49c20bb72a99a12bfb00dbf90b2302f087, as > a1e5278e40f16a4611264f8da9e557c16cb6f6ed is simply a merge of that commit > (the diffs are exactly the same). > > Without this revert, the machine gets to: Please check latest -tip (2a74852 or later), the commit should be gone now. There's clearly some (boundary-condition?) bug in the assembly code of 77ff5e49c2. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|
Pages: 1 Prev: [tip:x86/apic] x86/apic/es7000_32: Remove unused variable Next: perf migration |