Comments on: The other way http://www.sebruiz.net/137 Sun, 14 Mar 2010 23:15:18 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Peter http://www.sebruiz.net/137/comment-page-1#comment-401 Peter Fri, 23 Jun 2006 10:20:02 +0000 http://www.sebruiz.net/137#comment-401 <p>Re: memtest as someone else mentions: memtest doesn't end after a while but when you choose to reboot.</p> <p>I had faulty RAM that would work ok when cold booting and fail when rebooting my linux server and prechoosing the memtest image in the boot loader. If I used the sequence "halt -p" and powering up the machine right after lights off the fault would not be detected. Symptomes were weird oopses during operations, sometimes halting the machine, sometimes it continued to run.</p> Re: memtest as someone else mentions: memtest doesn’t end after a while but when you choose to reboot.

I had faulty RAM that would work ok when cold booting and fail when rebooting my linux server and prechoosing the memtest image in the boot loader. If I used the sequence “halt -p” and powering up the machine right after lights off the fault would not be detected. Symptomes were weird oopses during operations, sometimes halting the machine, sometimes it continued to run.

]]> By: Scott Wheeler http://www.sebruiz.net/137/comment-page-1#comment-382 Scott Wheeler Wed, 21 Jun 2006 22:04:20 +0000 http://www.sebruiz.net/137#comment-382 <p>The times I've seen this it's been heat. When I had bad memory it caused random segfaults in everything, not just GCC.</p> <p>You mentioned dust, and mind you, that can significantly increase the heat on the CPU. Specifically heat-sink fins get clogged up with the stuff rendering them pretty ineffective. You can just pop off the heat-sink, the fan and all that jazz and put it under the sink and then let it dry.</p> <p>Another thing you can give a whirl is underclocking your system. If that solves the problem then you can be fairly certain that it was a heat issue...</p> The times I’ve seen this it’s been heat. When I had bad memory it caused random segfaults in everything, not just GCC.

You mentioned dust, and mind you, that can significantly increase the heat on the CPU. Specifically heat-sink fins get clogged up with the stuff rendering them pretty ineffective. You can just pop off the heat-sink, the fan and all that jazz and put it under the sink and then let it dry.

Another thing you can give a whirl is underclocking your system. If that solves the problem then you can be fairly certain that it was a heat issue…

]]> By: James http://www.sebruiz.net/137/comment-page-1#comment-380 James Wed, 21 Jun 2006 17:44:19 +0000 http://www.sebruiz.net/137#comment-380 <p>If make||make||make (etc) completes successfully, are you sure it's created valid objects? If the computer has a hardware problem it could be doing more than just segfaulting - you may have bad data in memory. In fact, you probably do.</p> If make||make||make (etc) completes successfully, are you sure it’s created valid objects? If the computer has a hardware problem it could be doing more than just segfaulting – you may have bad data in memory. In fact, you probably do.

]]> By: Bram Schoenmakers http://www.sebruiz.net/137/comment-page-1#comment-377 Bram Schoenmakers Wed, 21 Jun 2006 12:57:57 +0000 http://www.sebruiz.net/137#comment-377 <p>But we have a CPU Info applet as well, somewhere on kde-apps.org. It will show you the temperature (if you get it compiled, that is).</p> But we have a CPU Info applet as well, somewhere on kde-apps.org. It will show you the temperature (if you get it compiled, that is).

]]> By: superstoned http://www.sebruiz.net/137/comment-page-1#comment-375 superstoned Wed, 21 Jun 2006 11:24:02 +0000 http://www.sebruiz.net/137#comment-375 <p>Cooling might help very well, nice -n 19 won't... After all, nice just changes the priority, so other tasks might go first, and your system becomes more responsive. But on an idle system, it makes no difference whatsoever in the cpu time the niced process gets...</p> <p>In most biosses you can see the cpu temp. run a compile, and after a segfault, reboot and check the temp's... if they run high, that's your problem. You might be able to let the computer beep if the cpu temp gets above a certain treshold, btw.</p> Cooling might help very well, nice -n 19 won’t… After all, nice just changes the priority, so other tasks might go first, and your system becomes more responsive. But on an idle system, it makes no difference whatsoever in the cpu time the niced process gets…

