Path: ...!weretis.net!feeder6.news.weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Buzz McCool <buzz_mccool@yahoo.com>
Newsgroups: sci.electronics.design
Subject: Re: Predictive failures
Date: Thu, 18 Apr 2024 10:18:08 -0700
Organization: A noiseless patient Spider
Lines: 11
Message-ID: <uvrkki$2c9fl$1@dont-email.me>
References: <uvjn74$d54b$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 18 Apr 2024 19:18:10 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="21917b2bbfdf7e3c9a43c288bffe8669";
	logging-data="2500085"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18oxGLRx/1MJNDC/qkW15x3oiJHtsrdFzQ="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:BBS35qtI0r9zfkC9Ge+zeCdBoqU=
In-Reply-To: <uvjn74$d54b$1@dont-email.me>
Content-Language: en-US
Bytes: 1545

On 4/15/2024 10:13 AM, Don Y wrote:
> Is there a general rule of thumb for signalling the likelihood of
> an "imminent" (for some value of "imminent") hardware failure?

This reminded me of some past efforts in this area. It was never 
demonstrated to me (given ample opportunity) that this technology 
actually worked on intermittently failing hardware I had, so be cautious 
in applying it in any future endeavors.

https://radlab.cs.berkeley.edu/classes/cs444a/KGross_CSTH_Stanford.pdf