Corruption in CPU

To: debian-devel@lists.debian.org
Subject: Corruption in CPU
From: Armin Avdic <armin.avdic.2010@gmail.com>
Date: Tue, 27 Jun 2017 12:53:52 +0200
Message-id: <[🔎] CABBMyMJvcccbrzA6V2t6V2FGyuhPLBtQ2r5PqMNRNEjtzk-gyA@mail.gmail.com>
In-reply-to: <CABBMyML2MSPB2mNGZrL3ym-4J-DVB2OvAafWZU=rJ84a0GRN2A@mail.gmail.com>
References: <CABBMyMLVXyWmnZywTGOpXZwjBEhfc_5PSzBVZf_vjp7PGWKkew@mail.gmail.com> <CABBMyMKU1oxTk63U7-Rh=sueFmJ0aVsQQeZfO5HSJQf3QaRb8Q@mail.gmail.com> <CABBMyML2MSPB2mNGZrL3ym-4J-DVB2OvAafWZU=rJ84a0GRN2A@mail.gmail.com>

Hello, I saw your article on corrupted data and I have reason to believe that the bad code goes as far back to Intel Pentium D processors, in my investigation I have seen that when hyperthreading is disabled the cpu acts ok no corrupted data or corrupted downloads however when enabled the corrupted data starts showing up and changing md5 completely.

Reply to:

Follow-Ups:
- Re: Corruption in CPU
  - From: Henrique de Moraes Holschuh <hmh@debian.org>

Prev by Date: Re: IMPORTANT: Do live Debian images have a future?
Next by Date: Bug#866099: ITP: libtwelvemonkeys-java -- collection of plugins and extensions for Java's ImageIO
Previous by thread: Bug#866053: ITP: emacs-ivy-doc -- documentation for emacs' Incremental Vertical completYon
Next by thread: Re: Corruption in CPU
Index(es):
- Date
- Thread