kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

-- 
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/1423472

Title:
  Logs flooded with "nfs4_schedule_state_manager: kthread_run: -12"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  An NFSv4 client running kernel 3.13.0-44-generic #73-Ubuntu (amd64) suddenly started spewing
     nfs4_schedule_state_manager: kthread_run: -12
  log messages at an average rate of 2.65 kHz. It did not stop until I rebooted it.

  At the very least that message needs to be rate-limited. (Doesn't seem
  to be fixed upstream yet.)

  As for the underlying problem, -12 is -ENOMEM. I'm afraid I have no
  idea why the kernel ran out of memory at that point. WIll follow up if
  the problem ever recurs. This bug report is mainly about the lack of
  rate limiting.

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