Yes, 
in fact it is not possible to execute the apoort-collect command when the 
kernel crashed.

If someone need information about the hardware, i can boot the computer
without the nfs stab entry and execute then the command.

But i can also report the same problem from other computers ( for
example Supermicro servers )... and not only runing Xenial ... computers
running Trusty with the linux-generic-lts-xenial kernel are also
affected.


** Changed in: linux (Ubuntu)
       Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1650336

Title:
  NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
  crash on boot when in /etc/fstab a nfsv4 entry is active

  When comment the line or set to noauto the kernel boot with no error
  and mounting the nfs shares (after uncomment ) is also possible
  without error

  4.4.0-54 boots without this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650336/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to