-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
intel microcode false positive #112
Comments
I did expect iucode_tool to consider pf_mask while listing microcode updates and so needrestart does not care about it, yet. Thanks for pointing out! |
The script |
Sorry for the delay, I didn't yet have a chance to use "offending" system. I replaced the script but the iucode tool seems to be ignoring the filter?... Needrestart still reports that a reboot is needed.
|
Using the old
Using the new command line and forging the filter on the same host:
This looks really weird! |
the iucode_tool manpage says that the -s option adds signatures to the ones already detected, that's why the extra one shows up on your system. i've been trying the --scan-system=0|1|2, but can't get it to list only the 0x000006fb/0x10 pair. |
The description of
Could you please try |
Worked like a charm.
Thanks! |
Just ran This means that it's just filtering the microcode files, so a multi step procedure may be required. Something like, system detection, available firmware sorting and then a version check. |
I did already fear this behavior (or bug?) of Disclaimer: although it looks like a bug in |
It looks good. Thank you! |
Facing the same problem. Any idea how to go about this if the stock OS installed (Bionic in this case) is missing the apparently required microcode.ko kernel module? |
For intel microcode, in my case processor signature 0x6fb with pf_mask 0x10, the most recent available microcode is rev 0xba, which the early update applied. However needrestart reports:
Processor microcode update
│ The currently running processor microcode revision is 0xba which is not the expected microcode revision 0xa4.
│ Restarting the system to load the new processor microcode will not be handled automatically, so you should
│ consider rebooting.
$dmesg | grep -i microcode
[ 0.000000] microcode: microcode updated early to revision 0xba, date = 2010-10-03
[ 2.904281] microcode: sig=0x6fb, pf=0x10, revision=0xba
[ 2.904326] microcode: Microcode Update Driver: v2.2.
$/usr/sbin/iucode_tool -tb -lS /lib/firmware/intel-ucode/*
...
selected microcodes:
001/001: sig 0x000006f2, pf_mask 0x20, 2010-10-02, rev 0x005c, size 4096
001/002: sig 0x000006f2, pf_mask 0x01, 2010-10-02, rev 0x005d, size 4096
002/001: sig 0x000006f6, pf_mask 0x20, 2010-10-01, rev 0x00d1, size 4096
002/002: sig 0x000006f6, pf_mask 0x04, 2010-10-01, rev 0x00d2, size 4096
002/003: sig 0x000006f6, pf_mask 0x01, 2010-09-30, rev 0x00d0, size 4096
003/001: sig 0x000006f7, pf_mask 0x40, 2010-10-02, rev 0x006b, size 4096
003/002: sig 0x000006f7, pf_mask 0x10, 2010-10-02, rev 0x006a, size 4096
004/001: sig 0x000006fa, pf_mask 0x80, 2010-10-02, rev 0x0095, size 4096
005/001: sig 0x000006fb, pf_mask 0x80, 2010-10-03, rev 0x00ba, size 4096
005/002: sig 0x000006fb, pf_mask 0x40, 2010-10-03, rev 0x00bc, size 4096
005/003: sig 0x000006fb, pf_mask 0x20, 2010-10-03, rev 0x00ba, size 4096
005/004: sig 0x000006fb, pf_mask 0x10, 2010-10-03, rev 0x00ba, size 4096
005/005: sig 0x000006fb, pf_mask 0x08, 2010-10-03, rev 0x00bb, size 4096
005/006: sig 0x000006fb, pf_mask 0x04, 2010-10-03, rev 0x00bc, size 4096
005/007: sig 0x000006fb, pf_mask 0x01, 2010-10-03, rev 0x00ba, size 4096
006/001: sig 0x000006fd, pf_mask 0x80, 2010-10-02, rev 0x00a4, size 4096
006/002: sig 0x000006fd, pf_mask 0x20, 2010-10-02, rev 0x00a4, size 4096
006/003: sig 0x000006fd, pf_mask 0x01, 2010-10-02, rev 0x00a4, size 4096
I guess needrestart 3.1 on debian is just looking at the end of the list of the last command, without considering signature or pf_mask.
The text was updated successfully, but these errors were encountered: