Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751550AbeADApQ convert rfc822-to-8bit (ORCPT + 1 other); Wed, 3 Jan 2018 19:45:16 -0500 Received: from smtp-16.smcloud.com ([198.36.167.16]:1778 "HELO smtp-16.smcloud.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751313AbeADApP (ORCPT ); Wed, 3 Jan 2018 19:45:15 -0500 From: "Tim Mouraveiko" Organization: IPCopper, Inc. To: linux-kernel@vger.kernel.org Date: Wed, 03 Jan 2018 16:47:02 -0800 MIME-Version: 1.0 Subject: Bricked x86 CPU with software? Message-ID: <5A4D7986.2138.FDC590CF@tim.ml.ipcopper.com> X-mailer: Pegasus Mail for Windows (4.52) Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 8BIT Content-description: Mail message body Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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