In this case I would check about the processor cooler. It could not be
working fine and need some lubrification or a clean, or in worst case a
new one.
Regards,
Elton
Jonathon McKitrick wrote:
On Thu, Nov 25, 2004 at 11:45:06PM -0500, Matt Emmerton wrote:
: Given the cost of memory these days,
If the goal is simply to stress-test the memory, just take a huge file
and write a shell script loop to gzip it and ungzip it ad infinitum.
I used this technique a while ago to ferret out some memory problems.
In this case, the bad memory manifested itself as gzip eventually
reporting an error
Chris Dillon wrote:
After fiddling around with some of the clock/voltage
related BIOS settings, putting new thermal compound
between the CPUs and heatsinks, reseating cards and
memory, placing the PCs inside a hexagram drawn on
the floor and dancing nak... nevermind... we got them
to run snip
I
On Thu, 25 Nov 2004, Chuck Robey wrote:
I don't want to embarrass anyone here, but something needs to be
said. Note this next sentence carefully: THERE IS NO SUCH THING AS A
WORKING MEMORY TEST PROGRAM!!!
Anyone who tells you otherwise is no friend of yours, because they
are making your life
Adam Fabian wrote:
Does parity RAM reliably report on it's reliability?
Nope. At least if you're talking about parity memory on FPM or EDO DRAM,
which only has a fifty-fifty chance of even noticing an error, and a 1/9
(~11%) chance of reporting an error with the parity bit itself.
Modern SDRAM
Chuck Robey [EMAIL PROTECTED] writes:
With that in mind, sometimes, the very best memory test programs can give
you better ideas that memory you thought was failing IS failing. The
opposite, proving that memory is good, is just totally, totally useless,
you cannot take any data home at all
On Fri, 26 Nov 2004 03:46:20 +
Jonathon McKitrick [EMAIL PROTECTED] wrote:
On Thu, Nov 25, 2004 at 04:05:53PM -0500, Lowell Gilbert wrote:
: Jonathon McKitrick [EMAIL PROTECTED] writes:
:
: This is what I get from make buildworld. I've gotten signal 10,
11, and now: 5.
:
: Is
Not seen this exact error before, but I recently had a mobo go bad
that would produce errors with compiles and ect before it would
hardlock. It would go flaky under heavy I/O.
I tested for it by swapping out the proc and ram.
On Thu, 25 Nov 2004 20:16:23 +
Jonathon McKitrick [EMAIL
On Thu, Nov 25, 2004 at 11:45:06PM -0500, Matt Emmerton wrote:
: Given the cost of memory these days, swapping it out is generally cheaper
: than the cost of random downtime and recovering from crashes in a production
: environment.
I am *really* not a hardware guy. I just had a box built and
This is what I get from make buildworld. I've gotten signal 10, 11, and now
5.
Is this bad memory?
S -DYP -c /usr/src/lib/libc/../libc/net/res_debug.c -o res_debug.o
cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include
-D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE
Jonathon McKitrick [EMAIL PROTECTED] writes:
This is what I get from make buildworld. I've gotten signal 10, 11, and now
5.
Is this bad memory?
That's a reasonable guess, but the only way to tell for sure is to
test it.
___
[EMAIL PROTECTED]
On Thu, Nov 25, 2004 at 08:16:23PM +, Jonathon McKitrick wrote:
Is this bad memory?
If you're not getting the same error every time, it's almost certainly
bad hardware, and memory is the most likely candidate.
--
Adam Fabian ([EMAIL PROTECTED])
On Thu, Nov 25, 2004 at 04:05:53PM -0500, Lowell Gilbert wrote:
: Jonathon McKitrick [EMAIL PROTECTED] writes:
:
: This is what I get from make buildworld. I've gotten signal 10, 11, and now
: 5.
:
: Is this bad memory?
:
: That's a reasonable guess, but the only way to tell for sure is to
Someone broke the silence:
On Thu, Nov 25, 2004 at 04:05:53PM -0500, Lowell Gilbert wrote:
Jonathon McKitrick [EMAIL PROTECTED] writes:
This is what I get from make buildworld. I've gotten signal 10,
11, and now 5.
Is this bad memory?
That's a reasonable guess, but the only way to
On Thu, 25 Nov 2004, Haulmark, Chris wrote:
Someone broke the silence:
On Thu, Nov 25, 2004 at 04:05:53PM -0500, Lowell Gilbert wrote:
Jonathon McKitrick [EMAIL PROTECTED] writes:
This is what I get from make buildworld. I've gotten signal 10,
11, and now 5.
Is this bad memory?
Chuck Robey wrote:
On Thu, 25 Nov 2004, Haulmark, Chris wrote:
Someone broke the silence:
On Thu, Nov 25, 2004 at 04:05:53PM -0500, Lowell Gilbert wrote:
Jonathon McKitrick [EMAIL PROTECTED] writes:
This is what I get from make buildworld. I've gotten signal 10,
11, and now 5.
Is this bad
On Thu, 25 Nov 2004, Haulmark, Chris wrote:
Someone broke the silence:
On Thu, Nov 25, 2004 at 04:05:53PM -0500, Lowell Gilbert wrote:
Jonathon McKitrick [EMAIL PROTECTED] writes:
This is what I get from make buildworld. I've gotten signal 10,
11, and now 5.
Is this bad
Chuck Robey wrote:
On Thu, 25 Nov 2004, Haulmark, Chris wrote:
Someone broke the silence:
On Thu, Nov 25, 2004 at 04:05:53PM -0500, Lowell Gilbert wrote:
Jonathon McKitrick [EMAIL PROTECTED] writes:
This is what I get from make buildworld. I've gotten signal 10,
11, and now
On Fri, 26 Nov 2004, Rob wrote:
Chuck Robey wrote:
On Thu, 25 Nov 2004, Haulmark, Chris wrote:
Someone broke the silence:
On Thu, Nov 25, 2004 at 04:05:53PM -0500, Lowell Gilbert wrote:
Jonathon McKitrick [EMAIL PROTECTED] writes:
This is what I get from make buildworld.
On Fri, 26 Nov 2004, Matt Emmerton wrote:
Chuck Robey wrote:
On Thu, 25 Nov 2004, Haulmark, Chris wrote:
Someone broke the silence:
On Thu, Nov 25, 2004 at 04:05:53PM -0500, Lowell Gilbert wrote:
Jonathon McKitrick [EMAIL PROTECTED] writes:
This is what I get
Does parity RAM reliably report on it's reliability?
--
Adam Fabian ([EMAIL PROTECTED])
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
21 matches
Mail list logo
