I'm forwarding this to the list.
Bodo
--- Begin Message ---
I really don't know what fxsr is. But I think I have it. My servers are dual proc xeons. 2.6.8.1 with skas3 v7 (mostly).
# cat /proc/cpuinfo | grep fxsr
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
So you can only reproduce the problem when your use the sighandler? But when you use your patch the problem is not triggered (even with the sighandler)?
I'd be happy to try a patch. I only have production machines at the moment, so I may not be able to restart one for a week or two until some new ones arrive.
Regards, Peter
Bodo Stroesser wrote:Peter wrote:
I don't run TT mode UMLs. So, no I haven't tried that.
I don't know about the sighandler. The program runs as it was listed. It is running on a 'regular' server (Debian, and/or WBL3) with other processes running. And the host servers happen to be running other UMLs. I don't know if that information helps. (i.e. can a sighandler in another process on the UML or on the host cause this problem?)
I'd be happy to try out a skas patch - preferably if it just applied to the guest ;) To see if it fixes things or not.
Regards, Peter
I could try to create a patch, just for testing. What machine is your host? It probably has fxsr?
Bodo
--- End Message ---
