Hi Tom,
Nope. No emulation here. Thanks for trying tho ;).
--Seth
Tom Leete wrote:
>
> Seth Goldberg wrote:
> >
> > Hi,
> >
> > So it seems that CONFIG_X86_USE_3DNOW is simply used to
> > enable access to the routines in mmx.c (the athlon-optimized
> > routines on CONFIG_K7 kernels), so
Seth Goldberg wrote:
>
> Hi,
>
> So it seems that CONFIG_X86_USE_3DNOW is simply used to
> enable access to the routines in mmx.c (the athlon-optimized
> routines on CONFIG_K7 kernels), so then it appears that somehow
> this is corrupting memory / not behaving as it should (very
> technical, r
> No, actually the instability starts right after/when the root
> filesystem is mounted (it seems). I have no foreign modules installed
> when this error occurs. Even if I did, why would the Abit KA7 with the
> same [other] hardware and software NOT show this problem, even with all
> opts enab
Manfred Spraul wrote:
>
> > So it seems that CONFIG_X86_USE_3DNOW is simply used to
> > enable access to the routines in mmx.c (the athlon-optimized
> > routines on CONFIG_K7 kernels), so then it appears that somehow
> > this is corrupting memory / not behaving as it should (very
> > technical, r
> So it seems that CONFIG_X86_USE_3DNOW is simply used to
> enable access to the routines in mmx.c (the athlon-optimized
> routines on CONFIG_K7 kernels), so then it appears that somehow
> this is corrupting memory / not behaving as it should (very
> technical, right?) :)...
Do you use any u
> So it seems that CONFIG_X86_USE_3DNOW is simply used to
> enable access to the routines in mmx.c (the athlon-optimized
> routines on CONFIG_K7 kernels), so then it appears that somehow
> this is corrupting memory / not behaving as it should (very
> technical, right?) :)...
Feel free to go ove
6 matches
Mail list logo
