kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

** Tags removed: needs-reverse-bisect
** Tags added: cherry-pick reverse-bisect-done

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

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

Title:
  automount fails on resume after suspend if file open for writing

Status in linux package in Ubuntu:
  Triaged

Bug description:
  For a couple of years I have usually not shut down my pc after using it, I just leave it and let it suspend.
  (Of course I have also shut down the system completely every now and then.)
  This has worked well but recently with new kernels 4.2.0-* I get problems.

  Further investigations show that it is automount that fails when :
  1. a file is opened for writing on a nfs-mounted volume that autofs mounts
  2. autofs unmounts the nfs directory after five minutes of inactivity, AND
  3. the system is automatically suspended after ten minutes of inactivity

  After resuming activity it is impossible to access the volume on the
  server

  To reproduce:
      cat > /path/to/file/on/automounted/nfs-dir/file.txt
      write some text
      wait for the system to suspend

      Activate the system again and try to access the automounted volume

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  seved      2472 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 11 09:35:17 2016
  HibernationDevice: RESUME=UUID=38682e03-657e-46a8-b728-71bb6b19ffd3
  InstallationDate: Installed on 2010-11-12 (1916 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  MachineType: Gigabyte Technology Co., Ltd. G41M-ES2L
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=67935e67-5ba7-4442-8401-b0134d6ca21f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-27-generic N/A
   linux-backports-modules-4.2.0-27-generic  N/A
   linux-firmware                            1.149.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: G41M-ES2L
  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.:bvrF6:bd11/04/2009:svnGigabyteTechnologyCo.,Ltd.:pnG41M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-ES2L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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