>No real additional information. It still fails with the latest >release-2.6.11 tree. It sometimes recovers once or twice, but >not more than that. Something is getting trashed or not restored >correctly. At least it is easily reproduceable, which makes >problems much easier to track down.
I've established that the scratch FP registers need to be saved, but nobody is doing that. Attached (untested) patch does that (not paticularly elegantly, but should be functional). -Tony
fpsave.patch
Description: fpsave.patch
