On 01/06/11 06:31, Hugh Dickins wrote:> Brad, my suspicion is that in each case the top 16 bits of RDX have been> mysteriously corrupted from ffff to 0000, causing the general protection> faults. I don't understand what that has to do with KSM.>> But it's only a suspicion, because I can't make sense of the "Code:"> lines in your traces, they have more than the expected 64 bytes, and> only one of them has a ">" (with no"<") to mark faulting instruction.>> I did try compiling the 2.6.39 kernel from your config, but of course> we have different compilers, so although I got close, it wasn't exact.>> Would you mind mailing me privately (it's about 73MB) the "objdump -trd"> output for your original vmlinux (with KSM on)? (Those -trd options are> the ones I'm used to typing, I bet not they're not all relevant.)>> Of course, it's only a tiny fraction of that output that I need,> might be better to cut it down to remove_rmap_item_from_tree and> dup_fd and ksm_scan_thread, if you have the time to do so.

Would you believe about 20 seconds after I pressed send the kernel oopsed.