Strange MXCSR messages?

[Matthew Dillon]

::should *NOT* be set to 1. Attempting to set them to 1 will result in a 
::general protection exception, which is probably what you're seeing here. 
::My guess is, the recent changes to how the signal code in the kernel 
::saves and restores the MXCSR register, introduced this bug, and not 
::NATA. I'll have a look later at the code in question.
::
::Cheers,
::-- 
::         Thomas E. Spanjaard
::         tgen at netphreax.net
:
:    Yah, its unrelated to nata.  I'll get mysqld built up and try to
:    figure out what is messing up the signal stack.  firefox and gtk
:    have the same problem.
:
:						-Matt

    Ok, I figured it out.  It's libc_r's thread code.  I have to implement
    the FP save format field so libc_r uses the correct fxsave or fnsave
    instruction.

    libc_r was saving and restoring with fnsave and frstor, and the
    kernel is using fxsave and fxrstor.

    I'm committing fixes right now.  Both the kernel and libc_r must be
    recompiled.

					-Matt
					Matthew Dillon 
					<dillon at backplane.com>