Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753513AbeADWMH (ORCPT + 1 other); Thu, 4 Jan 2018 17:12:07 -0500 Received: from smtp-16.smcloud.com ([198.36.167.16]:28358 "HELO smtp-16.smcloud.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753119AbeADWMG (ORCPT ); Thu, 4 Jan 2018 17:12:06 -0500 From: "Tim Mouraveiko" Organization: IPCopper, Inc. To: Pavel Machek Date: Thu, 04 Jan 2018 14:13:56 -0800 MIME-Version: 1.0 Subject: Re: Bricked x86 CPU with software? CC: linux-kernel@vger.kernel.org Message-ID: <5A4EA724.8051.25FC07E@tim.ml.ipcopper.com> In-reply-to: <20180104212334.GA17986@amd> References: <5A4D7986.2138.FDC590CF@tim.ml.ipcopper.com>, <5A4E9603.20778.21CD7C4@tim.ml.ipcopper.com>, <20180104212334.GA17986@amd> X-mailer: Pegasus Mail for Windows (4.52) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: > > As I mentioned before, I repeatedly and fully power-cycled the motherboard and reset BIOS > > and etc. It made no difference. I can see that the processor was not drawing any power. The > > software code behaved in a similar fashion on other processors, until I fixed it so that it would > > not kill any more processors. > > > > So you have code that killed more than one processor? Save it! We want > a copy. > > Do you have model numbers of affected CPUs? Why would you want a copy? Last time I checked bricked CPUs do not work well, even as decorations. I believe the processors were Intel Xeon series. The code would likely run on others too.