From: Eric Sandeen <sandeen@sandeen.net>
To: Linda Walsh <lkml@tlinx.org>
Cc: LKML <linux-kernel@vger.kernel.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Lock debugging noise or real problem?
Date: Mon, 11 Aug 2008 15:10:17 -0500 [thread overview]
Message-ID: <48A09CA9.9080705@sandeen.net> (raw)
In-Reply-To: <48A093A7.40606@tlinx.org>
Linda Walsh wrote:
> This is a trimmed version of my Warn log (with boot indicators) since
> the problems started. I'm also unsure why some user-level processes seem
> to be dumping trace-backs periodically, including:
>
> cifsopslock
> xfs_fsr (a few)
the explanation for xfs_fsr, at least, is the same as the last time you
brought it up ;)
http://lkml.org/lkml/2008/2/12/86
-Eric
next prev parent reply other threads:[~2008-08-11 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 19:31 Lock debugging noise or real problem? Linda Walsh
2008-08-11 20:10 ` Eric Sandeen [this message]
2008-08-12 2:33 ` Linda Walsh
2008-08-12 2:48 ` Eric Sandeen
2008-08-12 3:35 ` Linda Walsh
2008-08-12 22:28 ` XFS " Linda A. Walsh
2008-08-13 0:58 ` Dave Chinner
2008-08-13 22:05 ` Linda Walsh
2008-08-14 0:41 ` Dave Chinner
2008-08-14 1:04 ` Linda Walsh
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=48A09CA9.9080705@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.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