From: Chris Frey <cdfrey@netdirect.ca>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: Maciej Zenczykowski <maze@cela.pl>,
Arnaud Fontaine <arnaud@andesi.org>,
Mike Fedyk <mfedyk@matchmail.com>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: Oops with 2.4.23
Date: Mon, 22 Dec 2003 12:05:57 -0500 [thread overview]
Message-ID: <20031222120557.A21530@netdirect.ca> (raw)
In-Reply-To: <20031222021659.GA4857@ip68-4-255-84.oc.oc.cox.net>; from barryn@pobox.com on Sun, Dec 21, 2003 at 06:17:00PM -0800
On Sun, Dec 21, 2003 at 06:17:00PM -0800, Barry K. Nathan wrote:
> On Sat, Dec 20, 2003 at 12:35:24AM +0100, Maciej Zenczykowski wrote:
> > you did run memtest for a minimum dozen hours? sometimes it takes that
> > long to find errors...
>
> On one machine (with a bad power supply, as it turned out) it took
> memtest86 almost 18 hours to report an error. So 12 hours isn't enough
> either.
>
> (On a related note, one machine that I tested with mprime's Torture Test
> <http://www.mersenne.org/> took I think close to 43 hours to show a
> failure. In that case I don't know if the failure was the CPU or the
> motherboard, because in the end both failed on that system.)
At what point do people start suspecting the kernel?
I mean, I would hope the linux kernel is not so badly written as to stress
the machine 24/7. So after 12 hours of running memtest86 with clean
results, does that not begin to point to a software error rather than
hardware?
- Chris
next prev parent reply other threads:[~2003-12-22 17:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 8:56 Oops with 2.4.23 Arnaud Fontaine
2003-12-18 11:47 ` Marcelo Tosatti
2003-12-18 13:06 ` Arnaud Fontaine
2003-12-18 19:08 ` Mike Fedyk
2003-12-19 12:26 ` Arnaud Fontaine
2003-12-19 22:44 ` Arnaud Fontaine
2003-12-19 23:35 ` Maciej Zenczykowski
2003-12-19 23:55 ` Mike Fedyk
2003-12-22 10:07 ` Marc Bevand
2003-12-22 16:37 ` Disconnect
2003-12-21 7:54 ` Arnaud Fontaine
[not found] ` <Pine.LNX.4.58L.0312211238420.6632@logos.cnet>
2003-12-21 15:49 ` Arnaud Fontaine
2003-12-22 2:17 ` Barry K. Nathan
2003-12-22 17:05 ` Chris Frey [this message]
2003-12-22 18:36 ` Disconnect
2003-12-22 18:50 ` Mike Fedyk
2003-12-22 21:37 ` Barry K. Nathan
2003-12-23 14:13 ` Jesper Juhl
-- strict thread matches above, loose matches on Subject: below --
2003-12-19 16:09 Xose Vazquez Perez
2003-12-22 18:06 Xose Vazquez Perez
2003-12-22 18:44 ` Mike Fedyk
2003-12-22 18:53 ` Xose Vazquez Perez
2003-12-23 15:07 ` Arnaud Fontaine
2003-12-23 20:21 ` Xose Vazquez Perez
2003-12-28 14:00 ` Arnaud Fontaine
2003-12-28 21:49 ` James Bourne
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=20031222120557.A21530@netdirect.ca \
--to=cdfrey@netdirect.ca \
--cc=arnaud@andesi.org \
--cc=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=maze@cela.pl \
--cc=mfedyk@matchmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.