Slackware64 13.1 blocked when suspending because of NFS

irmin · 01-30-2011, 05:53 AM

Hi,

at home I use a computer running OpenSuse 10.2 to serve as an NFS server. I can mount the relevant nfs shares from my laptop running Slackware64 13.1, but there is an issue related to suspending the laptop to RAM:

If the laptop is suspended to RAM (or disk) while it is connected to the network everything works fine. But if the network connection is cut before the suspend, it seems that the suspend scripts from slackware or the kernel or whatever blocks the whole system, so that suspend "never" happens. (Ok, it will actually work, but only after several minutes, resume will work fine anyway).

Is there a way to "normally" suspend the laptop to RAM even with active NFS mounts and a cut network connection?

Thank you.

Tinkster · 01-30-2011, 10:56 PM

Quote:

Originally Posted by irmin

Hi,

at home I use a computer running OpenSuse 10.2 to serve as an NFS server. I can mount the relevant nfs shares from my laptop running Slackware64 13.1, but there is an issue related to suspending the laptop to RAM:

If the laptop is suspended to RAM (or disk) while it is connected to the network everything works fine. But if the network connection is cut before the suspend, it seems that the suspend scripts from slackware or the kernel or whatever blocks the whole system, so that suspend "never" happens. (Ok, it will actually work, but only after several minutes, resume will work fine anyway).

Is there a way to "normally" suspend the laptop to RAM even with active NFS mounts and a cut network connection?

Thank you.

Don't disconnect before suspend? What you're experiencing is the TCP/IP timeout. You
could reduce the time from the 3 minute default to something more friendly; but ideally
you just don't disconnect before suspend.

Cheers,
Tink