From: Jason Weisberger <jbdubbs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Microcode update AMD
Date: Mon, 17 Jan 2011 16:59:26 -0500 [thread overview]
Message-ID: <AANLkTin1ukYo5hobwE+OZqshRs25u6otoLHn6OPb+SK5@mail.gmail.com> (raw)
In-Reply-To: <4d34ab51.815bdf0a.4d62.ffffcd2e@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
The word "probably" implies that you have no idea what the statistics were
on getting a perfectly good core were or why they disabled entire batches of
cores based on an error from one.
You are just overdriving your point. If he doesn't want to enable updation
of microcode, it won't hurt anything. If it was functioning fine before, it
will also be fine without an update. There is nothing wrong with keeping
the version of code that is stable for you. It isn't stupid, its a good
rule of thumb. If it isn't broken, don't fix it.
On Jan 17, 2011 4:15 PM, "Volker Armin Hemmann" <volkerarmin@googlemail.com>
wrote:
> On Monday 17 January 2011 15:13:54 Jason Weisberger wrote:
>> As he said in the previous message, there are almost never changelogs for
>> microcode updates.
>>
>> I do, however, have to disagree with *never* disabling microcode updates.
>> If I recall properly, the AMD Phenom II 720 was able to be unlocked to 4
>> cores via a misconfiguration that enabled it with ACC. AMD later
corrected
>> this issue with a microcode update. True, some motherboards worked around
>> that fix a different way, but if you had a first gen board with ACC
support
>> you *had* to have the old microcode for it to work. The update killed
your
>> free core :)
>
> a 'free core' that is probably broken in mysterious and hard to find but
> nonetheless very dangerous ways. Thanks.
>
>
[-- Attachment #2: Type: text/html, Size: 1707 bytes --]
next prev parent reply other threads:[~2011-01-17 22:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 17:21 [gentoo-user] Microcode update AMD meino.cramer
2011-01-17 18:10 ` BRM
2011-01-17 18:34 ` meino.cramer
2011-01-17 19:14 ` Volker Armin Hemmann
2011-01-17 18:48 ` Mark Knecht
2011-01-17 19:12 ` Volker Armin Hemmann
2011-01-20 0:53 ` [gentoo-user] " walt
2011-01-20 1:08 ` walt
2011-01-17 19:08 ` [gentoo-user] " Volker Armin Hemmann
2011-01-17 19:19 ` meino.cramer
2011-01-17 19:46 ` Volker Armin Hemmann
2011-01-17 19:57 ` meino.cramer
2011-01-17 20:12 ` Mark Knecht
2011-01-17 20:52 ` Volker Armin Hemmann
2011-01-18 4:29 ` William Kenworthy
2011-01-18 15:38 ` Paul Hartman
2011-01-18 16:16 ` Mark Knecht
2011-01-18 17:34 ` Mark Knecht
2011-01-18 17:48 ` Volker Armin Hemmann
2011-02-05 14:28 ` Enrico Weigelt
2011-02-05 15:26 ` meino.cramer
2011-02-05 17:07 ` Volker Armin Hemmann
2011-02-06 11:36 ` Volker Armin Hemmann
2011-01-18 17:55 ` Paul Hartman
2011-01-18 18:21 ` Mark Knecht
2011-01-18 20:42 ` Paul Hartman
2011-01-18 20:56 ` Mick
2011-01-18 21:13 ` Paul Hartman
2011-01-18 23:08 ` Mick
2011-01-18 23:56 ` Mark Knecht
2011-01-17 20:13 ` Jason Weisberger
2011-01-17 20:49 ` Volker Armin Hemmann
2011-01-17 21:59 ` Jason Weisberger [this message]
2011-01-17 23:27 ` Volker Armin Hemmann
2011-01-18 15:39 ` [gentoo-user] " Nuno J. Silva
2011-02-05 13:34 ` [gentoo-user] " Enrico Weigelt
2011-02-05 16:15 ` Florian Philipp
2011-01-18 16:27 ` Volker Armin Hemmann
2011-01-19 17:10 ` Volker Armin Hemmann
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=AANLkTin1ukYo5hobwE+OZqshRs25u6otoLHn6OPb+SK5@mail.gmail.com \
--to=jbdubbs@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