linux-kernel - Re: Freezing of tasks failed after 20.01 seconds in 3.2.0-rc4+ (Linus GIT af968e2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120105072217.7ce7943f@tlielax.poochiereds.net>
Date:	Thu, 5 Jan 2012 07:22:17 -0500
From:	Jeff Layton <jlayton@...hat.com>
To:	Miles Lane <miles.lane@...il.com>
Cc:	Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
	Tejun Heo <tj@...nel.org>,
	Linux PM mailing list <linux-pm@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: Re: Freezing of tasks failed after 20.01 seconds in 3.2.0-rc4+
 (Linus GIT af968e2)

On Thu, 5 Jan 2012 07:11:21 -0500
Miles Lane <miles.lane@...il.com> wrote:

> 
> On Jan 5, 2012, at 6:53 AM, Pavel Machek <pavel@....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@...hat.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/