[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0705231045370.3673-100000@iolanthe.rowland.org>
Date: Wed, 23 May 2007 10:47:04 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Andrew Morton <akpm@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
cc: Pavel Machek <pavel@....cz>,
USB development list <linux-usb-devel@...ts.sourceforge.net>,
Oleg Nesterov <oleg@...sign.ru>,
Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.22-rc2-mm1
On Wed, 23 May 2007, Rafael J. Wysocki wrote:
> On Wednesday, 23 May 2007 09:48, Andrew Morton wrote:
> > On Wed, 23 May 2007 00:42:33 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc2/2.6.22-rc2-mm1/
> >
> > This is intermittently getting resume-from-RAM failures. It is not
> > sufficiently repeatable to be able to bisect.
> >
> > [ 1381.119362] PM: Preparing system for mem sleep
> > [ 2331.798452] Stopping tasks ...
> > [ 2351.760431] Stopping kernel threads timed out after 20 seconds (2 tasks refusing to freeze):
> > [ 2351.762385] ksuspend_usbd
> > [ 2351.764374] khubd
> > [ 2351.766338] Restarting tasks ... done.
>
> Hmm, that seems to be related to usb-fix-suspend-to-ram.patch (probably one of
> the threads is waiting for a completion by some other thread that has been
> frozen already).
Is it possible to get an Alt-SysRq-T stack trace during those 20
seconds? Knowing what those threads are waiting for would be a big
help.
Alan Stern
-
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/
Powered by blists - more mailing lists