tag 701169 wontfix severity 701169 minor thanks On Fri, 22 Feb 2013, Philipp Kern wrote: > intel-microcode's initramfs hook seems to try to load microcode > unconditionally. This causes the following error messages to appear if no
Yes. > microcode is present in the package, once for every scheduling unit: > > [ 4.257698] platform microcode: firmware: agent aborted loading > intel-ucode/06-2c-02 (not found?) Those messages will still show up when you load the microcode module anyway (and it will be autoloaded, so if you want to avoid the messages at all you actually have to blacklist it), and they're caused by the firmware kernel subsystem which has no concept of a "silently try to load a binary blob and keep quiet about it if it is not found" AFAIK. > It would be good if the script could deduce the ID and not only check if the > directory is present, but also if the corresponding microcode update itself is > available. I am not adding complexity of that level to the early boot if it can be avoided: IMO, it is not worth the risk _and_ it would force the update engine to actually understand the microcode layout of the underlying processor, which is not a forward-compatible change and therefore it could cause issues in the future. I recommend that you just ignore the messages, that way you will still get an updated microcode if Intel decides to start shipping one for your processor. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
