From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Dazed and Confused
Date: 9 Dec 2002 11:19:48 -0800 [thread overview]
Message-ID: <at2qck$ffi$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.42.0212061202230.7770-100000@egg
Followup to: <Pine.LNX.4.42.0212061202230.7770-100000@egg>
By author: Greg Boyce <gboyce@rakis.net>
In newsgroup: linux.dev.kernel
>
> Actually, this does leave one question still: How serious is the problem?
> How much would you trust a machine reporting these errors? Most of the
> machines are just performing DNS and web service (although with a pretty
> high load). The processes on the machine are are cpu and memory
> intensive, but there is no critical data stored on most of the machines.
>
> Are the machines likely to give us problems with crashing and data
> corruption, or would it be safe to ignore the problem unless we started
> noticing odd behavior?
>
The fact that you're seeing the error means data corruption has
already occurred.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-12-09 19:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 14:55 Dazed and Confused Greg Boyce
2002-12-06 15:24 ` Richard B. Johnson
2002-12-06 16:05 ` Alan Cox
2002-12-06 16:47 ` Greg Boyce
2002-12-06 17:08 ` Greg Boyce
2002-12-06 22:25 ` Alan Cox
2002-12-06 23:33 ` Krzysztof Halasa
2002-12-08 1:36 ` Alan Cox
2002-12-09 19:19 ` H. Peter Anvin [this message]
2002-12-10 0:42 ` Bill Davidsen
2002-12-09 19:19 ` H. Peter Anvin
2002-12-08 11:59 ` Gilad Ben-Yossef
2002-12-08 15:22 ` Gregory Boyce
2002-12-08 22:55 ` Toon van der Pas
-- strict thread matches above, loose matches on Subject: below --
2002-07-08 11:44 Dazed and confused jbradford
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='at2qck$ffi$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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.