All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Phil Turmel <philip@turmel.org>,
	Eyal Lebedinsky <eyal@eyal.emu.id.au>,
	list linux-raid <linux-raid@vger.kernel.org>
Subject: Re: possible HighPoint RocketRAID 2720SGL failure
Date: Sat, 23 Sep 2017 17:53:30 +0100	[thread overview]
Message-ID: <59C6918A.6040609@youngman.org.uk> (raw)
In-Reply-To: <fb8f1bc9-ef8a-96c7-b152-b12f07ba3243@turmel.org>

On 23/09/17 15:49, Phil Turmel wrote:
> If thermal stress doesn't kill them, then dopant diffusion within the
> semiconductors eventually will.  This occurs even when turned off, but
> proceeds much faster at elevated temperatures.  Dopant concentrations
> are engineered to not suffer from diffusion effects well beyond the
> expected life of the components (at rated operating temps), but that
> doesn't mean there aren't marginal production runs.  Which can be hard
> to discover before parts start failing years later.  If that happens
> after the warranty period, the manufacturer has dodged a big bullet.
> With a bit of tarnish on their name, of course.

And as manufacturers shrink their die sizes, dopant diffusion and
quantum leakage become much bigger problems :-( If your transistor is
only four or five atoms deep, it won't have many dopant atoms, and they
only have to diffuse a short distance before your transistor is toast.

Cheers,
Wol

      reply	other threads:[~2017-09-23 16:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 11:12 possible HighPoint RocketRAID 2720SGL failure Eyal Lebedinsky
2017-09-21 12:20 ` Roman Mamedov
2017-09-22  1:08   ` Roger Heflin
2017-09-22  8:27     ` Eyal Lebedinsky
2017-09-22 13:20       ` Phil Turmel
2017-09-22 22:52         ` Eyal Lebedinsky
2017-09-23  9:29           ` Eyal Lebedinsky
2017-09-23 14:49             ` Phil Turmel
2017-09-23 16:53               ` Wols Lists [this message]

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=59C6918A.6040609@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=eyal@eyal.emu.id.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.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.