From: Jesper Juhl <jesper.juhl@gmail.com>
To: Mark v Wolher <trilight@ns666.com>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Lee Revell <rlrevell@joe-job.com>,
Folkert van Heusden <folkert@vanheusden.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: system keeps freezing once every 24 hours / random apps crashing
Date: Sat, 31 Dec 2005 12:49:22 +0100 [thread overview]
Message-ID: <9a8748490512310349g10d004c7i856cf3e70be5974@mail.gmail.com> (raw)
In-Reply-To: <43B66E3D.2010900@ns666.com>
On 12/31/05, Mark v Wolher <trilight@ns666.com> wrote:
> Jesper Juhl wrote:
> > On 12/31/05, Mark v Wolher <trilight@ns666.com> wrote:
> >
> >>g'morning !
> >>
> >>the memtest86 went 40 times over the memory, no errors detected.
> >>
> >
> > Give memtest86+ a spin (http://www.memtest.org/) as well. memtest86 is
> > good, but I've found in the past that memtest86+ sometimes finds
> > errors that memtest86 does not, so giving both a sin fo an extended
> > period of time is usually a good idea.
> > Also, make sure you enable all the tests of both tools.
>
> Hi Jesper,
>
> Oh i thought they were the same, i used memtest86+ which comes with
> debian and not the "older" memtest86.
>
> Right now i booted the kernel with nomce since one never knows with dell
Surpressing MCE's (Machine Check Exceptions) is a really bad idea
usually. MCE's indicate a hardware problem, so unless it's known that
a certain MCE is reported wrongly they should *not* be ignored.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-12-31 11:49 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 14:05 system keeps freezing once every 24 hours / random apps crashing Trilight
2005-12-30 14:11 ` Ochal Christophe
2005-12-30 14:27 ` Jesper Juhl
2005-12-30 15:52 ` Mark v Wolher
2005-12-30 16:37 ` Mark v Wolher
2005-12-30 16:47 ` Folkert van Heusden
2005-12-30 17:14 ` Mark v Wolher
2005-12-30 18:30 ` Folkert van Heusden
2005-12-30 19:22 ` Mark v Wolher
2005-12-30 20:24 ` Folkert van Heusden
2005-12-30 20:58 ` Mark v Wolher
2005-12-30 21:15 ` Mark v Wolher
2005-12-30 21:30 ` Mark v Wolher
2005-12-30 21:35 ` Lee Revell
2005-12-30 21:47 ` Mark v Wolher
2005-12-30 21:51 ` Lee Revell
2005-12-30 21:57 ` Mark v Wolher
2005-12-30 22:00 ` Lee Revell
2005-12-30 22:05 ` Mark v Wolher
2005-12-30 22:11 ` Lee Revell
2005-12-30 22:16 ` Mark v Wolher
2005-12-30 23:11 ` Alistair John Strachan
2005-12-30 23:42 ` Mark v Wolher
2005-12-30 23:56 ` Alistair John Strachan
2005-12-31 0:20 ` Mark v Wolher
2005-12-31 0:27 ` Alistair John Strachan
2005-12-31 0:42 ` Mark v Wolher
2005-12-31 0:51 ` Alistair John Strachan
2005-12-31 0:54 ` Mark v Wolher
2005-12-31 10:31 ` Mark v Wolher
2005-12-31 11:08 ` Jesper Juhl
2005-12-31 11:40 ` Mark v Wolher
2005-12-31 11:49 ` Jesper Juhl [this message]
2005-12-31 12:46 ` Mark v Wolher
2005-12-31 15:18 ` Mark v Wolher
2005-12-31 15:22 ` Arjan van de Ven
2005-12-31 15:34 ` Mark v Wolher
2005-12-31 15:51 ` Mark v Wolher
2005-12-31 16:34 ` Sami Farin
2005-12-31 16:48 ` Mark v Wolher
2005-12-31 17:02 ` Sami Farin
2005-12-31 17:26 ` Mark v Wolher
2005-12-31 22:01 ` Sami Farin
2006-01-01 2:26 ` Mark v Wolher
2006-01-01 13:06 ` Mark v Wolher
2006-01-01 14:47 ` Mark v Wolher
2006-01-01 17:47 ` Mark v Wolher
2006-01-01 18:38 ` Jiri Slaby
2006-01-01 18:49 ` Mark v Wolher
2006-01-01 19:01 ` Mauro Carvalho Chehab
2006-01-01 19:12 ` Jiri Slaby
2006-01-01 19:37 ` Mark v Wolher
2006-01-01 23:20 ` Re; system keeps freezing once every 24 hours / random apps crashing Peter Missel
2006-01-02 22:29 ` Alan Cox
2006-01-03 0:19 ` Mauro Carvalho Chehab
2006-01-01 18:49 ` Folkert van Heusden
2006-01-01 18:54 ` Mark v Wolher
2006-01-01 20:49 ` Folkert van Heusden
2006-01-01 21:38 ` Mark v Wolher
2006-01-01 21:41 ` Lee Revell
2006-01-01 22:01 ` Mark v Wolher
2006-01-25 12:46 ` Jiri Slaby
2006-01-01 15:14 ` Sami Farin
2005-12-31 11:23 ` Jesper Juhl
2005-12-31 11:31 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a8748490512310349g10d004c7i856cf3e70be5974@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=s0348365@sms.ed.ac.uk \
--cc=trilight@ns666.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).