From owner-freebsd-questions@freebsd.org  Wed Nov 18 16:31:26 2015
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECE38A323C9
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Wed, 18 Nov 2015 16:31:26 +0000 (UTC)
 (envelope-from merlyn@geeks.org)
Received: from mail.geeks.org (jacobs.geeks.org [204.153.247.1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CDAC61D3F
 for <freebsd-questions@freebsd.org>; Wed, 18 Nov 2015 16:31:26 +0000 (UTC)
 (envelope-from merlyn@geeks.org)
Received: from mail.geeks.org (localhost [127.0.0.1])
 by after-clamsmtpd.geeks.org (Postfix) with ESMTP id DA5A3110235
 for <freebsd-questions@freebsd.org>; Wed, 18 Nov 2015 10:31:24 -0600 (CST)
Received: by mail.geeks.org (Postfix, from userid 1003)
 id BA5E3110234; Wed, 18 Nov 2015 10:31:24 -0600 (CST)
Date: Wed, 18 Nov 2015 10:31:24 -0600
From: Doug McIntyre <merlyn@geeks.org>
To: freebsd-questions@freebsd.org
Subject: Re: Is processor microcode advised?
Message-ID: <20151118163124.GC19167@geeks.org>
References: <564B3E4D.7070808@gmail.com>
 <CA+tpaK3EMAU5iN4NC6jXQtugJbxyN+m2OtN5-4cyXqnpy4fLcQ@mail.gmail.com>
 <564C3674.8040803@netfence.it> <2412157.pVeQKYeata@amd.asgard.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2412157.pVeQKYeata@amd.asgard.uk>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Virus-Scanned: ClamAV using ClamSMTP
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2015 16:31:27 -0000

On Wed, Nov 18, 2015 at 03:13:53PM +0000, Dave wrote:
> On Wednesday 18 November 2015 09:27:32 Andrea Venturoli wrote:
> > Supposing BIOS has not been updated (due to no availability, lazyness, 
> > impossibility over a remote link, fear of bricking the box, etc...)
> 
> FWIW, I've replaced many, many motherboards over the years and as part of our standard procedure we update the BIOS firmware to the latest company approved version with the corporate boot logo baked in and I've never, ever ended up with a bricked board.  ...

I have. Mostly with Dell systems. Later on, there are known errata
that pop up, like if you have this board, with this RAID controller,
and this version of the BCM, make sure to upgrade this component to
this version first, that component next, etc. etc.

And of course, usually this errata always shows up *after* I've done
the deed and killed the board. Dell also doesn't have a field recovery
option either.

I don't use Dell much any more.