mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tim Mouraveiko" <tim.ml@ipcopper.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bricked x86 CPU with software?
Date: Thu, 04 Jan 2018 13:00:51 -0800	[thread overview]
Message-ID: <5A4E9603.20778.21CD7C4@tim.ml.ipcopper.com> (raw)
In-Reply-To: <20180104200637.GC10427@amd>

Pavel,

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.

In case you are curious there was no overheating, no 100% utilization, no tampering with 
hardware (GPIO pins or anything of that sort), no overclocking and etc. No hardware issues 
or changes at all.

Tim

> 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.
> 
> Never seen that before. Can you try to brick another one? :-).
> 
> You may want to remove AC power and battery, wait for half an hour,
> then attempt to boot it...
> 
> 									Pavel
> -- 
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> 

  reply	other threads:[~2018-01-04 20:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04  0:47 Tim Mouraveiko
2018-01-04 20:06 ` Pavel Machek
2018-01-04 21:00   ` Tim Mouraveiko [this message]
2018-01-04 21:04     ` Andy Shevchenko
2018-01-04 21:31       ` Tim Mouraveiko
2018-01-04 21:23     ` Pavel Machek
2018-01-04 22:13       ` Tim Mouraveiko
2018-01-04 22:40         ` Pavel Machek
2018-01-05  1:21           ` Tim Mouraveiko
2018-01-05  1:29             ` Hector Martin 'marcan'
2018-01-05 18:54               ` Tim Mouraveiko
2018-01-05  9:28             ` Pavel Machek
2018-01-06  1:08               ` Tim Mouraveiko
2018-01-06 10:19                 ` Pavel Machek
2018-01-08 15:58                   ` Tim Mouraveiko
     [not found]                     ` <201801081920.21922.arekm@maven.pl>
2018-01-08 19:08                       ` Tim Mouraveiko
     [not found]                         ` <1515456557.4423.67.camel@infradead.org>
2018-01-09 21:48                           ` Tim Mouraveiko
2018-01-08 23:32                     ` Pavel Machek
2018-01-09  0:35                       ` Tim Mouraveiko
2018-01-05  1:51     ` james harvey
2018-01-06  1:00       ` Tim Mouraveiko
2018-01-06 15:50 ` Nikolay Borisov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5A4E9603.20778.21CD7C4@tim.ml.ipcopper.com \
    --to=tim.ml@ipcopper.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome