I was able to use taskset -p <process id> to see what its current affinity was set to, and then use taskset -p 1 <process id> to set it to use processor #0.<br><a href="http://linuxcommand.org/man_pages/taskset1.html">
http://linuxcommand.org/man_pages/taskset1.html</a><br>-Rick<br><br><div class="gmail_quote">On Jan 21, 2008 9:00 AM, Rene Treffer <<a href="mailto:treffer@in.tum.de">treffer@in.tum.de</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Limiting to one cpu can be done with xen (set the cpu count/cpu) or by<br>using cpuset. Should work with virtually any kernel that has these<br>options enabled. The default CentOS kernel should come with cpuset<br>support, I'm not sure about the xen kernel, though.
<br><br>Just google for tutorials.<br><div class="Ih2E3d"><br>Rick Page wrote:<br>> I have read in other similar posts that this can be caused by<br>> multi-processor or multi-core processor systems. How do you force
<br>> ut3-bin to run off of one processor or one core? The fix at AMD's<br>> website seems to be a Windows patch, is there a Linux patch hiding out<br>> there somewhere? I am running CentOS 5.<br>> -Rick<br>
><br>> On Jan 20, 2008 10:07 PM, Masher <<a href="mailto:lists@brainless.us">lists@brainless.us</a><br></div><div class="Ih2E3d">> <mailto:<a href="mailto:lists@brainless.us">lists@brainless.us</a>>> wrote:
<br>><br>> I'm not sure if this is the appropriate place to ask about this.<br>> I was going to post a bug report, but there wasn't a UT3 category<br>> in bugzilla.<br>><br>><br>><br>
> I'm getting the following error message:<br>><br>><br>><br>> ScriptLog: Reset UTTeamGame_0<br>><br>> Critical: appError called:<br>><br>> Critical: Detected negative delta time - on AMD systems please
<br>> install<br>> <a href="http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html" target="_blank">http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html
</a><br>><br>><br>> Exit: Executing UObject::StaticShutdownAfterError<br>><br>> Log: appRequestExit(1)<br>><br>><br>><br>> I'm running UT3 on a Xen virtual server. It runs quite well, but
<br>> dies with this message every 2-8 hours.<br>><br>><br>><br>> It's emulating intel hardware and runs on intel hardware.<br></div>> Provider is <a href="http://linode.com" target="_blank">
linode.com</a> <<a href="http://linode.com" target="_blank">http://linode.com</a>>.<br><div class="Ih2E3d">><br>><br>><br>> I get the same error with CentOS 5 and Fedora 8 on a 2.6.18<br>> kernel. I've tried binding the process to one CPU, and it helps
<br>> some in the frequency of how often it happens, but still crashes.<br>><br>><br>><br>> I'm open to trying anything to make it work.<br>><br>><br>><br>> Thanks!<br>><br>>
<br><br><br></div>---<br>To unsubscribe, send a blank email to <a href="mailto:ut3-unsubscribe@icculus.org">ut3-unsubscribe@icculus.org</a><br>Mailing list archives: <a href="http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?64" target="_blank">
http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?64</a><br><br><br></blockquote></div><br>