I suspect that your earlier oopses left something in a stale state - this
is the same machine that you've reported others oopses for, no?
> Is there some way to figure out if this page is special in some way or
> track down how it broke?
It looks like it's a bog-standard page, that was just free'd (probably
because of page->count corruption) while it was still in the page cache.
Now, how that page->count corruption actually happened, I have no idea,
which is why I suspect you had other earlier oopses that left the machine
in an inconsistent state.
There _is_ a known race in 2.4.15pre1, where we simply test a condition
that isn't true any more and that can cause spurious oopses (not this one,
though) under the right circumstances. Such an oops might have left
something in the VM in a half-way state...
Can you reproduce this on pre6, for example? And if so, what's the load?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/