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. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
