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
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
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,
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
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
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.
-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 size100K
Then look at /var/log/messages.0.bz2
Also, check `last`.
--
Jeroen Ruigrok van der Werven
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
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
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
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
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
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
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,
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
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
16 matches
Mail list logo
