Bug 101332 - "kernel-utils-2.4-8.31" microcode update fails
"kernel-utils-2.4-8.31" microcode update fails
Product: Red Hat Linux Beta
Classification: Retired
Component: kernel-utils (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-07-30 17:33 EDT by Joachim Frieben
Modified: 2015-01-04 17:02 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-30 00:10:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joachim Frieben 2003-07-30 17:33:30 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
On a PR440FX Dual Pentium Pro system, "kernel-utils-2.4-8.31" seems to fail to 
update the CPU microcode. The corresponding message in /var/log/dmesg reads

  "IA-32 Microcode Update Driver: v1.11 <tigran@veritas.com>
   microcode: CPU0 no microcode found! (sig=619, pflags=0)
   microcode: CPU1 no microcode found! (sig=619, pflags=0)"

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Reboot machine.
2. Type "dmesg".
3. Look at messages issued by microcode update utility.

Actual Results:  The above error message is displayed.

Expected Results:  There should be a message about the successful update of the 
microcode or not depending of the CPU revision.

Additional info: 

Same behaviour observed on an IBM Thinkpad 600e.
Comment 1 Dave Jones 2004-10-25 23:10:19 EDT
fixed in an update ?
also what OS are you running? Fedora ? RHEL ?
Comment 2 Joachim Frieben 2004-10-28 02:47:29 EDT
The bug report had originally been posted for FC1 test 1. There has
never been any update for this package, neither for the final release
of FC1 nor among the released updates.
The bug was definitely resolved as of kernel-utils-2.4-9.1.131 after
upgrading to FC2.

Note You need to log in before you can comment on or make changes to this bug.