On Thu, Jan 5, 2012 at 7:22 AM, Jeff Layton <jlayton@xxxxxxxxxx> wrote:
> On Thu, 5 Jan 2012 07:11:21 -0500
> Miles Lane <miles.lane@xxxxxxxxx> wrote:
>
>>
>> On Jan 5, 2012, at 6:53 AM, Pavel Machek <pavel@xxxxxx> 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?
FWIW, I only hit this one time.
Miles
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
