NFS oops

[Ray Cole]

NFS errors appearing in dmesg. Mounted to Seagate BlackArmor NAS using firmware 1000.1321.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-37-generic 3.13.0-37.64
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Fri Dec 12 11:49:20 2014
HibernationDevice: RESUME=UUID=b170f305-49ff-4e37-b417-1a977a8dc002
InstallationDate: Installed on 2014-06-06 (189 days ago)
InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530
IwConfig:
 vboxnet0 no wireless extensions.

 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=UUID=5d075486-6b9e-44d6-b28c-3fa1ec2ad88a ro crashkernel=384M-2G:64M,2G-:128M quiet splash crashkernel=384M-:128M
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-37-generic N/A
 linux-backports-modules-3.13.0-37-generic N/A
 linux-firmware 1.127.4
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7c
dmi.board.name: GA-MA790GP-UD4H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA790GP-UD4H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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.18 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.18-vivid/

[Ray Cole (the-other-ray-cole)]

I have not seen this happen since updating to 3.13.0-43 so perhaps this was fixed somewhere along the way.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]