← Back to team overview

kernel-packages team mailing list archive

[Bug 1170087] Re: NFS client hangs after some usage


Joshua Kugler as per your :
[    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
[    0.000000] Your BIOS doesn't leave a aperture memory hole
[    0.000000] Please enable the IOMMU option in the BIOS setup
[   12.643794] EDAC amd64: f10_probe_valid_hardware() This machine is running with DDR3 memory. This is not currently supported. DCHR0=0x3f48090d DCHR1=0x3f48090d
[   12.643797] EDAC amd64:    Contact 'amd64_edac' module MAINTAINER to help add support.

Hence, as per http://www.supermicro.com/support/resources/results.aspx an update is available for your BIOS (r3.0b). If during your maintenance window, you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it doesn't, could you please both specify what happened, and just provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see

Thank you for your understanding.

** 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.

  NFS client hangs after some usage

Status in “linux” package in Ubuntu:

Bug description:
  We have an Ubuntu 10.04 machine.  I mounts a directory (statically,
  i.e. a line in /etc/fstab) on an NFS server.

  After some usage, the mount will simply hang. Any attempt to access
  the mount (e.g. ls /somedir) will just hang, and will have to be kill

  Trying to mount another NFS export on the same server, or another
  server, will simply fail (syscall failed). Trying to access the hung
  export from another machine works fine (i.e. the server side works,
  this is a client-side problem).

  This is kernel 2.6.32-45-server.

  What logs would you like? When trying to do this:

  rpcdebug -m nfs -s all

  All I see on an access attempt is:

  Apr 17 10:47:53 brent kernel: [145406.995318] NFS: revalidating (0:15/2)
  Apr 17 10:47:53 brent kernel: [145406.995326] NFS call  getattr

  If I do this:

  rpcdebug - m rpc -s all

  I get waaaaay too much info. :)  This box also serves as an NFS
  server, but when this glitch happens, the NFS server is unaffected.

  We cannot do upstream testing. We tried the latest kernel on another
  machine with the exact same config, and one of our network interfaces
  would not come up.

  BIOS update available at:

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-45-server 2.6.32-45.104
  Regression: No
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.32-45.104-server
  Uname: Linux 2.6.32-45-server x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  Date: Wed Apr 17 12:17:37 2013
  MachineType: Supermicro H8DGU

  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-45-server root=/dev/mapper/vg_root-10.04 ro text console=tty0 console=ttyS0,115200n8
   PATH=(custom, no user)
  SourcePackage: linux
  dmi.bios.date: 10/14/10
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: H8DGU
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd10/14/10:svnSupermicro:pnH8DGU:pvr1234567890:rvnSupermicro:rnH8DGU:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: H8DGU
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to: