[Top] [All Lists]

Re: -mm: xfs lockdep warning

To: Tejun Heo <tj@xxxxxxxxxx>
Subject: Re: -mm: xfs lockdep warning
From: Torsten Kaiser <just.for.lkml@xxxxxxxxxxxxxx>
Date: Tue, 5 Oct 2010 20:09:58 +0200
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Yang Ruirui <ruirui.r.yang@xxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Alex Elder <aelder@xxxxxxx>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=rhPNnOHaczzwzZSAJXJCD4FvRX4P2yrS0Ew3yeVK1F0=; b=cJR4zw1rTetEw2KOQEPj0JDj4aQ60z9GT+YgDPtAcENFabO+bYMtJfv+rMyhK7X3V4 Qcol8a1OlF4oF3bIzOZl4PCrV7JdESGqRChsP93YUeTpS+5z/Mk4b0V7l8z6mx3JaXQG H+bDGidQVo7Oio0lCh6gKI9SJTUxfxB7ms4EM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ZBBXxKBzat+pE1A4vm7kjGnT7UYRTR6/cVhBQhkTSBr7sTe6gxbblhbQ8AzcUBpXFM QZ6NV6GZnYgWIZijA7dQxp5pGxaA0MQa1u12NPUcsRbASEitSduVEg8PXft4q1kfi2PM PF9I3Z9Ja8c0OBr8XIgra297q+8sZc/VCefqo=
In-reply-to: <4CAB5874.9060106@xxxxxxxxxx>
References: <201009161546.16909.ruirui.r.yang@xxxxxxxxx> <20100917005227.GJ24409@dastard> <20100920191355.GA28443@xxxxxxxxxxxxx> <AANLkTi=45J+=ytj=NC4bYTVJFRakNQQiFd35K7mrf+Gq@xxxxxxxxxxxxxx> <4CA997DF.5030008@xxxxxxxxxx> <20101004092107.GJ4681@dastard> <AANLkTi=3jjoCtYoK0endt8OM=omygO284WN2ZQZ=jceo@xxxxxxxxxxxxxx> <4CAB5779.5020901@xxxxxxxxxx> <4CAB5874.9060106@xxxxxxxxxx>
On Tue, Oct 5, 2010 at 6:55 PM, Tejun Heo <tj@xxxxxxxxxx> wrote:
> On 10/05/2010 06:51 PM, Tejun Heo wrote:
>> On 10/05/2010 12:09 PM, Torsten Kaiser wrote:
>>> 2) the hang with 2.6.35-rc5 I have seen twice (triggered probably by
>>> high load while building KOffice on an tmpfs)
>> The trace doesn't seem to firmly point at xfs locking up.  There are
>> md and dm crypt involved.  Are you sure this is locking up inside xfs?
>> Also, can you please enable frame pointers so that we can get more
>> reliable backtrace?
>>> 3) the lockdep issue that started this thread and that I am seeing in
>>> mainline 2.6.36-rc5 and -rc6 and that seems to be rather easy to
>>> trigger for me.
>>> Because 3) is regarded as a false positive, it should not be the cause
>>> of 2)
>> For now, let's not draw any conclusion or mix the issues.  I'll look
>> up the original thread and look into what the lockdep warning means.
> Ah, okay, David already looked into it and concluded it to be a
> spurious one.  Can you please attach full kernel message of the
> lockup?

Here is the complete log from bootup until the hang happened the second time.
I just logged into KDE and then started the upgrade of KOffice, which
meant that the package manager started to compile 4 programs each with
-j5. After a few minutes the load got to ~18 and probably at the point
where filecache and GCCs filled up my 4GB RAM the system got stuck.
The mouse so longer moved and SysRq+S did not work. The log was
captured via serial console on a second system.

I will try tomorrow with frame pointers enabled...


Attachment: xfs-lockup.txt
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>