From: Samuli Suonpaa <suonpaa@iki.fi>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: robw@optonline.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Intel And Kenrel Programming
Date: Sun, 12 Jan 2003 21:30:27 +0200 [thread overview]
Message-ID: <87y95qjhd8.fsf@puck.erasmus.jurri.net> (raw)
In-Reply-To: <1042394046.15051.21.camel@irongate.swansea.linux.org.uk> (Alan Cox's message of "12 Jan 2003 17:54:07 +0000")
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> For example the O(1) scheduler will trigger very occasional random
> crashes or reboots with early PII Xeon microcode sets. I'm sure
> Debian has a package for this somewhere.
Something like this, I guess:
$ apt-cache show microcode.ctl
Package: microcode.ctl
[...]
Description: Intel IA32 CPU Microcode Utility
The microcode_ctl utility is a companion to the IA32 microcode driver
written by Tigran Aivazian <tigran@veritas.com>. The utility has two
uses:
.
a) it decodes and sends new microcode to the kernel driver to be
uploaded to Intel IA32 family processors. (Pentium Pro, PII,
Celeron, PIII, Xeon, Pentium 4 etc.)
b) it signals the kernel driver to release any buffers it may hold
.
The microcode update is volatile and needs to be uploaded on each
system boot i.e. it doesn't re-flash your CPU permanently, reboot and
it reverts back to the old microcode. The ideal place to load
microcode is in BIOS, but most vendors never update it!
.
To enable microcode update, I need some kernel support, thus I need
the linux kernel 2.2.18 or later, or 2.4.0 or later.
Suonpää...
next prev parent reply other threads:[~2003-01-12 19:23 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 15:29 Nvidia and its choice to read the GPL "differently" Larry Sendlosky
2003-01-11 1:58 ` Rob Wilkens
2003-01-11 2:07 ` Larry McVoy
2003-01-11 2:13 ` Rob Wilkens
2003-01-11 2:17 ` Larry McVoy
2003-01-11 2:38 ` Rob Wilkens
2003-01-11 2:41 ` Larry McVoy
2003-01-11 2:46 ` Rob Wilkens
2003-01-11 21:44 ` Kurt Garloff
2003-01-11 21:53 ` Rob Wilkens
2003-01-11 22:16 ` Chief Gadgeteer
2003-01-11 22:26 ` Kurt Garloff
2003-01-11 23:23 ` Rob Wilkens
2003-01-12 3:33 ` Mark Mielke
2003-01-12 3:43 ` Rob Wilkens
2003-01-12 4:19 ` David Schwartz
2003-01-13 13:51 ` Richard B. Johnson
2003-01-12 4:00 ` Valdis.Kletnieks
2003-01-12 4:04 ` Rob Wilkens
2003-01-12 7:47 ` Chuck Wolber
2003-01-12 14:42 ` Intel And Kenrel Programming (was: Nvidia is a great company) Rob Wilkens
2003-01-12 16:45 ` Alan Cox
2003-01-12 16:58 ` Rob Wilkens
2003-01-12 17:54 ` Alan Cox
2003-01-12 19:30 ` Samuli Suonpaa [this message]
2003-01-12 19:46 ` Valdis.Kletnieks
2003-01-11 22:36 ` Nvidia and its choice to read the GPL "differently" Vojtech Pavlik
2003-01-11 22:57 ` Rob Wilkens
2003-01-12 1:06 ` The GPL, the kernel, and everything else Ryan Anderson
2003-01-12 4:15 ` Rob Wilkens
2003-01-12 4:21 ` David Lang
2003-01-12 4:55 ` Rob Wilkens
2003-01-12 5:10 ` David Lang
2003-01-12 5:45 ` Rob Wilkens
2003-01-12 5:12 ` Stephen Satchell
2003-01-16 16:28 ` Mark H. Wood
2003-01-16 16:41 ` venom
2003-01-16 18:22 ` John Alvord
2003-01-12 11:13 ` Nvidia and its choice to read the GPL "differently" Andrew McGregor
2003-01-12 1:44 ` [OT] Noise on lkml (was Re: Nvidia and its choice to read the GPL "differently") J Sloan
2003-01-12 3:18 ` Rob Wilkens
2003-01-12 4:08 ` Scott Murray
2003-01-11 3:26 ` Nvidia and its choice to read the GPL "differently" Alan Cox
2003-01-11 2:54 ` Larry McVoy
2003-01-11 2:58 ` Rob Wilkens
2003-01-11 3:11 ` Zwane Mwaikambo
2003-01-11 3:14 ` Rob Wilkens
2003-01-11 3:16 ` John Adams
2003-01-11 3:35 ` Rob Wilkens
2003-01-11 3:48 ` Hans Sgier
2003-01-11 3:55 ` Rob Wilkens
2003-01-11 4:41 ` J Sloan
2003-01-11 4:44 ` Rob Wilkens
2003-01-11 5:09 ` Andre Hedrick
2003-01-11 5:12 ` OT: Renaming the kernel??!?!?!? (Was Re: Nvidia and its choice to read the GPL "differently") Brian Davids
2003-01-11 15:57 ` Nvidia and its choice to read the GPL "differently" Tom Sightler
2003-01-11 3:27 ` Brian Tinsley
[not found] ` <1042256385.1259.106.camel@RobsPC.RobertWilkens.com>
2003-01-11 4:16 ` Brian Tinsley
2003-01-11 3:52 ` yodaiken
2003-01-11 4:05 ` Rob Wilkens
2003-01-11 5:45 ` Martin J. Bligh
2003-01-11 6:01 ` Tomas Szepe
2003-01-11 15:03 ` Rob Wilkens
2003-01-11 19:41 ` Andre Hedrick
2003-01-11 21:18 ` Rob Wilkens
2003-01-11 6:32 ` Ryan Anderson
2003-01-11 2:55 ` Rob Wilkens
2003-01-11 3:20 ` Tom Sightler
2003-01-11 19:48 ` Mark Mielke
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=87y95qjhd8.fsf@puck.erasmus.jurri.net \
--to=suonpaa@iki.fi \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=robw@optonline.net \
/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;
as well as URLs for NNTP newsgroup(s).