From mboxrd@z Thu Jan  1 00:00:00 1970
From: Soeren Sonnenburg <kernel@nn7.de>
Subject: Re: 2.6.22.6: kernel BUG at fs/locks.c:171
Date: Mon, 24 Sep 2007 22:21:38 +0200
Message-ID: <1190665298.4408.9.camel@localhost>
References: <1189675222.5352.10.camel@localhost>
	 <200709130951.48194.nickpiggin@yahoo.com.au>
	 <1189749754.25045.10.camel@localhost>
	 <200709140722.58046.nickpiggin@yahoo.com.au>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Cc: linux-fsdevel@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from nn7.de ([85.214.94.156]:35306 "EHLO nn7.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1756535AbXIXUVm (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Mon, 24 Sep 2007 16:21:42 -0400
In-Reply-To: <200709140722.58046.nickpiggin@yahoo.com.au>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org


On Fri, 2007-09-14 at 07:22 +1000, Nick Piggin wrote:
> On Friday 14 September 2007 16:02, Soeren Sonnenburg wrote:
> > On Thu, 2007-09-13 at 09:51 +1000, Nick Piggin wrote:
> > > On Thursday 13 September 2007 19:20, Soeren Sonnenburg wrote:
> > > > Dear all,
> > > >
> > > > I've just seen this in dmesg on a AMD K7 / kernel 2.6.22.6 machine
> > > > (config attached).
> > > >
> > > > Any ideas / which further information needed ?
> > >
> > > Thanks for the report. Is it reproduceable? It seems like the
> > > locks_free_lock call that's oopsing is coming from __posix_lock_file.
> > > The actual function looks fine, but the lock being freed could have
> > > been corrupted if there was slab corruption, or a hardware corruption.
> > >
> > > You could: try running memtest86+ overnight. And try the following
> > > patch and turn on slab debugging then try to reproduce the problem.
> >
> > OK so far I've run memtest86+ 1.40 from freedos for 8 hrs (v1.70 hung on
> > startup) - nothing.
> 
> Thanks.
> 
> > Could this corruption be caused by a pci card/driver? I am asking as I
> > am using a new dvb-t card (asus p7131) and the oops happened after 5 or
> > 6 days of uptime just about a day after watching some movie (very bad
> > reception/lots of errors).
> 
> It could be caused by that, definitely. slab debugging plus my earlier
> patch may help to narrow it down. (or stress testing with / without the
> dvb card in action).

OK, it is the dvb card. I have 1 week of uptime now without any errors.
Only change is the dvb driver (saa7146) not loaded.

:(
Soeren