Date: Tue, 26 Jan 2010 13:51:35 +0100 (CET)
From: Jiri Kosina <jkosina@suse.cz>
To: Kasper Sandberg <lkml@metanurb.dk>
Cc: Oliver Neukum <oliver@neukum.org>, smurf@smurf.noris.de,
       LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: option driver freezing entire system
In-Reply-To: <1264187509.12168.30.camel@localhost>
Message-ID: <alpine.LRH.2.00.1001261350530.15694@twin.jikos.cz>
References: <1263577116.27788.131.camel@localhost>  <201001151855.46217.oliver@neukum.org>  <1263580615.27788.134.camel@localhost>  <alpine.LRH.2.00.1001181656500.15694@twin.jikos.cz> <1264187509.12168.30.camel@localhost>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1040
Lines: 28

On Fri, 22 Jan 2010, Kasper Sandberg wrote:

> > > > Please recompile your kernel with lockdep. This should improve
> > > > debugging.
> > > 
> > > It is a debian unstable .32 kernel i run now, and grepping for lockdep
> > > reveals:
> > > CONFIG_LOCKDEP_SUPPORT=y
> > > only, is there anything more i should have? (never used lockdep before)
> > 
> > CONFIG_PROVE_LOCKING could be helpful here. (be aware of the fact that 
> > this will make your system noticeably slower).
> 
> Sorry, i was just away a few days. I shall enable this setting tomorow
> and test, though it may take a few days for it to crash.

This option should ideally report the lock ordering violation before the 
actual hang happens (if it is caused by improper locking semantics).

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

--
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/