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?
Date: Thu, 4 Jan 2018 22:23:34 +0100 [thread overview]
Message-ID: <20180104212334.GA17986@amd> (raw)
In-Reply-To: <5A4E9603.20778.21CD7C4@tim.ml.ipcopper.com>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
Hi!
> 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?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-01-04 21:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 0:47 Bricked x86 CPU with software? Tim Mouraveiko
2018-01-04 20:06 ` Pavel Machek
2018-01-04 21:00 ` Tim Mouraveiko
2018-01-04 21:04 ` Andy Shevchenko
2018-01-04 21:31 ` Tim Mouraveiko
2018-01-04 21:23 ` Pavel Machek [this message]
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=20180104212334.GA17986@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.ml@ipcopper.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.