In message [EMAIL PROTECTED] Matthew Dillon writes:
: Forget the drilling! Blood conducts electricity... simply *installing*
: a motherboard in those fraggin sharp-edged sheet metal chassis is enough!
I've had one or two cheapo mo-bos that haven't worked at 100MHz after
spattering human
On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote:
Intel's ECC implementation is not perfect (1), but it's good enough to
catch these sorts of problems.
Just as an interesting side note, we had a motherboard which
supported ECC ram and had ECC ram in it and which was
On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote:
Intel's ECC implementation is not perfect (1), but it's good enough to
catch these sorts of problems.
Just as an interesting side note, we had a motherboard which
supported ECC ram and had ECC ram in it and which
On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote:
Intel's ECC implementation is not perfect (1), but it's good enough to
catch these sorts of problems.
Just as an interesting side note, we had a motherboard which
supported ECC ram and had ECC ram in it and which was
:ECC doesn't protect against certain types of motherboard address line
: errors (since although the ECC is correct, the selected address is wrong, so
: thus the data is wrong). There's parity protection on parts of the CPU
: address bus, but I don't believe there is any protection between the
:Hi again,
:
: Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault
:error (strange, it didn't look like a normal panic screen, just the
:message and the content of three registers, then the syncing disks
:message). It seems that I might be wrong about hardware not being the
Hi again,
On Wed, 6 Oct 1999, Adrian Penisoara wrote:
hi again,
On Tue, 5 Oct 1999, Matthew Dillon wrote:
: The problem is that the machine is completely locked, I can't get into
:the debugger with CTR-ALT-ESC; no panics so there are no coredumps
:catched. Any advise ? Could you
:Hi again,
:
: Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault
:error (strange, it didn't look like a normal panic screen, just the
:message and the content of three registers, then the syncing disks
:message). It seems that I might be wrong about hardware not being
hi again,
On Tue, 5 Oct 1999, Matthew Dillon wrote:
: The problem is that the machine is completely locked, I can't get into
:the debugger with CTR-ALT-ESC; no panics so there are no coredumps
:catched. Any advise ? Could you escape in the debugger when you were hit
:by these bugs ?
Hi,
On Mon, 4 Oct 1999, Adrian Penisoara wrote:
I have a -stable production server that keeps (solidly) blocking pretty
often (I don't get over 3 days uptimes). If you need details just let me
know.
Just to let you know: syncing every second in a loop like this:
while true
do
: The problem is that the machine is completely locked, I can't get into
:the debugger with CTR-ALT-ESC; no panics so there are no coredumps
:catched. Any advise ? Could you escape in the debugger when you were hit
:by these bugs ?
If it's completely locked up and ctl-alt-esc doesn't work
Hi,
On Mon, 4 Oct 1999, Matthew Dillon wrote:
: Excuse my intrusion, but could you be so kind to tell me whether you had
:the time to build patches for these MMAP-related freezes ? If not could
:you recommend me some workarounds ?
:
: I have a -stable production server that keeps (solidly)
On Mon, 4 Oct 1999, Adrian Penisoara wrote:
Excuse my intrusion, but could you be so kind to tell me whether you had
the time to build patches for these MMAP-related freezes ? If not could
you recommend me some workarounds ?
doubling the ram from 384 - 768 meg appears to have fixed it for
13 matches
Mail list logo
