Well the problem's fixable, so caveat emptor due diligence etc. the consumer now knows they're buying a flawed CPU. The question is whether Intel should drop their price point 30% to account for the diminished CPU.
Kind regards Paul Wilkins On 14 January 2018 at 11:20, Michelle Sullivan <miche...@sorbs.net> wrote: > Paul Wilkins wrote: > >> Latest advice from Intel: >> >> https://security-center.intel.com/advisory.aspx?intelid=INTE >> L-SA-00088&languageid=en-fr >> >> No mention of warranty :) >> >> News to me, defect applies also in AMD and ARM. >> >> Very interested to hear if anyone takes this to Dep't Fair Trading and >> the response. >> >> > What will be as interesting is the word on why they are still selling > flawed processors.... especially as they have indicated there is no way to > fix it with an update. Can you imagine selling a car that doesn't actually > have working brakes and then saying, "not our problem it's working as > designed"... > > Michelle > > Kind regards >> >> Paul Wilkins >> >> >> On 8 January 2018 at 11:50, James Hodgkinson <yale...@ricetek.net >> <mailto:yale...@ricetek.net>> wrote: >> >> Yep, we have security appliances sold on performance figures >> that’ll be checked and pointed at pretty firmly post patching. >> >> >> On Mon, 8 Jan 2018, at 09:57, Mark Newton wrote: >> >>> The phrase, “Of merchantable quality and fitness for purpose,” >>> will become increasingly familiar to vendors over the next few weeks. >>> >>> Note that if you have relied on performance statements from a >>> server vendor, and that performance can’t be delivered because >>> the CPU can’t operate as advertised, both the CPU vendor /and the >>> server vendor/ have an obligation to make good. >>> >>> Start on page 5: >>> https://www.accc.gov.au/system/files/Warranties%20and%20refu >>> nds%20-%20a%20guide%20for%20consumers%20and%20business.pdf >>> <https://www.accc.gov.au/system/files/Warranties%20and%20ref >>> unds%20-%20a%20guide%20for%20consumers%20and%20business.pdf> >>> >>> >>> - mark >>> >>> >>> >>> On Jan 5, 2018, at 1:18 AM, Giles Pollock <glp...@gmail.com >>> <mailto:glp...@gmail.com>> wrote: >>> >>>> >>>> From their warranty section: >>>> >>>> WHAT THIS LIMITED WARRANTY DOES NOT COVER: >>>> • design defects or errors in the Product (Errata). Contact >>>> Intel for information on characterized errata. >>>> • any costs associated with the repair or replacement of the >>>> Product, including costs of removal or replacement of the Product; >>>> • damage to the Product, or errors or malfunctions in the >>>> Product, due to accident, abnormal electrical, mechanical or >>>> environmental conditions, use contrary to product instructions, >>>> misuse, neglect, alteration, mishandling, repair, improper >>>> installation or testing, combinations with incompatible products >>>> or any third party virus, infection, worm or similar malicious >>>> code; >>>> • that the Product will protect against all possible security >>>> threats, including intentional misconduct by third parties; >>>> • any Product which has been modified or operated outside of >>>> Intel’s publicly available specifications, including where clock >>>> frequencies or voltages have been altered, or where the original >>>> identification markings have been removed, altered or >>>> obliterated. Intel assumes no responsibility that the Product, >>>> including if used with altered clock frequencies or voltages, >>>> will be fit for any particular purpose and will not cause any >>>> damage or injury. >>>> >>>> Option 1 and 4 seems to have them covered :-( >>>> >>>> On Fri, Jan 5, 2018 at 1:07 AM, James Hodgkinson >>>> <yale...@ricetek.net <mailto:yale...@ricetek.net>> wrote: >>>> >>>> >>>> Watch them pull out the “this warranty doesn’t actually >>>> cover anything, and we don’t say it’ll work in all >>>> conditions” card. It’ll be nice to get a free CPU if they do >>>> have to, however! :) >>>> >>>> On Thu, 4 Jan 2018, at 18:32, Damien Gardner Jnr wrote: >>>> >>>>> If the hardware is under warranty, I'd be expecting the >>>>> vendor to replace the CPU's with updated ones which are not >>>>> affected? (oh man that's going to hurt Intel?) >>>>> >>>>> On 4 January 2018 at 16:31, Burt Mascareigne >>>>> <b...@stormnetwork.com.au >>>>> <mailto:b...@stormnetwork.com.au>> wrote: >>>>> >>>>> So, with this performance hit, does that mean we have >>>>> to buy more Intel Servers to cope O_o >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> >>>>> >>>>> *Burt Mascareigne >>>>> Mobile* 0414 450 962 *Office* (02) 9965 5422 >>>>> *Address* Level 19, 1 O’Connell Street, Sydney NSW 2000 >>>>> *Web* http://www.stormnetwork.com.au >>>>> <http://www.stormnetwork.com.au/> <image002.png> >>>>> >>>>> >>>>> >>>>> *From:*AusNOG [mailto:ausnog-boun...@lists.ausnog.net >>>>> <mailto:ausnog-boun...@lists.ausnog.net>] *On Behalf Of >>>>> *Paul Wilkins >>>>> *Sent:* Thursday, 4 January 2018 3:52 PM >>>>> *To:* ausnog@lists.ausnog.net >>>>> <mailto:ausnog@lists.ausnog.net> >>>>> *Subject:* [AusNOG] [AUSNOG] MS patches Intel memory >>>>> management >>>>> >>>>> >>>>> Fix for security bug in Intel CPUs will be released >>>>> patch Tuesday, and predictions are of a 5 - 30% >>>>> performance hit. >>>>> >>>>> This is a problem in cloud, but I'm sure it will all be >>>>> good on the day :) >>>>> >>>>> Kind regards >>>>> >>>>> Paul Wilkins >>>>> >>>>> >>>>> _______________________________________________ >>>>> AusNOG mailing list >>>>> AusNOG@lists.ausnog.net <mailto:AusNOG@lists.ausnog.net> >>>>> http://lists.ausnog.net/mailman/listinfo/ausnog >>>>> <http://lists.ausnog.net/mailman/listinfo/ausnog> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Damien Gardner Jnr >>>>> VK2TDG. Dip EE. GradIEAust >>>>> rend...@rendrag.net <mailto:rend...@rendrag.net> - >>>>> http://www.rendrag.net/_ >>>>> _-- >>>>> We rode on the winds of the rising storm, >>>>> We ran to the sounds of thunder. >>>>> We danced among the lightning bolts, >>>>> and tore the world asunder >>>>> >>>>> _________________________________________________ >>>>> AusNOG mailing list >>>>> AusNOG@lists.ausnog.net <mailto:AusNOG@lists.ausnog.net> >>>>> http://lists.ausnog.net/mailman/listinfo/ausnog >>>>> <http://lists.ausnog.net/mailman/listinfo/ausnog> >>>>> >>>> >>>> >>>> _______________________________________________ >>>> AusNOG mailing list >>>> AusNOG@lists.ausnog.net <mailto:AusNOG@lists.ausnog.net> >>>> http://lists.ausnog.net/mailman/listinfo/ausnog >>>> <http://lists.ausnog.net/mailman/listinfo/ausnog> >>>> >>>> >>>> _______________________________________________ >>>> AusNOG mailing list >>>> AusNOG@lists.ausnog.net <mailto:AusNOG@lists.ausnog.net> >>>> http://lists.ausnog.net/mailman/listinfo/ausnog >>>> <http://lists.ausnog.net/mailman/listinfo/ausnog> >>>> >>> >>> _________________________________________________ >>> AusNOG mailing list >>> AusNOG@lists.ausnog.net <mailto:AusNOG@lists.ausnog.net> >>> http://lists.ausnog.net/mailman/listinfo/ausnog >>> <http://lists.ausnog.net/mailman/listinfo/ausnog> >>> >> >> >> _______________________________________________ >> AusNOG mailing list >> AusNOG@lists.ausnog.net <mailto:AusNOG@lists.ausnog.net> >> http://lists.ausnog.net/mailman/listinfo/ausnog >> <http://lists.ausnog.net/mailman/listinfo/ausnog> >> >> >> >> >> _______________________________________________ >> AusNOG mailing list >> AusNOG@lists.ausnog.net >> http://lists.ausnog.net/mailman/listinfo/ausnog >> > > _______________________________________________ > AusNOG mailing list > AusNOG@lists.ausnog.net > http://lists.ausnog.net/mailman/listinfo/ausnog >
_______________________________________________ AusNOG mailing list AusNOG@lists.ausnog.net http://lists.ausnog.net/mailman/listinfo/ausnog