Re: weird restarts when compiling
Aggelidis Nikos wrote:
The voltages as the BIOS reports them:
Vcore = 1.258 V
+3.30 V = 3.274V
+5.00 V = 5.121V
+12.00 V = 11.870V
Not very useful here, since these may change under load I am afraid.
i hope by the end of the day i will be able to test the system with a
1100watt Tagan PSU {a friend just bought a monster pc!}.
Nice, this will help you eliminate one factor.
I will then run: make buildworld...
-nikos
PS: i can interup the process of builworld without causing any
problems to the system correct?
Certainly.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
The voltages as the BIOS reports them:
Vcore = 1.258 V
+3.30 V = 3.274V
+5.00 V = 5.121V
+12.00 V = 11.870V
i hope by the end of the day i will be able to test the system with a
1100watt Tagan PSU {a friend just bought a monster pc!}.
I will then run: make buildworld...
-nikos
PS: i can interup the process of builworld without causing any
problems to the system correct?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
It doesn't look like overheating, unless the thermal compound, heatsink and temperature monitor are not properly set. The only times I had reboots like that was due to a driver with an irq conflict, a driver accessing incorrect memory, or running out of space on a device (trying to write to non-existent address). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
On Jul 13, 2008, at 4:38 AM, Aggelidis Nikos wrote: FATAL ERROR: Rounding was 0.5, expected less than 0.4 Hardware failure detected, consult stress.txt file. Torture Test ran 9 minutes - 1 errors, 0 warnings. so maybe it isn't even a psu problem but a cpu one? If it was strictly a problem with the CPU, you'd likely not be able to boot, or this test would fail within a few seconds. 9 minutes is possible but a bit on the early side to be a thermal issue; more likely would be the memory config and BIOS setup is marginal and that relaxing the timings would help. If you shut down for a while, and then do a cold restart with the case open, does that result in the stress test taking longer to fail? If so, check your cooling. On the other hand, if the length of time before failure doesn't change, or more precisely seems random-- 5-10 minutes one try, an hour the next, that generally indicates memory and motherboard BIOS setup. PSU problems tend to not show up with prime95, but when you have the disks busy and maybe graphics, also. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
Aggelidis Nikos wrote: Not really. All modern CPUs have BIST (built-in self tests) that run even before the BIOS starts, and it would be really rare to actually have a "working" system with a faulty CPU. Errors in mprime usually indicate some other problem, such as bad memory, bad BIOS settings, overheating or an incompatibility of CPU/motherboard etc. Going back to what you said previously, you got an Nvidia 5200 graphics card? Were these ever produced for PCI express or are you using a) a normal PCI one or b)You got one of these weird mobos that have both AGP and PCI express? As I understand there are no AGP-only motherboards for core2duo. Yes i have a weird mobo that has both AGP and PCI. The nvidia is an AGP one. The mobo wasn't my choise :( but when the changed the false cpu with a dual core they didn't want to change the graphics card as well. Can this mobo create problems? It is possible, having both an AGP and PCI express on the same board is a hack, and not even all AGP cards are compatible with these mobos. It would be better to test it with a PCI express graphics card, if you can grab one. I'd be happy to lend you one for testing, but I guess we are not in the same town ;) (Chania here...) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
> > Not really. All modern CPUs have BIST (built-in self tests) that run even > before the BIOS starts, and it would be really rare to actually have a > "working" system with a faulty CPU. Errors in mprime usually indicate some > other problem, such as bad memory, bad BIOS settings, overheating or an > incompatibility of CPU/motherboard etc. > Going back to what you said previously, you got an Nvidia 5200 graphics > card? Were these ever produced for PCI express or are you using a) a normal > PCI one or b)You got one of these weird mobos that have both AGP and PCI > express? As I understand there are no AGP-only motherboards for core2duo. Yes i have a weird mobo that has both AGP and PCI. The nvidia is an AGP one. The mobo wasn't my choise :( but when the changed the false cpu with a dual core they didn't want to change the graphics card as well. Can this mobo create problems? > Another thought: Sometimes the CPU cooler is not entirely seated, resulting > in bad thermal contact of the heatsink/CPU assembly. This is not unusual in > the 775 socket since the mechanism requires quite some pressure to lock and > some people are afraid to apply it ;) > I will check it... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
Aggelidis Nikos wrote: running mprime-torture i get: Beginning a continuous self-test to check your computer. Please read stress.txt. Hit ^C to end this test. Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length. Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length. Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length. Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length. FATAL ERROR: Rounding was 0.5, expected less than 0.4 Hardware failure detected, consult stress.txt file. Torture Test ran 9 minutes - 1 errors, 0 warnings. so maybe it isn't even a psu problem but a cpu one? Not really. All modern CPUs have BIST (built-in self tests) that run even before the BIOS starts, and it would be really rare to actually have a "working" system with a faulty CPU. Errors in mprime usually indicate some other problem, such as bad memory, bad BIOS settings, overheating or an incompatibility of CPU/motherboard etc. Going back to what you said previously, you got an Nvidia 5200 graphics card? Were these ever produced for PCI express or are you using a) a normal PCI one or b)You got one of these weird mobos that have both AGP and PCI express? As I understand there are no AGP-only motherboards for core2duo. Another thought: Sometimes the CPU cooler is not entirely seated, resulting in bad thermal contact of the heatsink/CPU assembly. This is not unusual in the 775 socket since the mechanism requires quite some pressure to lock and some people are afraid to apply it ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
running mprime-torture i get: Beginning a continuous self-test to check your computer. Please read stress.txt. Hit ^C to end this test. Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length. Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length. Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length. Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length. FATAL ERROR: Rounding was 0.5, expected less than 0.4 Hardware failure detected, consult stress.txt file. Torture Test ran 9 minutes - 1 errors, 0 warnings. so maybe it isn't even a psu problem but a cpu one? >I'd make a list of what your voltages are (go into the BIOS and see) and >provide them here. i will do that. thanks everyone for your assistance so far! -nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
Aggelidis Nikos wrote: * CPU overheating -> Is there anyway to check for cpu temperatures within freebsd? -> I 've used the pc for like 8 hours in a really hot day but it didn't restart...if this can be considered as an indication. You could try sysutils/mbmon or sysutils/xmbmon - shows cpu temperature, inside case temperature and vcore voltage. Supported chipsets are listed in mbmon/pkg-descr. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
On Sun, Jul 13, 2008 at 11:04:31AM +0300, Aggelidis Nikos wrote: > * CPU overheating > -> Is there anyway to check for cpu temperatures within freebsd? > -> I 've used the pc for like 8 hours in a really hot day but it > didn't restart...if this can be considered as an indication. Not easily. If coretemp(4) is loaded, you should have some sysctls named dev.cpu.X.temperature which contain the temperature of the core in Celcius. Otherwise, you can try utilities like mbmon and healthd, but those were written for old (circa 90s) hardware. Also, are you running powerd(8) on this machine? > *Memory > -> i used memtest ,from an ubuntu live cd, to check the memory and > everything works fine according to it. That's a good start; your memory is probably not the issue then. > *PSU > I have a 400Watt PSU... maybe this is inadequate. I will try to swap > it for something stronger to see how it goes. Wattage is not the only thing that matters with a PSU. Voltages are significantly more important, if you ask me. I'd make a list of what your voltages are (go into the BIOS and see) and provide them here. There may be one which is significantly off, indicating a bad PSU. > In general where are there any stress tests i can do, to test the PSU > and some major subsystems of the computer? Windows offers many free utilities that do this; I'm not sure about FreeBSD. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
Since i can't buy a new PSU today... I kept testing: i tried compile and i got a reboot again: this time i checked /var/log/messages and i have this: ... Jul 13 13:41:20 apollo syslogd: kernel boot file is /boot/kernel/kernel Jul 13 13:41:20 apollo kernel: panic: vm_fault: fault on nofault entry, addr: c3a16000 Jul 13 13:41:20 apollo kernel: cpuid = 0 Jul 13 13:41:20 apollo kernel: Uptime: 4h50m11s Jul 13 13:41:20 apollo kernel: Physical memory: 2035 MB Jul 13 13:41:20 apollo kernel: Dumping 218 MB: 203 187 171 155 139 123 107 91 75 59 43 27 11Copyrigh t (c) 1992-2008 The FreeBSD Project. ... i also installed xmbmon to measure temperatures... i haven't seen anything above 60C so i guess it isn't the BIOS rebooting the computer due to cpu temperature.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
-On [20080713 10:04], Aggelidis Nikos ([EMAIL PROTECTED]) wrote: >> Look through /var/log/messages. >i get this: Jul 13 09:00:00 apollo newsyslog[1018]: logfile turned >over due to size>100K Then look at /var/log/messages.0.bz2 Also, check `last`. -- Jeroen Ruigrok van der Werven / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B There is time in life for everything... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
Aggelidis Nikos wrote: PS: this was a ready-made pc that had it's p4 processor upgraded to a dual core. It also got a new motherboard and 2G of ddr2. It has an old nvidia GeForce fx 5200, and a 400watt nameless PSU. I only have freebsd,which i installed a month ago, on it. ___ The nameless PSU is probably the cause then. It would work ok with the older CPU but can not keep up with 2cores... I would focus on that, since you already tested memory and the rest of the components seem standard. In ports you will find a few programs for stress testing, e.g.: math/mprime (in "torture" mode) sysutils/cpuburn (specifically for CPU stress testing) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
Thanks for your answers Manolis and Mike. In the beginning i didn't suspect hardware because it happened only at compilation procedures. Now i realize that every other task i do isn't really demanding. > Look through /var/log/messages. i get this: Jul 13 09:00:00 apollo newsyslog[1018]: logfile turned over due to size>100K * CPU overheating -> Is there anyway to check for cpu temperatures within freebsd? -> I 've used the pc for like 8 hours in a really hot day but it didn't restart...if this can be considered as an indication. *Memory -> i used memtest ,from an ubuntu live cd, to check the memory and everything works fine according to it. *PSU I have a 400Watt PSU... maybe this is inadequate. I will try to swap it for something stronger to see how it goes. In general where are there any stress tests i can do, to test the PSU and some major subsystems of the computer? thanks in advance, nikos PS: this was a ready-made pc that had it's p4 processor upgraded to a dual core. It also got a new motherboard and 2G of ddr2. It has an old nvidia GeForce fx 5200, and a 400watt nameless PSU. I only have freebsd,which i installed a month ago, on it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
On Sun, 13 Jul 2008 09:09:09 +0300
"Aggelidis Nikos" <[EMAIL PROTECTED]> wrote:
> Hi to all the list, i 've been using FreeBSD for almost a month ,and i
> have this weird problem. Sometimes when i try to compile a program the
> computer will hard-reset itself, like someone pulled of the plug...
> For example yesterday i was trying to install jdk1.6 + eclipse, and
> while i was compiling eclipse {more precisely -if i remember
> correctly- the "diablo-jdk" needed for eclipse} the computer rebooted
> itself.
>
> The load of the computer was: 2-3xterms, 1 Konversation irc client
> ,several opera9.51 windows, 1-2 konqueror windows, and 1-2 Firefox
> widows. I have a dual core box with 2GB of memory and i use freebsd7
> 32bit. The computer was online for 8hours with almost the same load
> {minus the compilation-procedure}.
>
> * Has anyone had problems like this?
Yes. It's always turned out to be flaky hardware for me.
> * What can i do to investigate a bit more what was the situation
> before the restart?
Look through /var/log/messages.
> * Is there anyway to solve this problem.
Well, you really can't "solve" it, so much as troubleshoot it. Make up
a list of possible causes, and then start checking each possible
cause. You haven't given any real information about the system or the
problem, so we can't eliminate anything. My top suspects would be the
PSU (old or inadequate) and CPU (overheating or overclocked). Memory
and the I/O subsystem would be next, but they tend to cause
random process failure rather than system shutdowns when they go
flaky, so I'd try them last.
http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: weird restarts when compiling
Aggelidis Nikos wrote:
Hi to all the list, i 've been using FreeBSD for almost a month ,and i
have this weird problem. Sometimes when i try to compile a program the
computer will hard-reset itself, like someone pulled of the plug...
For example yesterday i was trying to install jdk1.6 + eclipse, and
while i was compiling eclipse {more precisely -if i remember
correctly- the "diablo-jdk" needed for eclipse} the computer rebooted
itself.
The load of the computer was: 2-3xterms, 1 Konversation irc client
,several opera9.51 windows, 1-2 konqueror windows, and 1-2 Firefox
widows. I have a dual core box with 2GB of memory and i use freebsd7
32bit. The computer was online for 8hours with almost the same load
{minus the compilation-procedure}.
* Has anyone had problems like this?
* What can i do to investigate a bit more what was the situation
before the restart?
* Is there anyway to solve this problem.
thanks for your help,
nikos
PS: i could blame the power company but the above problem has happened
before{several times} when i tried to compile "big" programs like
firefox or do a pkgdb -Fu, so i don't think it is this.
Hi Nikos,
This sounds like a hardware problem to me. It is not easy to find out
the exact cause, except perhaps by swapping components:
- Could be bad RAM, but I doubt it is you would probably get at least a
kernel panic and not a hard reboot
- Could be that your power supply can not handle the increased current
required by the CPU / disk when compiling, voltages fall out of spec,
and the motherboard resets itself. I've seen this happening quite a few
times - systems exhibit a variety of weird symptoms like this, commonly
failing when running CPU intensive apps.
- Your CPU / system may get overheated and hits a thermal cutoff.
- You could have some other faulty component, or some of your BIOS
settings are too 'high'
Things to try:
- Take the cover off and see whether there is heat build up when
compiling and also whether the fans work adequately.
- Swap out the power supply
- Change some BIOS settings, or maybe underclock the CPU a bit so it
requires less power and see if it works then.
Most of the people here are used to run long compilation / portupgrade
cycles (sometimes in excess of 24 hours) and when a system fails
unexpectedly like this it is normal to suspect hardware problems.
Manolis
P.S. I removed the -hackers list from the reply - this question is
better suited for -questions only.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
