From: Ben Myers <bpm@sgi.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: Christoph Hellwig <hch@infradead.org>,
gregkh@linuxfoundation.org, stable@vger.kernel.org,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs: blocked task in xfs_buf_lock
Date: Wed, 30 May 2012 17:09:14 -0500 [thread overview]
Message-ID: <20120530220914.GF4721@sgi.com> (raw)
In-Reply-To: <4FC272D0.4090101@profihost.ag>
Stefan,
On Sun, May 27, 2012 at 08:30:40PM +0200, Stefan Priebe wrote:
> nobody who has an idea? Or what to check?
I think we need more information to get anywhere. Maybe 'echo t >
/proc/sysrq-trigger' is a good place to start?
Regards,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-30 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 11:14 xfs: blocked task in xfs_buf_lock Stefan Priebe - Profihost AG
2012-05-27 18:30 ` Stefan Priebe
2012-05-30 22:09 ` Ben Myers [this message]
[not found] <000201d2c548$68fc5450$3af4fcf0$@alibaba-inc.com>
2017-05-08 13:40 ` Brian Foster
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=20120530220914.GF4721@sgi.com \
--to=bpm@sgi.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=s.priebe@profihost.ag \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).