Bug 153153 - microcode_ctl update locks machine up
microcode_ctl update locks machine up
Product: Fedora
Classification: Fedora
Component: kernel-utils (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-04-01 16:09 EST by Hrunting Johnson
Modified: 2015-01-04 17:18 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-01 16:55:06 EST
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 Hrunting Johnson 2005-04-01 16:09:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

Description of problem:
I have three Dell 6650s identically configured with identical hardware specs.  On two of them, the microcode_ctl program will lock the machine up, requiring a manual power-cycle.  On the third, it works just fine.  The older version (pre-update) works just fine.  Something in the new update is locking up the machine.

Even when I do this by hand, it will lock up the machine.

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

How reproducible:

Steps to Reproduce:
1. update to 2.4-9.1.131_FC2
2. reboot box

Actual Results:  Box hangs at 'Applying Intel Microcode Update'

Expected Results:  Box should apply the update and continue.

Additional info:

The boxes are all quad 1.5GHz Xeon machines, 1MB of cache (although Linux reports 512KB) with hyperthreading enabled.
Comment 1 Hrunting Johnson 2005-04-01 16:28:24 EST
Disabling hyperthreading prevents the hangup with the new version.  Enable
hyperthreading and it will always hang.
Comment 2 Hrunting Johnson 2005-04-01 16:55:06 EST
Grr, I'm off-base.  I thought these boxes had the latest BIOS updates, but I was
wrong.  The latest Dell BIOSes fix the problem.

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