From: Jeff Layton <jlayton@redhat.com>
To: Miles Lane <miles.lane@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Tejun Heo <tj@kernel.org>,
Linux PM mailing list <linux-pm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: Freezing of tasks failed after 20.01 seconds in 3.2.0-rc4+ (Linus GIT af968e2)
Date: Thu, 5 Jan 2012 07:22:17 -0500 [thread overview]
Message-ID: <20120105072217.7ce7943f@tlielax.poochiereds.net> (raw)
In-Reply-To: <3BA6B994-29A1-44E6-AF10-C9331F3BB521@gmail.com>
On Thu, 5 Jan 2012 07:11:21 -0500
Miles Lane <miles.lane@gmail.com> wrote:
>
> On Jan 5, 2012, at 6:53 AM, Pavel Machek <pavel@ucw.cz> wrote:
>
> > Hi!
> >>>
> >>> Miles Lane (in CC) hit freezing failures in 3.2.0-rc4+ (Linus GIT af968e2)
> >>> while trying to suspend the machine.
> >>
> >> Well, ext3 seems to be involved. I don't see any problems with suspending
> >> those kernels on my test machines, but I don't use ext3 on them any more.
> >>
> >> It would be good to rule out ext3 somehow.
> >
> > I still use ext3 here, and suspend works in recent kernels.
> >
> > Is it reproducible for Miles?
>
> It was a one time event, sorry.
>
> All the best.
>From looking at the stack traces, it really just looks like the ext3
code was waiting for requests to come back from the underlying storage.
I don't know ext3 that well, but could something have offlined the
storage while these tasks were waiting for their requests to come back?
Another hypothesis...could those requests require kthreads that got
frozen while processing these requests?
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2012-01-05 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHFgRy_AdA7iKzCwNvXiE3pR1dqdkuKPgT0soWjw8E_TcLjJtA@mail.gmail.com>
2011-12-28 5:58 ` Freezing of tasks failed after 20.01 seconds in 3.2.0-rc4+ (Linus GIT af968e2) Srivatsa S. Bhat
2011-12-28 22:03 ` Rafael J. Wysocki
2012-01-03 14:47 ` Jan Kara
2012-01-05 11:53 ` Pavel Machek
2012-01-05 12:11 ` Miles Lane
2012-01-05 12:22 ` Jeff Layton [this message]
2012-01-05 16:37 ` Miles Lane
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=20120105072217.7ce7943f@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tj@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).