ropers wrote:
> 2009/6/26 Jussi Peltola :
>> memtest86+: it can prove it's broken, but if it doesn't
>> find problems it doesn't guarantee there are none.
This is correct.
> I've said this before, but I've yet to see faulty RAM whose problems
> memtest86+ will not detect during a 24hr burn-in tes
On Sun, Aug 2, 2009 at 10:45 AM, ropers wrote:
> Of course, depending on your circumstances it may be more economical
> to just chuck the suspect RAM instead of wasting 24 hours. And
> granted, YMMV. But if anyone has ever seen any faulty RAM whose
> problems a 24hr burn-in test with memtest86+ co
2009/6/26 Jussi Peltola :
> memtest86+: it can prove it's broken, but if it doesn't
> find problems it doesn't guarantee there are none.
I've said this before, but I've yet to see faulty RAM whose problems
memtest86+ will not detect during a 24hr burn-in test. Sure, I've seen
faulty RAM that memte
On 2009-08-01, Comete wrote:
> as suggested, i finally changed the RAID controler (Compaq Smart Array
> 431) with the same device and the firewall still crashes with the same
> error.
I think the idea was probably to change it for a completely different
type of device (or for just a plain SCSI
wer supply across 2 servers I would be shocked
:)
-Original Message-
From: Comete [mailto:com...@daknet.org]
Sent: 26 June 2009 13:48
To: Michal
Subject: Re: random crashes on a firewall with OpenBSD 4.5-stable
No problem with the PSU and voltage limits. The PSU isn't used at its
full c
Can't read that? Custom compiled kernel and cac error speaks by
themselves; dirty solution, try other disk controller. Best solution,
discard you don't have bad hardware and, if everything is ok, make
contact with developers and help searching for a code patch to improve
the RAID adapter driver
On 2009-06-26, Michal wrote:
> Well, you can check the Volt readings in the bios, most will give you a
> reading, but I am sure there is some BSD software out there
"sysctl hw.sensors" works for some systems. also see sensorsd(8).
27;s worth knowing how to check this as a simple check on
servers
-Original Message-
From: Comhte [mailto:com...@daknet.org]
Sent: 26 June 2009 16:42
To: Michal
Subject: Re: random crashes on a firewall with OpenBSD 4.5-stable
Oh sorry :p
How could i test the power supply unit ?
Mich
But even measuring the ripple with a scope won't guarantee it's OK.
Swapping out all of the hardware is sometimes the only way to find out.
Same goes for memtest86+: it can prove it's broken, but if it doesn't
find problems it doesn't guarantee there are none.
--
Jussi Peltola
on servers
-Original Message-
From: Comhte [mailto:com...@daknet.org]
Sent: 26 June 2009 16:42
To: Michal
Subject: Re: random crashes on a firewall with OpenBSD 4.5-stable
Oh sorry :p
How could i test the power supply unit ?
Michal a icrit :
> Other servers?? I don't mean PDU, I me
On Thu, Jun 25, 2009 at 05:23:40PM +0200, Com??te wrote:
> Hi,
>
> we are using the last OpenBSD 4.5-stable release on an old Compaq
> Proliant ML350 as a firewall with spamd. But we encounter randomly some
> system crashes (once a week or two weeks). The system always displays
> the same mes
find unexplained crash's can be traced back to PSU's
quite often
-Original Message-
From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
Comhte
Sent: 26 June 2009 12:22
To: Misc OpenBSD
Cc: Daniel Gracia Garallar
Subject: Re: random crashes on a firewall with Ope
Well i have tested the RAM with memtest, no error.
maybe another idea ?
Thanks
Daniel Gracia Garallar a C)crit :
Oh and maybe bad RAM; I've hit some nasty errors with these faulty
DIMMs... :/
ComC(te escribiC3:
Hi,
we are using the last OpenBSD 4.5-stable release on an old Compaq
Proliant
Oh and maybe bad RAM; I've hit some nasty errors with these faulty
DIMMs... :/
ComC(te escribiC3:
Hi,
we are using the last OpenBSD 4.5-stable release on an old Compaq
Proliant ML350 as a firewall with spamd. But we encounter randomly some
system crashes (once a week or two weeks). The syste
Hi,
we are using the last OpenBSD 4.5-stable release on an old Compaq
Proliant ML350 as a firewall with spamd. But we encounter randomly some
system crashes (once a week or two weeks). The system always displays
the same message:
uvm_fault (0xd080d9e00x0,0,1) -> e
kernel: page fault trap, c
15 matches
Mail list logo
