desktop-packages team mailing list archive

Thread
Date
[Bug 516592] Re: Network manager kills NFS link on going to sleep hanging Gnome etc.

To: desktop-packages@xxxxxxxxxxxxxxxxxxx
From: Oliver Joos <516592@xxxxxxxxxxxxxxxxxx>
Date: Thu, 20 Oct 2011 01:13:53 -0000
Reply-to: Bug 516592 <516592@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
As I wrote on similar bug 792007 I am always able to release the blocking by restarting network-manager. Try:
  sudo service network-manager restart

Please leave a comment here if you know a permanent workaround to
automatically unmount nfs shares BEFORE the network-manager
disconnects.. It seems that scripts in /usr/lib/pm-utils/sleep.d/  get
executed too late.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/516592

Title:
  Network manager kills NFS link on going to sleep hanging Gnome etc.

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager

  When the system is going to sleep Network Manager unloads the network interface even though the home directory is NFS loaded on that interface.
  Obviously there is still more work happening on that directory and so the system hangs on I/O in the case where NFS is mounted with the hard option.
  This prevents power saving and the system is unusable as Network Manager dies with the rest of Gnome all waiting for I/O
  If you log in on one of the TTYs shutting the system down cleanly fails on the kernel hung I/O and so the only way out is to press the reset button.

  here is the syslog output showing network manager stopping the nic just before the kernel says ouch I have no file system to talk to:
  Feb  2 21:33:53 desktop kernel: [19339.921076] CPU0 attaching NULL sched-domain.
  Feb  2 21:33:53 desktop kernel: [19339.921090] CPU1 attaching NULL sched-domain.
  Feb  2 21:33:53 desktop kernel: [19339.961405] CPU0 attaching sched-domain:
  Feb  2 21:33:53 desktop kernel: [19339.961414]  domain 0: span 0-1 level SIBLING
  Feb  2 21:33:53 desktop kernel: [19339.961421]   groups: 0 1
  Feb  2 21:33:53 desktop kernel: [19339.961434] CPU1 attaching sched-domain:
  Feb  2 21:33:53 desktop kernel: [19339.961439]  domain 0: span 0-1 level SIBLING
  Feb  2 21:33:53 desktop kernel: [19339.961445]   groups: 1 0
  Feb  2 21:33:53 desktop anacron[2176]: Normal exit (0 jobs run)
  Feb  2 21:33:54 desktop NetworkManager: <info>  Sleeping...
  Feb  2 21:33:54 desktop NetworkManager: <info>  (eth0): now unmanaged
  Feb  2 21:33:54 desktop NetworkManager: <info>  (eth0): device state change: 8 -> 1 (reason 37)
  Feb  2 21:33:54 desktop NetworkManager: <info>  (eth0): deactivating device (reason: 37).
  Feb  2 21:33:54 desktop NetworkManager: <info>  (eth0): canceled DHCP transaction, dhcp client pid 839
  Feb  2 21:33:54 desktop NetworkManager: <WARN>  check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess#012
  Feb  2 21:33:54 desktop NetworkManager: <info>  (eth0): cleaning up...
  Feb  2 21:33:54 desktop NetworkManager: <info>  (eth0): taking down device.
  Feb  2 21:33:54 desktop NetworkManager: <info>  (wlan0): now unmanaged
  Feb  2 21:33:54 desktop NetworkManager: <info>  (wlan0): device state change: 3 -> 1 (reason 37)
  Feb  2 21:33:54 desktop NetworkManager: <info>  (wlan0): cleaning up...
  Feb  2 21:33:54 desktop NetworkManager: <info>  (wlan0): taking down device.
  Feb  2 21:33:55 desktop NetworkManager: <info>  (eth0): carrier now OFF (device state 1)
  Feb  2 21:36:55 desktop kernel: [19521.570035] nfs: server nfs.office.local not responding, still trying
  Feb  2 21:36:56 desktop kernel: [19522.710031] nfs: server nfs.office.local not responding, still trying
  Feb  2 21:37:03 desktop kernel: [19529.660034] nfs: server nfs.office.local not responding, still trying
  Feb  2 21:37:17 desktop kernel: [19543.690033] nfs: server nfs.office.local not responding, still trying
  Feb  2 21:37:26 desktop kernel: [19552.670037] nfs: server nfs.office.local not responding, still trying
  Feb  2 21:37:27 desktop kernel: [19553.670029] nfs: server nfs.office.local not responding, still trying
  Feb  2 21:37:29 desktop kernel: [19555.660034] nfs: server nfs.office.local not responding, still trying
  Feb  2 21:37:33 desktop kernel: [19559.470051] nfs: server nfs.office.local not responding, still trying
  Feb  2 21:37:34 desktop kernel: [19560.950099] INFO: task sync:2239 blocked for more than 120 seconds.
  Feb  2 21:37:34 desktop kernel: [19560.950184] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Feb  2 21:37:34 desktop kernel: [19560.950267] sync          D 00000000ffffffff     0  2239   2104 0x00000000
  Feb  2 21:37:34 desktop kernel: [19560.950279]  ffff8800228d1c58 0000000000000086 ffff880001a23880 0000000000015880
  Feb  2 21:37:34 desktop kernel: [19560.950290]  ffff880010115e70 0000000000015880 0000000000015880 0000000000015880
  Feb  2 21:37:34 desktop kernel: [19560.950299]  0000000000015880 ffff880010115e70 0000000000015880 0000000000015880
  Feb  2 21:37:34 desktop kernel: [19560.950309] Call Trace:
  Feb  2 21:37:34 desktop kernel: [19560.950328]  [<ffffffff810da7f0>] ? sync_page+0x0/0x50
  Feb  2 21:37:34 desktop kernel: [19560.950338]  [<ffffffff81527c98>] io_schedule+0x28/0x40
  Feb  2 21:37:34 desktop kernel: [19560.950346]  [<ffffffff810da82d>] sync_page+0x3d/0x50
  Feb  2 21:37:34 desktop kernel: [19560.950354]  [<ffffffff815283c7>] __wait_on_bit+0x57/0x80
  Feb  2 21:37:34 desktop kernel: [19560.950363]  [<ffffffff810da99e>] wait_on_page_bit+0x6e/0x80
  Feb  2 21:37:34 desktop kernel: [19560.950373]  [<ffffffff81078b60>] ? wake_bit_function+0x0/0x40
  Feb  2 21:37:34 desktop kernel: [19560.950383]  [<ffffffff810e4d20>] ? pagevec_lookup_tag+0x20/0x30
  Feb  2 21:37:34 desktop kernel: [19560.950391]  [<ffffffff810dae45>] wait_on_page_writeback_range+0xf5/0x190
  Feb  2 21:37:34 desktop kernel: [19560.950401]  [<ffffffff810e4d20>] ? pagevec_lookup_tag+0x20/0x30
  Feb  2 21:37:34 desktop kernel: [19560.950411]  [<ffffffff81012bae>] ? apic_timer_interrupt+0xe/0x20
  Feb  2 21:37:34 desktop kernel: [19560.950421]  [<ffffffff811357a6>] ? generic_forget_inode+0x1b6/0x240
  Feb  2 21:37:34 desktop kernel: [19560.950429]  [<ffffffff810daf07>] filemap_fdatawait+0x27/0x30
  Feb  2 21:37:34 desktop kernel: [19560.950439]  [<ffffffff8113fb56>] generic_sync_sb_inodes+0x366/0x530
  Feb  2 21:37:34 desktop kernel: [19560.950449]  [<ffffffff8116f896>] ? vfs_quota_sync+0x186/0x200
  Feb  2 21:37:34 desktop kernel: [19560.950457]  [<ffffffff810e39f8>] ? do_writepages+0x28/0x50
  Feb  2 21:37:34 desktop kernel: [19560.950466]  [<ffffffff8113fdbe>] sync_inodes_sb+0x9e/0xb0
  Feb  2 21:37:34 desktop kernel: [19560.950475]  [<ffffffff81143b90>] __sync_filesystem+0x30/0x70
  Feb  2 21:37:34 desktop kernel: [19560.950483]  [<ffffffff81143c97>] sync_filesystems+0xc7/0x120
  Feb  2 21:37:34 desktop kernel: [19560.950492]  [<ffffffff81143d4c>] sys_sync+0x1c/0x40
  Feb  2 21:37:34 desktop kernel: [19560.950500]  [<ffffffff81012002>] system_call_fastpath+0x16/0x1b

  ProblemType: Bug
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Wed Feb  3 15:23:26 2010
  DistroRelease: Ubuntu 9.10
  Gconf:
   
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IpRoute:
   10.10.10.0/24 dev eth0  proto kernel  scope link  src 10.10.10.124  metric 1 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   default via 10.10.10.2 dev eth0  proto static
  NonfreeKernelModules: nvidia
  Package: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: network-manager
  Uname: Linux 2.6.31-17-generic x86_64
  WpaSupplicantLog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/516592/+subscriptions