linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <lists2009@fnarfbargle.com>
To: Hugh Dickins <hughd@google.com>
Cc: Borislav Petkov <bp@alien8.de>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	linux-mm <linux-mm@kvack.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Izik Eidus <ieidus@redhat.com>
Subject: Re: KVM induced panic on 2.6.38[2367] & 2.6.39
Date: Wed, 01 Jun 2011 08:18:06 +0800	[thread overview]
Message-ID: <4DE5853E.8040106@fnarfbargle.com> (raw)
In-Reply-To: <alpine.LSU.2.00.1105311517480.21107@sister.anvils>

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.

No, nor do I. The panic I reproduced with KSM off was in a completely 
unrelated code path. To be honest I would not be surprised if it turns 
out I have dodgy RAM, although it has passed multiple memtests and I've 
tried clocking it down. Just a gut feeling.

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

Yeah, with hindsight I must have removed them when I re-formatted the 
code from the oops. Each byte was one line in the syslog so there was a 
lot of deleting to get it to a postable format.

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

Ok, so since my initial posting I've figured out how to get a clean oops 
out of netconsole, so tonight (after 9PM GMT+8) I'll reproduce the oops 
a couple of times. What about I upload the oops, plus the vmlinux, plus 
.config and System.map to a server with a fat pipe and give you a link 
to it?

At least I can reproduce it quickly and easily.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-06-01  0:18 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DE44333.9000903@fnarfbargle.com>
2011-05-31  5:47 ` Borislav Petkov
2011-05-31  9:26   ` Brad Campbell
2011-05-31 10:38     ` Borislav Petkov
2011-05-31 14:24       ` Brad Campbell
2011-05-31 22:31         ` Hugh Dickins
2011-06-01  0:18           ` Brad Campbell [this message]
2011-06-01  0:37           ` Brad Campbell
2011-06-01  1:15             ` Andrea Arcangeli
2011-06-01  2:03               ` Brad Campbell
2011-06-01  4:52               ` Hugh Dickins
2011-06-01  6:31                 ` Brad Campbell
2011-06-01  6:56                   ` Avi Kivity
2011-06-01  9:29                     ` Brad Campbell
2011-06-01  9:40                       ` Avi Kivity
2011-06-01  9:41                         ` Avi Kivity
2011-06-01 10:53                           ` Brad Campbell
2011-06-01 11:09                             ` Avi Kivity
2011-06-01 11:18                             ` CaT
2011-06-01 11:52                               ` Brad Campbell
2011-06-01 23:03                                 ` CaT
2011-06-03 13:38                                   ` Brad Campbell
2011-06-03 15:50                                     ` Bernhard Held
2011-06-03 16:07                                       ` Brad Campbell
2011-06-06 20:10                                         ` Bart De Schuymer
2011-06-06 20:23                                           ` Eric Dumazet
2011-06-07  3:33                                           ` Brad Campbell
2011-06-07 13:30                                             ` Patrick McHardy
2011-06-07 14:40                                               ` Brad Campbell
2011-06-07 15:35                                                 ` Patrick McHardy
2011-06-07 18:31                                                   ` Eric Dumazet
2011-06-07 22:57                                                     ` Patrick McHardy
2011-06-08  0:18                                                       ` Brad Campbell
2011-06-08  3:59                                                         ` Eric Dumazet
2011-06-08 17:02                                                           ` Brad Campbell
2011-06-08 21:22                                                             ` Eric Dumazet
2011-06-10  2:52                                                             ` Simon Horman
2011-06-10 12:37                                                               ` Mark Lord
2011-06-10 16:43                                                                 ` Henrique de Moraes Holschuh
2011-06-12 15:38                                                               ` Avi Kivity
2011-06-07 23:43                                                   ` Brad Campbell
2011-06-07 18:04                                                 ` Bart De Schuymer
2011-06-08  0:15                                                   ` Brad Campbell
2011-06-05  8:14                                     ` Avi Kivity
2011-06-05 13:45                                       ` Brad Campbell
2011-06-05 13:58                                         ` Avi Kivity
2011-06-06 20:22                                         ` Eric Dumazet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DE5853E.8040106@fnarfbargle.com \
    --to=lists2009@fnarfbargle.com \
    --cc=aarcange@redhat.com \
    --cc=bp@alien8.de \
    --cc=hughd@google.com \
    --cc=ieidus@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox