Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757539AbZGJUex (ORCPT ); Fri, 10 Jul 2009 16:34:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755424AbZGJUeo (ORCPT ); Fri, 10 Jul 2009 16:34:44 -0400 Received: from mx2.redhat.com ([66.187.237.31]:55914 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756070AbZGJUen (ORCPT ); Fri, 10 Jul 2009 16:34:43 -0400 Date: Fri, 10 Jul 2009 16:34:33 -0400 From: Dave Jones To: Joao Correia Cc: Peter Zijlstra , LKML , Amerigo Wang Subject: Re: [PATCH 3/3] Increase lockdep limits: MAX_LOCKDEP_CHAINS_BITS Message-ID: <20090710203433.GA11105@redhat.com> Mail-Followup-To: Dave Jones , Joao Correia , Peter Zijlstra , LKML , Amerigo Wang References: <1247078066.16156.15.camel@laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1390 Lines: 35 On Wed, Jul 08, 2009 at 08:33:37PM +0100, Joao Correia wrote: > On Wed, Jul 8, 2009 at 8:32 PM, Joao Correia wrote: > > On Wed, Jul 8, 2009 at 7:34 PM, Peter Zijlstra wrote: > >> On Tue, 2009-07-07 at 16:25 +0100, Joao Correia wrote: > >>> (Applies to current Linus tree, as of 2.6.31-rc2) > >>> > >>> A third limit becomes apparent as being too low after raising > >>> MAX_STACK_TRACE_ENTRIES and MAX_LOCK_DEPTH, although this one is more > >>> elusive to trigger. > >> > >> Would this involve reloading modules a lot? > >> > >> > > > > All the other limits were triggered immediatly upon boot. This one > > happens during regular system usage, after a couple of hours. Not > > loading more modules than needed, the system stays at around 45 > > modules loaded, give or take. I do have qemu running, if that helps > > anything. > > > > Joao Correia > > > > qemu running as a -host-, not the system running inside it. Just to clear it up. Could you upload your /proc/lockdep someplace ? Maybe there's some obvious clues in there like the ones we saw in mine. Dave -- 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/