Posts by old_user2917

1) Questions and Answers : Unix/Linux : Computer hang up (Message 14309) Posted 12 Jul 2005 by old_user2917 Post: > I kind of wonder if deep in the Intel Fortran compiler we used for CPDN/BOINC > on Intel & Windows is some sort of hidden & random "crashAMD()" > routine! ;-) > > Indeed, it might even be the cause of a law suit: http://www.theregister.co.uk/2005/07/12/amd_vs_intel_code/
2) Questions and Answers : Unix/Linux : Computer hang up (Message 5049) Posted 4 Oct 2004 by old_user2917 Post: I have experienced a very similar problem. Running result name 03e5_300029382_0 (I have applied the minor edit to the client_state.xml file) on boinc_4.05_i686-pc-linux-gnu. I have had two different machines lock up after running the experiment for varying periods of time (using the two machines I have just about limped into phase2). They do not respond to ctrl+alt+del, nor to the alt+SysRq magic keys and have to be powered down manually. I have tried running the machines with Mandrake 10 Official (kernel-2.6.3.16mdk) and SUSE 9.1 (kernel-2.6.5-7.108-default), while using the same hostname each time. I have tarred up my boinc directory to move it between machines and to back up between reinstallations. The two machines have the following spec: 1. AMD Duron 800MHz, 512MB PC133 SDRAM, VIA KT133 chipset. 2. AMD Athlon 2500+, 512MB PC2700 DDR RAM, NVIDIA nForce2 chipset. I run the experiment with the following command: mv boinc.log boinc.old.log && ./boinc_4.05_i686-pc-linux-gnu >>boinc.log 2>>error.log There are no errors in the error log and nothing beyond the standard entries in the other log. There are no clues in my syslog or kernel logs to indicate why the machines have frozen. I have eliminated overheating as a possible cause by using additional case fans, indeed on at least one occasion the computer has locked up after a clean boot, before it has had the chance to warm up. Given these problems an the fact that I don't wish to ruin my computers I don't feel I can carry on with this experiment. Meanwhile my AMD64 machine is running a different result (2m1q_100143119_0) without problems.