From owner-freebsd-questions@freebsd.org Wed Nov 18 20:27:16 2015 Return-Path: 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 1A8F2A32523 for ; Wed, 18 Nov 2015 20:27:16 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id E206B149C for ; Wed, 18 Nov 2015 20:27:15 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 6022DCB8CA0; Wed, 18 Nov 2015 14:05:08 -0600 (CST) Received: from 128.135.208.186 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Wed, 18 Nov 2015 14:05:08 -0600 (CST) Message-ID: <60773.128.135.208.186.1447877108.squirrel@cosmo.uchicago.edu> In-Reply-To: <20151118163124.GC19167@geeks.org> References: <564B3E4D.7070808@gmail.com> <564C3674.8040803@netfence.it> <2412157.pVeQKYeata@amd.asgard.uk> <20151118163124.GC19167@geeks.org> Date: Wed, 18 Nov 2015 14:05:08 -0600 (CST) Subject: Re: Is processor microcode advised? From: "Valeri Galtsev" To: "Doug McIntyre" Cc: freebsd-questions@freebsd.org Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 20:27:16 -0000 On Wed, November 18, 2015 10:31 am, Doug McIntyre wrote: > 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. I'm with you on both items. If you need rack mount server, Dell will cost you about twice compared to what one of many small companies will assemble for you based on some barebone. And with Dell you will not be flexible. Say, you want 3ware RAID controller. Most likely it will not be possible to add into Dell rack mount server (I've been through that). I didn't flash new BIOS into Dell servers (to the best of my recollection). I've flashed into Tyan system boards, and once I've flashed one into HP laptop (they "blacklisted" hardware, which prevented me from replacing piece of crap broadcom wireless adapter with great Intel one - to have Linux... - so I had to use hex editor to add my ID, and then match checksum...). Didn't brick any of boards luckily. But with all my heart I would oppose flashing bios or firmware (unless it is absolutely necessary). In general, if I hear from some hardware vendor that I _must_ flash updated firmware or I am in trouble, I will never use their hardware in a future. BIOS or firmware are programs, and being such they can contain bugs. They are, however, extremely short and simple programs (at least the must be IMHO), and significant effort should be put in their debugging. So, once released, they should be virtually bug free. If I _must_ upgrade BIOS (except for extra features), then the original BIOS as released was a piece of crap, therefore I avoid this hardware in a future. Just my humble opinion. Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++