Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 12
|
![]() |
Author |
|
39er
Cruncher Canada Joined: Aug 10, 2006 Post Count: 28 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Problem Statement:
My O/S Suse 10.1 freezes every 2 days or so and I have to reboot. Background: I am running BOINC version 5.4.9.i686 in a P4 pc. Memory 1/2 meg. The system uses the onboard memory card and ethernet port. The BOINC agent is installed in a desktop folder and is started from the GUI icon "boinc". Looking with the KDE systems monitoring utility at the boinc process, the CPU is running flatout on that process. Could someone suggest a remedy for the freezup situation. Thank you very kindly for taking time to respond. -39er |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi 39er
Im also running suse 10.1 and boinc but my system is running stable with no problems. If you know the exact time and date of the freeze or close enough then go to your k menu select system then yast control centre then miscellaneous and in the right hand panel youll find view system log. Select this and then the /var/log/messages tab and it should give you an error message for the failure or freeze. hope this helps you. Keep us posted Slapshot |
||
|
39er
Cruncher Canada Joined: Aug 10, 2006 Post Count: 28 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Hi Slapshot,
Thanks for reply. I am going to watch it on next occurrence, although I am not certain if it would write something to this file since it appears that certain functions are dead. i.e the time stopped and it cannot be powered down normally. After a few mouse clicks the screen functions freeze as well. Anyway, I shall keep you posted. cheers, -39er |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
G'day 39er
Have you checked for overheating? Check the heatsink fan for dust buildup and check that the heatsink isn't loose. (I'm presuming that this is a relatively new problem). |
||
|
39er
Cruncher Canada Joined: Aug 10, 2006 Post Count: 28 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Hi Slapsshot,
My system froze twice today at 8:08 and 12:30 respectively. This never happened before. But here are excerpts from the log. Actually it does not mean much too me. Aug 28 22:45:01 linux-ve3fd su: (to beagleindex) root on none Aug 28 22:45:05 linux-ve3fd su: (to beagleindex) root on none Aug 28 23:41:44 linux-ve3fd syslog-ng[2145]: STATS: dropped 0 Aug 29 00:00:01 linux-ve3fd /usr/sbin/cron[4002]: (root) CMD ( /usr/sbin/awstats-update) Aug 29 08:53:03 linux-ve3fd syslog-ng[2109]: syslog-ng version 1.6.8 starting I rebooted at 8:53 ------------------------ Aug 29 11:53:04 linux-ve3fd syslog-ng[2109]: STATS: dropped 0 Aug 29 12:00:01 linux-ve3fd /usr/sbin/cron[4133]: (root) CMD ( /usr/sbin/awstats-update) Aug 29 12:37:35 linux-ve3fd zmd: NetworkManagerModule (WARN): Failed to connect to NetworkManager Aug 29 12:38:29 linux-ve3fd zmd: Daemon (WARN): Not starting remote web server This one is slightly different from above since it did not log the reboot as in the last line of above. If it is not a software/installation problem the it could very well be a heat problem as discussed in this tread. Should you spot any problems based on the log, please let me know. cheers, -39er |
||
|
39er
Cruncher Canada Joined: Aug 10, 2006 Post Count: 28 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
G'day Trog Dog Chruncher,
Thanks for the hint. It makes sense since the the PC does nothing else but crunch numbers and the CPU load is nearly 100%. The PC here is an older IBM Netvista. When I opened it up I was actually surprised by the small size of the heatsink/fan assembly. I shall certainly investigate your suggestion further. Thanks mate. cheers, -39er |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Remove the fan from the heatsink. Look between the cooling fins on the heatsink and blow out the dust. Clean the dust off the fan blades too. If the fan and heatsink are not dirty then the problem may be that there is not enough air moving in and out of the box which causes the air temperature inside the box to rise abnormally high. Blowing hot air at a hot CPU doesn't do much good so try running it with the case open. Just make sure curious cats and kids can't poke around inside.
Also, fans sometimes slow down when they get old. If the fan seems lazy then replace it. They don't cost much and it's a good investment if you intend to keep the computer for a while. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi 39er,
As Trog Dog suggested it could be temperature related, my wifes windows pc only crunches fine with no case sides on and the stock pentium fan is clean and running fine. My cpu has a layer of arctic silver thermal paste and a little enclosed evaporative gas cooler assembly on it to keep running continuously. I have also seen this before whilst browsing the suse forums and have found the thread I was looking for after some grey matter searching. The link is here http://www.linuxquestions.org/questions/showthread.php?t=452466 Also ther are a couple of things here to try about half way down is the cpu frequency scaling and the powersav demon. Give it a try and also suse 10.0 is doing same for some so here is a link to a thread for that but it could be mem timing power supply or cpu overheating. This could be as you are driving it harder than anyone predicted with a stock cooler when they designed it. They didn't think it would run 24/7 with 100 % load. Here's the link http://www.linuxquestions.org/questions/showthread.php?t=412884 Also mate there was a problem that I had myself when I installed it and I had to run a kernel specifically made by Nvidia for my 3d accelerated card an FX 5600. You dont by any chance have one of those do you. Also on the subject of temps there is a package you can install called GKRELLM which monitors pretty much everything from processor percentage to your e-mail and makes a Penguin dance if you have any LOL, But it does monitor cpu usage temp and hard disk activity. Dont give up and we'll get there mate Keep us posted with any news Slapshot |
||
|
39er
Cruncher Canada Joined: Aug 10, 2006 Post Count: 28 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Hello Trog Dog , Slapshot and Dagorath.
Thanks to all of you who haven taken time to reply. It is time to put this issue to bed now that it is obvious that it was a heat issue. The pc now runs with the cover off and it seems to run at least for 2 days without freezing up. There was no dust to speak off between the fins of the CPU heat sink but the fan/heatsink assembly is too small, IMHO. I will look for an additional fan somewhere and get the air circulating some more. Perhaps it will run with the cover on too. The pc is an old IBM Netvista "beater" and I am doing just that to it. Thanks again fellas, Cheers, 39er |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
39er,
Glad to hear you're getting it sorted out. Have you checked the CPU core voltage? Some BIOS-motherboard combinations allow you to play with the core voltage. Higher core voltage makes the CPU run hotter. If the core voltage is higher than called for in the specs for that CPU then you should be able to reduce the core voltage and reduce the temperature. I was just thinking that maybe you or perhaps a previous owner tried overclocking the CPU and raised the core voltage, a common practice in overclocking. They may have found the overclock did not work and may have forgot to set the voltage back to specification. If you go into the BIOS and find it does not allow tinkering with core voltage then obviously that's not the problem. If it does allow voltage adjustments then you might want to look up the voltage spec at the CPU manufacturer's website. The specs will be in a document called a Data Sheet. The trick is to make sure you've got the exact model number for your CPU when you look for the datasheet. |
||
|
|
![]() |