tags 827162 upstream,fixed-upstream
found 827162 needrestart/2.8-1
thanks
Re,
Martin Steigerwald <mar...@lichtvoll.de> writes:
>> Could you please provide the output of `needrestart -v -r l`? It would
>> be sufficient to provide the kernel related lines ('^[Kernel]' until
>> the kernel status message).
>
> Including everything as there are some could not get a source file messages
> that might be interesting as well.
those are just informational... it is a common problem that it is
impossible to get the source file of a running interpreter process.
> I think it doesn´t cut the kernel version string at the place where it should
> for comparing.
It looks weirrd... I've fetched the kernel from snapshot[1] and running
needrestart shows (this is strech on amd64, but the bug(?) is triggered,
too):
[Kernel/Linux] /boot/vmlinuz-4.6.0-1-686 => 4.6.0-1-686
(debian-ker...@lists.debian.org) #1 SMP Debian 4.6.4-1 (2016-07-18)
[4.6.0-1-686]
[Kernel/Linux] /boot/vmlinuz-4.6.0-1-amd64 => 4.6.0-1-amd64
(debian-ker...@lists.debian.org) #1 SMP Debian 4.6.4-1 (2016-07-18)
[4.6.0-1-amd64]*
[Kernel/Linux] /boot/vmlinuz-4.5.0-0.bpo.2-686 => 4.5.0-0.bpo.2-686
(debian-ker...@lists.debian.org) #1 SMP Debian 4.5.4-1~bpo8+1 (2016-05-13)
, [4.5.0-0.bpo.2-686 (debian-ker...@lists.debian.org) #1 SMP Debian
4.5.4-1~bpo8+1 (2016-05-13)]
^
should be [4.5.0-0.bpo.2-686]
[Kernel/Linux] /boot/vmlinuz-4.3.3-tl1+ => 4.3.3-tl1+ (root@ijon) #13 SMP
PREEMPT Thu Dec 17 10:09:53 CET 2015 [4.3.3-tl1+]
[Kernel/Linux] /boot/vmlinuz-4.3.0-tl1+ => 4.3.0-tl1+ (root@ijon) #12 SMP
PREEMPT Sat Nov 7 00:01:34 CET 2015 [4.3.0-tl1+]
[Kernel/Linux] /boot/vmlinuz-4.2.3-tl1+ => 4.2.3-tl1+ (root@ijon) #11 SMP
PREEMPT Sun Oct 4 09:52:40 CEST 2015 [4.2.3-tl1+]
[Kernel/Linux] /boot/vmlinuz-4.1.3-tl1+ => 4.1.3-tl1+ (root@ijon) #7 SMP
PREEMPT Sun Jul 26 11:43:47 CEST 2015 [4.1.3-tl1+]
[Kernel/Linux] /boot/vmlinuz-3.19.3-tl1+ => 3.19.3-tl1+ (root@ijon) #3 SMP
PREEMPT Thu Mar 26 20:06:50 CET 2015 [3.19.3-tl1+]
[Kernel/Linux] /boot/vmlinuz-3.19.0-tl1 => 3.19.0-tl1 (root@ijon) #2 SMP
PREEMPT Sat Feb 14 11:29:24 CET 2015 [3.19.0-tl1]
[Kernel/Linux] /boot/vmlinuz-3.18.0-tl1 => 3.18.0-tl1 (root@ijon) #1 SMP
PREEMPT Mon Dec 8 20:13:55 CET 2014 [3.18.0-tl1]
[Kernel/Linux] /boot/vmlinuz-3.17.6-tl1 => 3.17.6-tl1 (root@ijon) #7 SMP
PREEMPT Mon Dec 8 06:52:20 CET 2014 [3.17.6-tl1]
[Kernel/Linux] /boot/vmlinuz-3.2.0-4-amd64 => 3.2.0-4-amd64
(debian-ker...@lists.debian.org) #1 SMP Debian 3.2.51-1 [3.2.0-4-amd64]
[Kernel/Linux] Expected linux version: 4.6.0-1-amd64
[1]
http://snapshot.debian.org/archive/debian/20160614T164243Z/pool/main/l/linux/linux-image-4.5.0-0.bpo.2-686_4.5.4-1~bpo8+1_i386.deb
So I added some debug output into the NeedRestart::Kernel::Linux package
(printing the return of the nr_linux_version_x86 calls):
$VAR1 = '4.6.0-1-686 (debian-ker...@lists.debian.org) #1 SMP Debian 4.6.4-1
(2016-07-18)';
$VAR2 = 1;
$VAR1 = '4.6.0-1-amd64 (debian-ker...@lists.debian.org) #1 SMP Debian 4.6.4-1
(2016-07-18)';
$VAR2 = 1;
$VAR1 = '4.5.0-0.bpo.2-686 (debian-ker...@lists.debian.org) #1 SMP Debian
4.5.4-1~bpo8+1 (2016-05-13)
,';
$VAR2 = 1;
$VAR1 = '4.3.3-tl1+ (root@ijon) #13 SMP PREEMPT Thu Dec 17 10:09:53 CET 2015';]
$VAR2 = 1;
Ooops - there is a newline for 4.5.0-0.bpo.2-686... and the chomp/regex
foo did not remove it since a missing 's' regex modifier. Has been fixed
upstream [master 7249b2c]:
[Kernel/Linux] /boot/vmlinuz-4.5.0-0.bpo.2-686 => 4.5.0-0.bpo.2-686
(debian-ker...@lists.debian.org) #1 SMP Debian 4.5.4-1~bpo8+1 (2016-05-13)
, [4.5.0-0.bpo.2-686]
HTH,
Thomas
> mondschein:~> LANG=C needrestart -v -r l
> [main] eval /etc/needrestart/needrestart.conf
> [main] running in root-mode
> [Core] Using UI 'NeedRestart::UI::stdio'...
> [Core] #2101 is a NeedRestart::Interp::Python
> [Core] #2102 is a NeedRestart::Interp::Python
> [Core] #2103 is a NeedRestart::Interp::Python
> [Core] #2104 is a NeedRestart::Interp::Python
> [Core] #2105 is a NeedRestart::Interp::Python
> [Core] #2106 is a NeedRestart::Interp::Python
> [Core] #2107 is a NeedRestart::Interp::Python
> [Core] #2108 is a NeedRestart::Interp::Python
> [Core] #2109 is a NeedRestart::Interp::Python
> [Core] #2493 is a NeedRestart::Interp::Perl
> [Perl] #2493: could not get a source file, skipping
> [Core] #2495 is a NeedRestart::Interp::Perl
> [Perl] #2495: could not get a source file, skipping
> [Core] #2590 is a NeedRestart::Interp::Perl
> [Perl] #2590: could not get a source file, skipping
> [Core] #2843 is a NeedRestart::Interp::Perl
> [Perl] #2843: could not get a source file, skipping
> [Core] #2844 is a NeedRestart::Interp::Perl
> [Perl] #2844: could not get a source file, skipping
> [Core] #7943 is a NeedRestart::Interp::Perl
> [Perl] #7943: could not get a source file, skipping
> [Core] #9811 is a NeedRestart::Interp::Perl
> [Perl] #9811: could not get a source file, skipping
> [Kernel] Linux: kernel release 4.5.0-0.bpo.2-686, kernel version #1 SMP
> Debian
> 4.5.4-1~bpo8+1 (2016-05-13)
> Failed to load NeedRestart::Kernel::kFreeBSD: [Kernel/kFreeBSD] Not running
> on
> GNU/kFreeBSD!
> [Kernel/Linux] /boot/vmlinuz-4.5.0-0.bpo.2-686 => 4.5.0-0.bpo.2-686 (debian-
> ker...@lists.debian.org) #1 SMP Debian 4.5.4-1~bpo8+1 (2016-05-13)
> , [4.5.0-0.bpo.2-686 (debian-ker...@lists.debian.org) #1 SMP Debian
> 4.5.4-1~bpo8+1 (2016-05-13)]*
> [Kernel/Linux] /boot/vmlinuz-4.4.0-0.bpo.1-686 => 4.4.0-0.bpo.1-686 (debian-
> ker...@lists.debian.org) #1 SMP Debian 4.4.6-1~bpo8+1 (2016-03-20)
> , [4.4.0-0.bpo.1-686 (debian-ker...@lists.debian.org) #1 SMP Debian
> 4.4.6-1~bpo8+1 (2016-03-20)]
> [Kernel/Linux] /boot/vmlinuz-3.16.0-4-686-pae => 3.16.0-4-686-pae (debian-
> ker...@lists.debian.org) #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08)
> [3.16.0-4-686-pae]
> [Kernel/Linux] Expected linux version: 4.5.0-0.bpo.2-686 (debian-
> ker...@lists.debian.org) #1 SMP Debian 4.5.4-1~bpo8+1 (2016-05-13)
> Pending kernel upgrade!
>
> Running kernel version:
> 4.5.0-0.bpo.2-686
>
> Diagnostics:
> The currently running kernel version is not the expected kernel version
> 4.5.0-0.bpo.2-686 (debian-ker...@lists.debian.org) #1 SMP Debian
> 4.5.4-1~bpo8+1 (2016-05-13).
>
> Restarting the system to load the new kernel will not be handled
> automatically, so you should consider rebooting. [Return]
>
> No services need to be restarted.
> No containers need to be restarted.
> No user sessions are running outdated binaries.
>
> Thanks,
> --
> Martin
>
--
:: WWW: https://fiasko-nw.net/~thomas/ ::
::: Jabber: xmpp:tho...@jabber.fiasko-nw.net :::
:: flickr: https://www.flickr.com/photos/laugufe/ ::
