From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: svaidy@linux.vnet.ibm.com
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Random freezing failure with NFS and automount
Date: Tue, 5 Jul 2011 01:29:01 +0200 [thread overview]
Message-ID: <201107050129.01936.rjw@sisk.pl> (raw)
In-Reply-To: <20110704171449.GC5357@dirshya.in.ibm.com>
On Monday, July 04, 2011, Vaidyanathan Srinivasan wrote:
> * Rafael J. Wysocki <rjw@sisk.pl> [2011-07-03 09:07:18]:
>
> > Hi,
> >
> > On Tuesday, June 28, 2011, Vaidyanathan Srinivasan wrote:
> > > Hi,
> > >
> > > I have random freezing failures on my laptop running 2.6.39 kernel.
> > > The laptop has NFS client and automount. Network could have been
> > > disconnected by the time suspend is attempted, hence nfs client should
> > > fail all operations, just freeze and allow laptop to suspend.
> > >
> > > I need some help to drill deeper at this log and also suggestions on
> > > config options to try and get more information to help me root cause
> > > this issue.
> > >
> > > This happens once in 4-5 suspend/resume cycles, does not succeed on
> > > retry, eventually I have to reboot.
> >
> > This is a tasks freezer failure, ie. the freezing of tasks fails, because
> > one of them refuses to handle signals for 20 s. This is probably related
> > to waiting on a VFS mutex in the TASK_UNINTERRUPTIBLE state.
> >
> > We don't handle those cases nicely right now, sorry about that.
>
> Hi Rafael,
>
> Thanks for taking a look. The NFS mount option in hard,intr so
> I would expect an interruptible sleep. I will take this to file
> system folks and see if they can help. I will also review my mount
> options to improve the situation.
>
> When you said we are not handling the situation, what did you mean?
I meant that the freezing fails in those cases.
> We seem to cleanly unfreeze the tasks and return the system to working
> state (though suspend fails). Maybe we should send some signals and
> try to prod the failing task to get to freeze? What is needed here to
> improve our framework?
Probably there is a bug (or more bugs) in our error code paths. That wouldn't
suprpise me too much, because those code paths are not tested very hard ...
Thanks,
Rafael
prev parent reply other threads:[~2011-07-04 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 15:50 Random freezing failure with NFS and automount Vaidyanathan Srinivasan
2011-07-03 7:07 ` Rafael J. Wysocki
2011-07-04 17:14 ` Vaidyanathan Srinivasan
2011-07-04 23:29 ` Rafael J. Wysocki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201107050129.01936.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-pm@lists.linux-foundation.org \
--cc=svaidy@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox