** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
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/1691899
Title:
regression: the 4.8 hwe kernel does
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
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
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
@arges - fyi the 20 nodes running
3.16.0-031600-generic #201408031935
have not encountered this problem in the ~2 weeks since install reboot.
@matt-jarvis - thx for the verification, i was out-of-office most of
this week.
i just took the 20 nodes that had been running
3.13.0-38.65-generic
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”
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.
Matt - i am using the following (takes advantage of the ipmi_si module's hot
add and remove):
KIPMI_INST=0 # the web suggests this should increment but i've always seen 0
IPMI_PARAMS=$(cat /proc/ipmi/${KIPMI_INST}/params)
sudo sh -c echo remove,${IPMI_PARAMS}
@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
@chris - i have 10 nodes that i just installed w/3.16.0-031600-generic
#201408031935
i will increase that number tomorrow and update thisbug report if i see
ipmi hangs on these hosts.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
agreed. thank you for providing the test 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/1383921
Title:
kipmi0 process hangs with ipmitool
Status in “linux” package in Ubuntu:
the reboot was delayed but 7 of the 8 remaining hosts are now running the
3.13.0-38.65-generic #lp1383921
kernel. i have not yet seen a recurrence of the ipmi hang on any hosts running
this version.
--
You received this bug notification because you are a member of Kernel
Packages, which is
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: [
** 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
the hot-add/hot-remove workaround was performed on a mishmash of hosts
where this has crept up. the majority were precise hosts w/a 3.5.0 hwe
kernel. one was trusty w/3.13.0-37-generic and the remainder are
running locally built kernels from linux-source 3.13.0-35.62 w/the patch
from lp#1368991
i've installed and rebooted 16 of the 14.04 hosts so that they are now
running w/the 3.13.0-38.65-generic #lp1383921 kernel. i'll update the
ticket if i see the symptoms recur on this set.
the remaining 8 can't be rebooted until early next week.
thanks!
--
You received this bug notification
the workaround red hat suggests (forcing a hot-add/hot-remove cycle of
the IPMI interface) appears to work. the same page claims the issue was
resolved w/kernel-2.6.32-504.el6 from Errata RHSA-2014-1392 (released
2014-10-14). however, i'm unable to pinpoint the resolution in the
release or
Public bug reported:
we're in the process of migrating from 12.04 to 14.04 and are noticing a
problem apparently related to the kernel and ipmi. after an
indeterminate period of regular ipmi queries (e.g., nagios checks using
ipmitool) the kipmi0 process pegs a cpu to ~100% usage and further
the kernel from linux-image-3.13.0-37-generic does indeed eliminate that
error. thank you!
tag updated to: verification-done-trusty
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Public bug reported:
hello -
we had a freshly installed 14.04.1 server run into disk access issues
after swapping out a hard drive. on further investigation, whenever a
drive is pulled (on both the mptsas and mpt2sas systems i can test) the
included warning is logged.
the message is
20 matches
Mail list logo
