Messages in this thread | | | Date | Wed, 02 May 2001 00:10:53 +0200 | From | Manfred Spraul <> | Subject | Re: Followup to previous post: Atlon/VIA Instabilities |
| |
> 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 unusual (binary only/with source) kernel modules?
mmx.c stores the current contents on the fpu registers into current->thread.i387.f{,x}save. If another module modifes the fpu registers and calls memmove it will cause fpu corruptions.
I checked that a few months ago, and no module in the main kernel tree does that.
-- Manfred - 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/
| |