mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chris Rankin" <rankincj@yahoo.com>
To: tigran@veritas.com
Cc: linux-kernel@vger.kernel.org
Subject: Loading Pentium III microcode under Linux - catch 22!
Date: Thu, 7 Aug 2003 13:28:50 +0100 (BST)	[thread overview]
Message-ID: <20030807122850.99548.qmail@web40611.mail.yahoo.com> (raw)

Tigran,

I have an i840 motherboard with a pair of 933 MHz PIII
Coppermine CPUs, and I use your microcode driver to
load the latest Intel microcode into my CPUs. This is
very important because these CPUs are buggy without
their microcode, and I would prefer to have the BIOS
load it except that this would prevent me from booting
into memtest. I have tried this before - memtest
crashes with an "Unexpected Interrupt" error after a
few minutes. (No i840 workarounds enabled?) Since I
suspect that DOS would do the same thing and I would
boot into DOS to flash firmware, I have decided that
crashes like this would be a Bad Thing.

I have modified by boot scripts to load the microcode
as soon as the root filesystem has been successfully
mounted. However, this means that kernel always boots
on buggy CPUs! For example, last night my boot failed
just after releasing the unused kernel memory. I
suspect that the record temperatures that my part of
the world is currently experiencing is adversely
influencing things. My boot-ups are usually fine.

In an ideal world, I would like Linux to load the
microcode *before* the kernel boots, which begs the
question of "How?". Can you suggest anything, please?
I remember talk of boot-time RAM disks, and wondered
if the microcode could be placed on one of these
somehow? Or would that be ruled out immediately by the
microcode's non-GPL nature?

Any suggestions gratefully received,
Thanks,
Chris Rankin


________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://uk.messenger.yahoo.com/

             reply	other threads:[~2003-08-07 12:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07 12:28 Chris Rankin [this message]
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
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=20030807122850.99548.qmail@web40611.mail.yahoo.com \
    --to=rankincj@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tigran@veritas.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®