From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Linda Walsh <lkml@tlinx.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux-Xfs <linux-xfs@oss.sgi.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Known prob: MAX_LOCK_DEPTH too low?
Date: Mon, 21 Jan 2008 18:13:49 +0100 [thread overview]
Message-ID: <1200935629.6341.9.camel@lappy> (raw)
In-Reply-To: <4794C7C0.8030207@tlinx.org>
On Mon, 2008-01-21 at 08:26 -0800, Linda Walsh wrote:
> Peter Zijlstra wrote:
> > On Fri, 2008-01-18 at 17:17 -0800, Linda Walsh wrote:
> >
> >> On my x86_64 machine, I got the following message
> >> in log (kern = 2.6.23.14)
> >>
> >> Jan 16 04:08:38 Astara kernel: BUG: MAX_LOCK_DEPTH too low!
> >> Jan 16 04:08:38 Astara kernel: turning off the locking correctness
> >> validator.
> >>
> >> Have no idea what caused it as I found the message on my console
> >> somewhat after the fact. The system had been up over 24 hours and
> >> is still running. System still seems 'fine' (been up 3 days now),
> >> so you can treat this as a "data point".
> >>
> >
> > Are you perhaps an XFS user?
> >
> >
> ----
> Funny you should mention that... yes. However, there were no
> other messages that seem to indicate that the message had anything
> to do with XFS. Nice shot in the dark.
:-), know issue, I guess I'll up the MAX_LOCK_DEPTH for the next
release. I looked at dynamically allocating that stuff, but that gets
awfully painful.
prev parent reply other threads:[~2008-01-21 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 1:17 Known prob: MAX_LOCK_DEPTH too low? Linda Walsh
2008-01-21 12:27 ` Peter Zijlstra
2008-01-21 16:26 ` Linda Walsh
2008-01-21 17:13 ` Peter Zijlstra [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=1200935629.6341.9.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lkml@tlinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.