Bug#884094: Impact on NFS shared
Here are the results:
root@xxx:~# uname -v
#1 SMP Debian 4.9.51-1 (2017-09-28)
root@xxx:~# dpkg -l linux-image-4.9.0-4-amd64
ii linux-image-4.9.0-4-amd64 4.9.65-3 amd64 Linux 4.9 for 64-bit PCs
root@video-test:~# debsums -c linux-image-4.9.0-4-amd64
/boot/System.map-4.9.0-4-amd64
/boot/config-4.9.0-4-amd64
/boot/vmlinuz-4.9.0-4-amd64
root@xxx:~# uname -a
Linux xxx 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux
Still available for further informations.
> ----------------------------------------
> From: Ben Hutchings <ben@decadent.org.uk>
> Sent: Sat Dec 16 03:16:31 CET 2017
> To: Louis Chanouha <louis.chanouha@univ-toulouse.fr>, <884094@bugs.debian.org>
> Subject: Re: Bug#884094: Impact on NFS shared
>
>
> On Sat, 2017-12-16 at 00:28 +0100, Louis Chanouha wrote:
> > I'm not Linux kernel neither Debian boot friendly, my apologies if
> > I'm missing anything.
> > This error occurred after a reboot on an fresh install of Debian
> > STRETCH (not upgraded from Jessie), consecutive after an apt upgrade
> > command (with kernel update).
> > This installation is very standard (but with LVM layer), no
> > modifications regarding boot configuration were done (debian
> > installer did the job).
> >
> > Tell me if you need something from me, I would me glad to help.
>
> Try these commands:
>
> uname -v
> dpkg -l linux-image-4.9.0-4-amd64
> debsums -c linux-image-4.9.0-4-amd64
>
> Ben.
>
> --
> Ben Hutchings
> Teamwork is essential - it allows you to blame someone else.
>
Reply to: