From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: Chris Rankin <rankincj@yahoo.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Loading Pentium III microcode under Linux - catch 22!
Date: Fri, 08 Aug 2003 09:12:41 +1000 [thread overview]
Message-ID: <3F32DCE9.74E61CF9@eyal.emu.id.au> (raw)
In-Reply-To: <20030807143831.73389.qmail@web40603.mail.yahoo.com>
Chris Rankin wrote:
>
> --- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > As far as I am aware none of the microcode updates
> > even apply to 933Mhz era PIII, just the ones the
> > BIOS ships with by default nowdays. Also the kind of
> > stuff the errata fix are obscure ultra-weird corner
> > cases people just don't hit.
>
> Lucky me, eh?
>
> My CPUs *do* take microcode, and they are 933 MHz...
> ;-). I upgraded from a pair of 733 MHz CPUs bought in
Some random ideas:
- reinstall the slower, stable CPUs and burn the BIOS
If you are a linux hacker then you kept these
"just in case".. or else
- get a loaner CPU and use it to burn the BIOS
If you are a linux hacker then you have no
life and no friends to get a loaner from but
you do have a roomfull of computer parts...
otherwise
- install only one CPU, it may be more stable
- run your CPU slower than spec, it may be more stable
most microcode bugs are not timining sensitive
but it is worth a try
Good luck.
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
next prev parent reply other threads:[~2003-08-07 23:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 12:28 Chris Rankin
2003-08-07 13:04 ` Måns Rullgård
2003-08-07 13:58 ` Alan Cox
2003-08-07 14:38 ` Chris Rankin
2003-08-07 14:53 ` Alan Cox
2003-08-07 15:21 ` Tomas Szepe
2003-08-07 15:41 ` Chris Rankin
2003-08-07 23:12 ` Eyal Lebedinsky [this message]
2003-08-07 15:57 ` Tigran Aivazian
2003-08-07 15:55 ` Alan Cox
2003-08-08 8:24 ` Chris Rankin
2003-08-07 17:40 Nakajima, Jun
2004-01-13 19:00 ` Alan Cox
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=3F32DCE9.74E61CF9@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rankincj@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®