Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760290AbYAUM1g (ORCPT ); Mon, 21 Jan 2008 07:27:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759264AbYAUM13 (ORCPT ); Mon, 21 Jan 2008 07:27:29 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:52407 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759251AbYAUM12 (ORCPT ); Mon, 21 Jan 2008 07:27:28 -0500 Subject: Re: Known prob: MAX_LOCK_DEPTH too low? From: Peter Zijlstra To: Linda Walsh Cc: LKML In-Reply-To: <47914FA7.1000807@tlinx.org> References: <47914FA7.1000807@tlinx.org> Content-Type: text/plain Date: Mon, 21 Jan 2008 13:27:28 +0100 Message-Id: <1200918448.6341.5.camel@lappy> Mime-Version: 1.0 X-Mailer: Evolution 2.21.5 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 810 Lines: 21 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? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/