From: Soeren Sonnenburg <kernel@nn7.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-fsdevel@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.22.6: kernel BUG at fs/locks.c:171
Date: Fri, 14 Sep 2007 08:02:34 +0200 [thread overview]
Message-ID: <1189749754.25045.10.camel@localhost> (raw)
In-Reply-To: <200709130951.48194.nickpiggin@yahoo.com.au>
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.
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).
However this machine used to have uptimes of months before the dvb card
was in there and the kernel version upgrade (don't know which version
that was...).
Anyway I am not sure if this is reproducible, but I will keep memtest
running today and then proceed as you said...
Thanks,
Soeren
--
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
next prev parent reply other threads:[~2007-09-14 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1189675222.5352.10.camel@localhost>
2007-09-12 23:51 ` 2.6.22.6: kernel BUG at fs/locks.c:171 Nick Piggin
2007-09-14 6:02 ` Soeren Sonnenburg [this message]
2007-09-13 21:22 ` Nick Piggin
2007-09-15 9:47 ` Soeren Sonnenburg
2007-09-15 10:22 ` Soeren Sonnenburg
2007-09-16 8:15 ` Nick Piggin
2007-09-17 13:43 ` Soeren Sonnenburg
2007-09-24 20:21 ` Soeren Sonnenburg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1189749754.25045.10.camel@localhost \
--to=kernel@nn7.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).