looks like this made it into 3.13.0-48.80
https://launchpad.net/ubuntu/trusty/+source/linux/+changelog
* LOCKD: Fix a race when initialising nlmsvc_timeout
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427438
Upgraded a few days ago, haven't seen the errors
--
You received this bug
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 l
I'm affected by this bug across 10 production servers, is there a
fix/workaround for trusty, that doesn't involve a manual kernel roll?
--
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/13582
Does anyone know if/when this will make it into the trusty kernel?
--
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 i
Sorry, right. It looks like the patch was just submitted upstream. It
was also cc'd to stable, so it should make it's way into all the stable
kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
doesn't appear to have made it into 3.19-rc3 but beyond that i don't
have any information other than what is in http://www.spinics.net/lists
/linux-nfs/msg48569.html (patch appears to be from and signed off by the
NFS client maintainer)
--
You received this bug notification because you are a memb
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
--
You received this bug notification because you are a member of
still no errors seen. i believe this patch addresses the issue.
--
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
** Tags added: patch
--
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
Bug desc
to apply to the 3.13 trusty kernel source i had to make a trivial edit
to the patch (result attached). the power user/developer whose workflow
typically triggers these messages has been using it and i have not yet
seen the errors recur.
** Patch added: "initialising-nlmsvc_timeout.patch"
https
Looks like there may be a patch
http://www.spinics.net/lists/linux-nfs/msg48575.html
--
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 r
http://www.spinics.net/lists/linux-nfs/index.html#47942
--
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” p
verified that messages persist w/3.18.0-031800rc6-generic #201411231935
and sent email to linux-...@vger.kernel.org
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
@Joseph - rebooted into 3.18.0-031800rc5-generic #201411162035
and the msgs are still being logged:
[ 231.437941] xprt_adjust_timeout: rq_timeout = 0!
[ 231.437945] lockd: server nfs-home not responding, still trying
[ 231.441744] lockd: server nfs-home OK
--
You received this bug notification
@Andrew, the issue with the upstream kernels not booting should be
resolved now.
The v3.18-rc5 kernel is now available. Can you see if it also exhibits
the bug?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc5-vivid/
--
You received this bug notification because you are a member of Kerne
I'm also seeing this issue - currently running:
3.15.4-x86_64-linode45 #1 SMP Mon Jul 7 08:42:36 EDT 2014 x86_64 x86_64
x86_64 GNU/Linux
Nov 14 00:23:05 localhost kernel: xprt_adjust_timeout: rq_timeout = 0!
Nov 14 00:23:05 localhost kernel: lockd: server 192.168.132.120 not responding,
still tr
** 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/1358226
Title:
kernel and lockd xprt_adjust_timeout rq_timeout
Status
hello -
per the above comments, i installed the 3.18.0-031800rc1-generic mainline
kernel on the Ubuntu 14.04.1 LTS vm that we have been seeing log these errors.
the error persists:
Oct 29 22:30:37 vm1 kernel: [ 214.434104] xprt_adjust_timeout: rq_timeout = 0!
Oct 29 22:30:37 vm1 kernel: [ 214
The v3.18-rc1 kernel is now available. Can you see if it also exhibits
the bug?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
I am also experiencing this bug.
This issue did not occur on precise, however it does occur on trusty. I
have not tried non-LTS releases.
I can confirm that the same issue occurs on the current upstream
mainline kernel.
I have reproduced the issue with 3.17.1-031701-generic
** Tags added: kerne
** Tags removed: lockd nfs
--
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:
Incomplet
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.17 kernel[0].
If this bug is fixed in the mainline kernel, please add th
I keep seeing this as well, my use case is a mail server (dovecot). It
always seems to happen for less than a second, the times don't seem
predictable and two 14.04 servers accessing the same share report the
issues and different times, so I'm not sure it's really related to the
remote end.
I am
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => 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/1358226
** Package changed: ubuntu => linux-meta (Ubuntu)
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1358226
Title:
kernel and
26 matches
Mail list logo
