From owner-freebsd-questions@freebsd.org Sun Feb 4 15:36:37 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92A2FEDC8CD for ; Sun, 4 Feb 2018 15:36:37 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) Received: from sonic304-11.consmr.mail.bf2.yahoo.com (sonic304-11.consmr.mail.bf2.yahoo.com [74.6.128.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2467C84B61 for ; Sun, 4 Feb 2018 15:36:36 +0000 (UTC) (envelope-from pathiaki2@yahoo.com) X-YMail-OSG: eHiTZVAVM1lPSaLGeJGU0OdHeCL9hPJ6gohuaxKfEDviurVqH8W8zFY8IzStcJI zXr3btFRr2Au48xnIXe.eklbCk2kqwU29PM8gJ4j3LhV0gRyqAgHeXuqBsUwXsESE5BIyF.ofdTh 1.QRSrnj8PyH_SSOCLnpY0FrounkatCHggseFIuXFWeIDNY4.ieAZwe3ypjZGBi9fW0kbfdGpMsf LRKX7gKe_Z0W73SHQQ3qTzw.FJbMbaz7eLRx7QqzFeuxYeqQkLT.PRkNBcti6zo2XkkUNISxDkxP JrGa1bkdD7Wb178TddQpuYGM1z2tmX8rqCLoCG4VApZe2KpiT4u4q0dKrPaOCjYjhqz4ZqRydzh6 l6v.GdLww.u4bIiBvaPAAbTW2CLXxihqOFSX1_nlN.wSMMUB90o_waJTYgzjU9fLhC3zR.K.W70k 0fST1zU0SKE9v4KpVpLnzrFhsQQyO15CDDPJlQ_e5Bh9vsIlqB6JboI5WKPTe.ThRGPIzfTw_INK n5FwAKYjPsSPLZRQrNN6u Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.bf2.yahoo.com with HTTP; Sun, 4 Feb 2018 15:36:30 +0000 Received: from smtp105.rhel.mail.bf1.yahoo.com (EHLO [192.168.0.6]) ([98.139.231.38]) by smtp415.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 560317f9df28eb4c6d8029191acbe365 for ; Sun, 04 Feb 2018 15:36:27 +0000 (UTC) Subject: Re: Response to Meltdown and Spectre To: freebsd-questions@freebsd.org References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> <044e62f7-69ca-71fe-34a8-5c5cafc06f08@yahoo.com> <0520dd84-c00c-fbf2-da1c-f6ff4c63739d@yahoo.com> <20180203224612.GA10517@milliways.localdomain> <51178.108.68.160.114.1517699531.squirrel@cosmo.uchicago.edu> From: Paul Pathiakis Message-ID: <04967319-e627-9efa-2049-e35f8e1a42ba@yahoo.com> Date: Sun, 4 Feb 2018 10:36:22 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Feb 2018 15:36:37 -0000 On 02/03/2018 20:00, Christian Weisgerber wrote: > On 2018-02-03, "Valeri Galtsev" wrote: > >> With all due respect, one person saying, it didn't affect me, doesn't >> prove it is not disastrous for somebody else. Even if it is one machine >> out of thousand that is "bricked" for some time, it is a disaster for >> sysadmin who has that machine as a production server > Of course, but who at all is saying that Intel's microcode updates > have "bricked" any machines? This appears to be an entirely spurious > claim, based on nothing other than grievous exaggeration that turns > "higher system reboots" into "bricked". You guys are talking each > other into a frenzy of fear over nothing. > I would say we are not panicking in any manner. Nor are we in a frenzy. Real sysadmins are cautious on everything/anything that can affect the availability of the machines. Any machine that is 'unreliable' is 'bricked' or 'near-bricked' to us. It causes a major question about availability of the machine. If Intel's patch hadn't immediately caused issues, it may have caused something that might not have been caught after it was rolled out to farms (aka 1000s) of machine. What then? There was a similar issue in the UK (I have since forgotten the name of the data center owner) about 8 (or more) years regarding fujitsu hard drives. The data center was doing an excellent job of tracking hard drive replacement every five years. Fujitsu gave a great bid and shipped the drives..... After less than 6 months, the drives started to fail. All the drives needed to be replaced after they had just replaced all the drives a few months previous. The company almost went under. It's that simple in the world of a sysadmins in charge of a large number of systems. Had that patch been rolled out to thousands and failed months later..... P.