Re: Oops in 2.4.0-ac5

Ingo Molnar
2001-01-10T22:42:01Z

On Wed, 10 Jan 2001, Alan Cox wrote:

> > it. I could never persuade Ingo to use wrmsr_eio() and check the
> > return code, maybe this will change his mind. Extract from kdb v1.7.
>
> I have a patch from Ingo to fix this one properly. Its just getting tested

i prefer clear oopses and bug reports instead of ignoring them. A failed
MSR write is not something to be taken easily. MSR writes if fail mean
that there is a serious kernel bug - we want to stop the kernel and
complain ASAP. And correct code will be much more readable that way.

Ingo