In most biosses you can see the cpu temp. run a compile, and after a segfault, reboot and check the temp’s… if they run high, that’s your problem. You might be able to let the computer beep if the cpu temp gets above a certain treshold, btw.

]]> By: Aron Stansvik http://www.sebruiz.net/137/comment-page-1#comment-374 Aron Stansvik Wed, 21 Jun 2006 11:16:06 +0000 http://www.sebruiz.net/137#comment-374 <p>I've had this problem and it was bad RAM. memtest continues indefinately so if you're waiting for it to finish you will get gray hairs ;) It tests the memory in several passes, wait a couple of passes and if it isn't finding any errors you can be pretty sure it's not the RAM.</p> I’ve had this problem and it was bad RAM. memtest continues indefinately so if you’re waiting for it to finish you will get gray hairs ;) It tests the memory in several passes, wait a couple of passes and if it isn’t finding any errors you can be pretty sure it’s not the RAM.

]]> By: Thomas vK http://www.sebruiz.net/137/comment-page-1#comment-373 Thomas vK Wed, 21 Jun 2006 10:46:53 +0000 http://www.sebruiz.net/137#comment-373 <p>Perhaps a bit useless to say this also but a year ago I had my first shot at Gentoo so I had a lot to compile. I constantly got Segmentation Faults and blamed it on Gentoo (was the easiest way to go, hehe). But a friend of mine noted that my conclusion was wrong and I should look at my hardware. When my PC also regularly crashed while playing computer games and stuff like that I went inspecting more. I installed and configured lm_sensors and then saw that my CPU constantly was getting very hot (as much as 80°C while with my CPU it should never be more than 72!). I bought some cooling hardware (in my case a new CPU fan, a new case) and had some techie install it for me in the optimal way. After that it was still pretty hot but not so much to have it crash.</p> <p>Point is... you could look at your temperatures. :-) Either with software like lm_sensors but you could also reboot and go into the BIOS right after a Segmentation Fault (or after manually loading the CPU with software like burnCPU) and see the page Health Status. Normally you can see temperatures there. If they seem very high you need to fix that. :-)</p> <p>In any case: good luck and I hope you can beat this one!</p> Perhaps a bit useless to say this also but a year ago I had my first shot at Gentoo so I had a lot to compile. I constantly got Segmentation Faults and blamed it on Gentoo (was the easiest way to go, hehe). But a friend of mine noted that my conclusion was wrong and I should look at my hardware. When my PC also regularly crashed while playing computer games and stuff like that I went inspecting more. I installed and configured lm_sensors and then saw that my CPU constantly was getting very hot (as much as 80°C while with my CPU it should never be more than 72!). I bought some cooling hardware (in my case a new CPU fan, a new case) and had some techie install it for me in the optimal way. After that it was still pretty hot but not so much to have it crash.

Point is… you could look at your temperatures. :-) Either with software like lm_sensors but you could also reboot and go into the BIOS right after a Segmentation Fault (or after manually loading the CPU with software like burnCPU) and see the page Health Status. Normally you can see temperatures there. If they seem very high you need to fix that. :-)

In any case: good luck and I hope you can beat this one!

]]> By: Brad Hards http://www.sebruiz.net/137/comment-page-1#comment-372 Brad Hards Wed, 21 Jun 2006 09:00:55 +0000 http://www.sebruiz.net/137#comment-372 <p>Do you need some new hardware?</p> Do you need some new hardware?

]]> By: Lee http://www.sebruiz.net/137/comment-page-1#comment-371 Lee Wed, 21 Jun 2006 08:07:03 +0000 http://www.sebruiz.net/137#comment-371 <p>Try resetting your bios to default settings. If that fails, look for the memory timings, and put them to the highest numbers possible. It should push the memory less, and therefore be more reliable, if the problem IS memory.</p> <p>You might want to read the SIG-11 FAQ.</p> Try resetting your bios to default settings. If that fails, look for the memory timings, and put them to the highest numbers possible. It should push the memory less, and therefore be more reliable, if the problem IS memory.

You might want to read the SIG-11 FAQ.

]]> By: Seb http://www.sebruiz.net/137/comment-page-1#comment-370 Seb Wed, 21 Jun 2006 07:45:23 +0000 http://www.sebruiz.net/137#comment-370 <p>haha, I suppose I should put the side cover of my box back on then? Maybe after I clear the dust off it!</p> haha, I suppose I should put the side cover of my box back on then? Maybe after I clear the dust off it!

]]>