It looks like the fix for this bug is in mainline as of 3.19-rc5:
06bed7d LOCKD: Fix a race when initialising nlmsvc_timeout
git describe --contains 06bed7d
v3.19-rc5~13^2~5
The fix was also cc'd to stable, and it is working it's way through the stable
releases. It has made it's way into the linux-3.13.y-queue branch of the
upstream 3.13 kernel:
1185361 LOCKD: Fix a race when initialising nlmsvc_timeout
Trusty will pick up this fix when it gets the 3.13 upstream updates.
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => Triaged
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Medium
--
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/1358226
Title:
kernel and lockd xprt_adjust_timeout rq_timeout
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Trusty:
Triaged
Bug description:
I am seeing the following messages in syslog. There are no other
messages around that time to suggest why it is happening.
Aug 18 11:01:16 hostname kernel: [943559.414398] xprt_adjust_timeout:
rq_timeout = 0!
Aug 18 11:01:16 hostname kernel: [943559.414401] lockd: server nfs_server not
responding, still trying
Aug 18 11:01:16 hostname kernel: [943559.415347] lockd: server nfs_server OK
System is:
Linux hostname 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 14.04.1 LTS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358226/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
