From: Andi Kleen <andi@firstfloor.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Greg Donald" <gdonald@gmail.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: INFO: task reiserfs/0:1322 blocked for more than 120 seconds
Date: Wed, 20 Aug 2008 11:59:32 +0200 [thread overview]
Message-ID: <87ej4kypkr.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080819235258.fa775505.akpm@linux-foundation.org> (Andrew Morton's message of "Tue, 19 Aug 2008 23:52:58 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
>
> Seems that about 100% of the reports we get of this warning triggering
> are sys_sync, transaction commit, etc.
And NFS -- i just had the kernel log on one of my nfsroot test systems
flooded recently with them when the ethernet cable was disconnected
for some time and nfs blocked. Scared me first, but then after
analysis didn't seem very useful. I imagine it would scare normal
users far more.
-Andi
prev parent reply other threads:[~2008-08-20 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-17 4:36 INFO: task reiserfs/0:1322 blocked for more than 120 seconds Greg Donald
2008-08-20 6:52 ` Andrew Morton
2008-08-20 9:19 ` Ingo Molnar
2008-08-20 10:00 ` Andi Kleen
2008-08-20 9:59 ` Andi Kleen [this message]
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=87ej4kypkr.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=gdonald@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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