Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

2018-01-13 Thread Henrique de Moraes Holschuh
On Sat, 13 Jan 2018, Thomas Liske wrote: > wouldn't the microcode updates included into the initrd automaticly? I > don't find any config option in intel-microcode or initramfs-tools to > disable adding the microcode updates. I would expect that > intel-microcode is removed in such cases. /etc/def

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

2018-01-13 Thread Thomas Liske
Henrique de Moraes Holschuh writes: > On Sat, 13 Jan 2018, Thomas Liske wrote: >> # iucode_tool -Sl /lib/firmware/intel-ucode/ > > It would have to be: > > iucode_tool -Sl /lib/firmware/intel-ucode /usr/share/misc/intel-microcode* > > and that could still miss something. > > > Maybe it would be

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

2018-01-13 Thread Henrique de Moraes Holschuh
On Sat, 13 Jan 2018, Paul Wise wrote: > It should be enough, but it would be better to handle all cases IMO. > I have no idea if iucode-tool handles systems with multiple sockets, > so I am CCing Debian's Intel/AMD microcode maintainer. Current versions of iucode_tool will include microcode for ev

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

2018-01-13 Thread Henrique de Moraes Holschuh
On Sat, 13 Jan 2018, Thomas Liske wrote: > # iucode_tool -Sl /lib/firmware/intel-ucode/ It would have to be: iucode_tool -Sl /lib/firmware/intel-ucode /usr/share/misc/intel-microcode* and that could still miss something. Maybe it would be best to look inside the initrds directly, too... iucod

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

2018-01-13 Thread Thomas Liske
Hi, Paul Wise writes: > On Sat, 2018-01-13 at 14:20 +0100, Thomas Liske wrote: > >> during adding the feature in needrestart I've looked more closely at the >> uicode-tool stuff. I don't think we need to examine the initrd since >> the following command should give already the required informa

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

2018-01-13 Thread Paul Wise
On Sat, 2018-01-13 at 14:20 +0100, Thomas Liske wrote: > during adding the feature in needrestart I've looked more closely at the > uicode-tool stuff. I don't think we need to examine the initrd since > the following command should give already the required informations: > > # iucode_tool -Sl /li

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

2018-01-13 Thread Thomas Liske
Hi Paul, during adding the feature in needrestart I've looked more closely at the uicode-tool stuff. I don't think we need to examine the initrd since the following command should give already the required informations: # iucode_tool -Sl /lib/firmware/intel-ucode/ iucode_tool: system has proces

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

2018-01-08 Thread Thomas Liske
tags 886445 upstream thanks Hi Paul, thanks for summarising your findings. I'm going add the new feature to handle the microcode update problem in needrestart 3.0. HTH, Thomas Paul Wise writes: > Package: needrestart > Version: 2.11-4 > Severity: wishlist > > Please detect the need to reb

Bug#886445: needrestart: detect need to reboot due to Intel microcode updates

2018-01-05 Thread Paul Wise
Package: needrestart Version: 2.11-4 Severity: wishlist Please detect the need to reboot to apply Intel microcode updates. When iucode_tool is installed, please check if /boot/initrd.img* contain the same microcode rev for the current CPU signature as the Linux kernel is listing in /proc/cpuinfo