lkml.org 
[lkml]   [2008]   [Jan]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Known prob: MAX_LOCK_DEPTH too low?
From
Date

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.




\
 
 \ /
  Last update: 2008-01-21 18:17    [W:0.071 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site