From: Luigi Mantellini <luigi.mantellini.ml@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Microcode updates for "old" Intel CPU's
Date: Tue, 9 Jan 2018 09:43:03 +0100 [thread overview]
Message-ID: <CAGneTA3-NdZ+J+ix2==YfKVpv4KVXopx7iq8TW48r-BuH6j1MA@mail.gmail.com> (raw)
In-Reply-To: <15310596.tlLjEkevsN@peak>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
I have a less-two-old N3700 CPU on a Asrock N3700-ITX board that (was)is
perfect for my NAS, but without pcid instruction that mitigates the last
pti patches slowdown.
Asrock said nothing about the microcode/bios update and I asked for
warranty return because I consider a factory defect but I think that I will
fight with the seller.
BTW, the European Community Law requires at least 2 years of warranty
coverage on factory defects... Proud to be European.
ciao
luigi
On Mon, Jan 8, 2018 at 1:00 AM, Peter Humphrey <peter@prh.myzen.co.uk>
wrote:
> On Sunday, 7 January 2018 20:46:52 GMT Taiidan@gmx.com wrote:
> > I have several sandy/ivybridge CPU's and I was wondering if anyone knows
> > as to if intel is releasing microcode updates for them.
> >
> > It sure would be funny if intel wanted you to buy a new CPU to fix a
> > problem that was their fault to begin with.
>
> Welcome to unbridled capitalism, USA-style.
>
> --
> Regards,
> Peter.
>
>
>
--
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy
Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantellini@idf-hit.com
[-- Attachment #2: Type: text/html, Size: 2050 bytes --]
next prev parent reply other threads:[~2018-01-09 8:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 20:46 [gentoo-user] Microcode updates for "old" Intel CPU's Taiidan
2018-01-08 0:00 ` Peter Humphrey
2018-01-08 0:55 ` R0b0t1
2018-01-09 8:43 ` Luigi Mantellini [this message]
2018-01-08 4:47 ` Adam Carter
2018-01-08 17:47 ` Corbin Bird
2018-01-09 7:56 ` Mick
2018-01-10 1:33 ` Corbin Bird
2018-01-10 1:46 ` Rich Freeman
2018-01-11 22:41 ` Mick
2018-01-11 23:02 ` Rich Freeman
2018-01-12 16:23 ` Corbin Bird
2018-01-12 17:21 ` Taiidan
[not found] ` <1542759.NuuG9cTaQ6@dell_xps>
2018-01-13 18:14 ` Taiidan
2018-01-12 17:47 ` Rich Freeman
2018-01-12 18:42 ` Mick
2018-01-12 19:06 ` Rich Freeman
2018-01-12 20:32 ` Taiidan
2018-01-12 19:58 ` Corbin Bird
2018-01-12 20:18 ` Rich Freeman
2018-01-13 0:03 ` Adam Carter
2018-01-13 0:06 ` Adam Carter
2018-01-12 16:23 ` Daniel Frey
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='CAGneTA3-NdZ+J+ix2==YfKVpv4KVXopx7iq8TW48r-BuH6j1MA@mail.gmail.com' \
--to=luigi.mantellini.ml@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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