Re: 2.6.22.6: kernel BUG at fs/locks.c:171

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).


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

OK. Don't put too much effort into memtest if it hasn't caught anything
by now -- it's really only exercising your CPU and memory, so even if it
is your video hardware, it probably won't find the problem.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Patch to fixe Data Acess error in dup_fd
    ... are a few slab corruption issues but not while running memtest and no ... could as well be a memory corruption issue. ... I had observed random slab corruption issues in the machine, ... to point at any particular part of the kernel, ...
    (Linux-Kernel)
  • Re: Patch to fixe Data Acess error in dup_fd
    ... could as well be a memory corruption issue. ... I had observed random slab corruption issues in the machine, ... Haven't run memtest will run and check if the problem gets recreated. ... to point at any particular part of the kernel, ...
    (Linux-Kernel)
  • Re: Opinions on new Fedora Core 2 install with LVM 2 and snapshots?
    ... There are some corruption issues with 3ware 9500's on Opteron boards. ... XFS is in the mainline kernel, and available in the Fedora 2.6 kernels. ... It seems that many of the "ext3 filesystem is corrupt" reports on ...
    (Fedora)
  • large file corruption (x86_64, ext3) under 2.6.17 kernels?
    ... where backups were written to two 300G Maxtor SATA ... The file corruption problem seem to occur on large files, ... images saved on the hard drives) to see if the problem has been ... This leaves mainly only the kernel and/or the ext3 ...
    (Linux-Kernel)
  • Re: kernel 2.6 and memtester
    ... I compiled a new kernel without APIC/IOAPIC ... Unable to malloc 4293918720 bytes. ... I found 3 bad blocks in the swap space. ... the memtest in a custom 2.6.5 kernel looks like ...
    (Debian-User)