Date: Thu, 4 Jan 2018 21:06:37 +0100
From: Pavel Machek <pavel@ucw.cz>
To: Tim Mouraveiko <tim.ml@ipcopper.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bricked x86 CPU with software?
Message-ID: <20180104200637.GC10427@amd>
References: <5A4D7986.2138.FDC590CF@tim.ml.ipcopper.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="dkEUBIird37B8yKS"
Content-Disposition: inline
In-Reply-To: <5A4D7986.2138.FDC590CF@tim.ml.ipcopper.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org


--dkEUBIird37B8yKS
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi!

> In all my years of extensive experience writing drivers and kernels, I ne=
ver came across a situation=20
> where you could brick an x86 CPU. Not until recently, when I was working =
on debugging a piece of=20
> code and I bricked an Intel CPU. I am not talking about an experimental m=
otherboard or anything=20
> exotic or an electrical issue where the CPU got fried, but before the sof=
tware code execution the CPU=20
> was fine and then it=B4s dead. There were signs that something was not ri=
ght, that the code was causing=20
> unusual behavior, which is what I was debugging.
>=20
> Has anyone else ever experienced a bricked CPU after executing software c=
ode? I just wanted to get=20
> input from the community to see if anyone had had any experience like tha=
t, since it seems rather=20
> 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
--=20
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo=
g.html

--dkEUBIird37B8yKS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlpOiU0ACgkQMOfwapXb+vIhQgCfYjW0JBTqLrw03KegK+7uvD6T
5xIAnj9QJA2Zl3UUeZ1M56JZbxhn4jjS
=xG0J
-----END PGP SIGNATURE-----

--dkEUBIird37B8yKS--