From: Christoph Hellwig <hch@lst.de>
To: Torsten Kaiser <just.for.lkml@googlemail.com>
Cc: Yang Ruirui <ruirui.r.yang@tieto.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
Christoph Hellwig <hch@infradead.org>,
Alex Elder <aelder@sgi.com>, Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: -mm: xfs lockdep warning
Date: Tue, 5 Oct 2010 14:17:29 -0400 [thread overview]
Message-ID: <20101005181729.GA30877@lst.de> (raw)
In-Reply-To: <AANLkTikzvD6B=8bGp6h2+bjV5BimErqLOgt2Ujsn053C@mail.gmail.com>
On Tue, Oct 05, 2010 at 08:09:58PM +0200, Torsten Kaiser wrote:
> 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..
Lots of hangs in sync_page and dm-crypt in the stack is unfortunately
something we've seen quite a few times, and it usually points to that
layer. In the best case we might just have a similar workqueue priority
issue somewhere in the dm-crypt or maybe just md code.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-05 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 7:46 -mm: xfs lockdep warning Yang Ruirui
2010-09-17 0:52 ` Dave Chinner
2010-09-20 19:13 ` Christoph Hellwig
2010-09-25 13:08 ` Torsten Kaiser
2010-10-04 9:01 ` Tejun Heo
2010-10-04 9:21 ` Dave Chinner
2010-10-05 10:09 ` Torsten Kaiser
2010-10-05 16:51 ` Tejun Heo
2010-10-05 16:55 ` Tejun Heo
2010-10-05 18:09 ` Torsten Kaiser
2010-10-05 18:17 ` Christoph Hellwig [this message]
2010-10-05 17:54 ` Torsten Kaiser
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=20101005181729.GA30877@lst.de \
--to=hch@lst.de \
--cc=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=just.for.lkml@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ruirui.r.yang@tieto.com \
--cc=tj@kernel.org \
--cc=xfs@oss.sgi.com \
/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