> On Wed, 19 Sep 2001, Arjan van de Ven wrote:
> > If it were only 5%, I would vote for disabling the optimisation given the
> > number of problems; however it's 2x _and_ you can trigger the bug as normal
> > user from userspace too... so we need to fix the hardware/bios.
>
> But we really dont know what the hell that bit is doing. It might trigger
> some other obscure bugs and make things a real mess.
>
> Until we get some answer from VIA its IMHO a bad idea to start twiddling
> this bit willy-nilly on all machines.
That is the only way we can get information. We can twiddle this bit and
run memory performance tests on machines that aren't affected and
other stress tests on machines that are affected and see if we can see
if stability is impacted.
Additionaly the motherboards could be instrumented, and we could see
if there are any timing differences.
Of course VIA looking at what they have done and what that bit is
supposed to be is easiest as they have the schemantics of those
chips. But there is not reason to be limited to just that approach.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/