From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Debian/1.7.8-1

Description of problem:
When switching from various run levels (to diagnose a separate problem (XDMCP access) I see these warnings:

/etc/init.d/microcode_ctl: microcode device /dev/cpu/microcode doesn't exist?


Indeed /dev/cpu/microcode does not exist. 

If I 'modprobe microcode'

The directory is created (actually a symlink):
# ls -ld /dev/cpu/microcode
lrwxrwxrwx  1 root root 12 Aug 17 16:58 /dev/cpu/microcode -> ../microcode

 
Rerunning /etc/sbin/init.d/microcode_ctl (as will happen when switching to a higher run level) now works:
# service microcode_ctl start
Applying Intel Microcode update:                           [  OK  ]


However, if I run it again (or drop run levels and later up the run level) the warning comes back:
# service microcode_ctl start
/etc/init.d/microcode_ctl: microcode device /dev/cpu/microcode doesn't exist?


It appears the cause of this is that the /etc/init.d/microcode boot script does an 'rmmod microcode' at the end of it's start routine.

This seems like a bug, or there should be a way to quiet this warning or prevent microcode_ctl from running each time I switch run levels.

Version-Release number of selected component (if applicable):
kernel-utils-2.4-13.1.66

How reproducible:
Always

Steps to Reproduce:
1. On a booted system, run 'service microcode_ctl start'

or

1b. init 3, wait a few seconds, init 5, watch for the error on the console

  

Actual Results:  /etc/init.d/microcode_ctl: microcode device /dev/cpu/microcode doesn't exist?

Expected Results:  Applying Intel Microcode update:                           [  OK  ]


... or possibly something like:
Microcode update previously applied, skipping              [  OK  ]

Additional info: