On 2013-01-22 17:12, Boris Ostrovsky wrote: >> Seen once over here. Correlated with raid-check. > > Then the answer from Gigabyte doesn't prove anything. You can also boot > Linux without seeing this problem in most cases.
That was my situation until the first time it hit. > Your BIOS does not have the required erratum workaround. We will provide > a patch to close that hole but since the problem is not easily > reproducible (and the erratum is also not easy to trigger) it may be > difficult to say whether it really helped with your problem. Can we think of certain loads/actions/etc that could help trigger the issue? Then if reproducing is easier we can better say if stuff is actually fixed after the workaround. Udo -- 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/
