Re: Kernel BUG at mm/rmap.c:487

[Hugh Dickins]

On Thu, 10 Nov 2005, Alistair John Strachan wrote:
> Hi Hugh,
> 
> I was searching the list today for the subject line and found a response you 
> had written to Sandro Tosi on the 5th of this month.
> 
> I've had a similar oops on 2.6.14, my memory is checked and is okay, however I 
> cannot say reliably whether it is a kernel bug because I had the proprietary 
> NVIDIA driver loaded at the time, which I'm aware is a taboo on this list.

Thanks for the info.  Don't worry about the taboo.  But yes, it is
conceivable that the nVidia driver interferes in some way here,
and we simply don't know how advise on that.

> My system is entirely different from the reporter's, I'm running an x86-64 
> kernel, non-SMP but with PREEMPT. I've reported this to linux-bugs@xxxxxxxxxx 
> who told me simply that "preempt kernels have known stability issues". Having 
> recompiled without preempt, I have not yet encountered the problem, but since 
> it's so rare it's impossible to reproduce anyway.

Good, yes, do follow their advice.  But I hope they'll be doing
something to solve whatever their problems are with PREEMPT.

> Here's the oops (though it's from a tainted kernel, so I don't expect you to 
> even look at it ;-)).
> 
> I'm going to run with the patch you posted for a few weeks to see if it 
> happens again (just to tempt fate, I'll keep preempt enabled).

Okay, even better, please do tempt fate if you're willing, and let me
know if you get any "Bad rmap" or "Bad page state" messages (the more
the better from my point of view).  Though of course the nVidia means
it's not very likely that I'll be able to deduce much from the info.

Thanks,
Hugh
-
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/