Subject: Re: Bricked x86 CPU with software?
To: Tim Mouraveiko <tim.ml@ipcopper.com>, linux-kernel@vger.kernel.org
References: <5A4D7986.2138.FDC590CF@tim.ml.ipcopper.com>
From: Nikolay Borisov <n.borisov.lkml@gmail.com>
Message-ID: <6363f70b-c400-f04f-e64c-76bc2b4c4452@gmail.com>
Date: Sat, 6 Jan 2018 17:50:27 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <5A4D7986.2138.FDC590CF@tim.ml.ipcopper.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org


On  4.01.2018 02:47, Tim Mouraveiko wrote:
> Hi,
> 
> In all my years of extensive experience writing drivers and kernels, I never came across a situation 
> where you could brick an x86 CPU. Not until recently, when I was working on debugging a piece of 
> code and I bricked an Intel CPU. I am not talking about an experimental motherboard or anything 
> exotic or an electrical issue where the CPU got fried, but before the software code execution the CPU 
> was fine and then it´s dead. There were signs that something was not right, that the code was causing 
> unusual behavior, which is what I was debugging.
> 
> Has anyone else ever experienced a bricked CPU after executing software code? I just wanted to get 
> input from the community to see if anyone had had any experience like that, since it seems rather 
> unusual to me.
> 
> Tim
> 

"Code talks, bullshit walks". Unless you share the code I don't think
anyone has any reason to believe anything you said.