Hello, I believe at the moment that neither the nvidia driver for the Quadro P400 nor ZFS are available with the mainline kernel, after reading https://wiki.ubuntu.com/Kernel/MainlineBuilds and trying to check the actual contents of the repository. Please correct me if I am wrong. Without these modules and functionality the workstations would be useless to us. Also, please take into account that this bug appears to trigger only sporadically when considering my reply.
So, from my perspective it is unfortunately not possible to test the mainline kernel. I will upgrade to the current kernel which appears to be the best thing I can do. We will actively try to trigger this again by suspend/resume (which I assume is a causative factor), but only on one workstation at the beginnig. Regards -- 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/1785788 Title: NFS breaks after wake from suspend Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am observing all symptoms of debian bug 898060 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898060) on ubuntu bionic 4.15.0-23-generic x86_64 clients with a Centos7 NFS server (3.10.0-693.21.1.el7.x86_64). After a wake from suspend the server always logs kernel: NFSD: client 2001:638:redacted testing state ID with incorrect client ID which is not observed with ubuntu 16.04 (kernel 4.4) clients. Sporadically after wake from suspend (takes days to weeks to trigger) the server logs are flooded with messages of the type kernel: RPC request reserved 84 but used 276 and NFS on the client does not work any more. This also has not been observed with our 20 or so ubuntu 16.04 NFS clients in the last two years. Rebooting the client appears to stop the log flooding on the server and NFS works normally after the reboot. Remark: systemd hangs during shutdown, presumably waiting for the NFS mount to stop, the power button is the only remaining option. I will upgrade to the latest bionic kernel later and try to trigger this again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785788/+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
