The problem in question manifests itself when the fast memcpy routine
is used both in user space and in the kernel. I don't have the report
in front of me (my ISP system is down right now), but the upshot is
that it is due to a conflict with the FPU save routine. Presumably it
will cause a problem with any user program that uses the FPU. I will
post a more complete report as soon as it is available.
-- Robert Krawitz <rlk@tiac.net> http://www.tiac.net/users/rlk/Member of the League for Programming Freedom -- mail lpf@uunet.uu.net Tall Clubs International -- tci-request@aptinc.com or 1-800-521-2512