George Robbert wrote:
> On an intel system, where uCode/AMD.pm was run before uCode/Intel.pm
>
> intel_sys1# needrestart -b
> NEEDRESTART-VER: 3.6
> NEEDRESTART-KCUR: 6.1.0-18-amd64
> NEEDRESTART-KEXP: 6.1.0-18-amd64
> NEEDRESTART-KSTA: 1
> NEEDRESTART-UCSTA: 1
> Use of uninitialized value $ucode_vars{"CURRENT"} in concatenation (.) or
> string at /usr/sbin/needrestart line 940.
> NEEDRESTART-UCCUR:
> Use of uninitialized value $ucode_vars{"AVAIL"} in concatenation (.) or
> string at /usr/sbin/needrestart line 941.
> NEEDRESTART-UCEXP:
I have been seeing these exact uninitialized value errors on my
machines too. Very annoying as I am often using dsh to scan a large
collective of systems and the noise from these errors obscures the
information want to read.
> The attached patch fixes includes the previous patch and also fixes
> these 2 issues.
I have applied this second patch from George on my systems both Stable
and Unstable and it has solved the uninitialized value errors for me.
I saw no problems patching or running. It is oh so very nice not to
be seeing those uninitialized value errors.
Example on an Debian Unstable Sid system.
root@clash:/# needrestart -b
NEEDRESTART-VER: 3.6
NEEDRESTART-KCUR: 6.4.0-4-amd64
NEEDRESTART-KEXP: 6.4.0-4-amd64
NEEDRESTART-KSTA: 1
NEEDRESTART-UCSTA: 1
Use of uninitialized value $ucode_vars{"CURRENT"} in concatenation (.) or
string at /usr/sbin/needrestart line 940.
NEEDRESTART-UCCUR:
Use of uninitialized value $ucode_vars{"AVAIL"} in concatenation (.) or
string at /usr/sbin/needrestart line 941.
NEEDRESTART-UCEXP:
root@clash:/# patch -p0 < /var/tmp/needrestart-ghr-2.patch
patching file /usr/share/perl5/NeedRestart/uCode.pm
Hunk #2 succeeded at 179 with fuzz 1.
root@clash:/# needrestart -b
NEEDRESTART-VER: 3.6
NEEDRESTART-KCUR: 6.4.0-4-amd64
NEEDRESTART-KEXP: 6.4.0-4-amd64
NEEDRESTART-KSTA: 1
NEEDRESTART-UCSTA: 0
Looks good to me! :-)
Bob
