All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Hans de Bruin <bruinjm@xs4all.nl>, kvm@vger.kernel.org
Subject: Re: just a dump
Date: Sun, 24 May 2009 14:49:31 +0300	[thread overview]
Message-ID: <4A19344B.8070503@redhat.com> (raw)
In-Reply-To: <20090523214753.GA17590@amt.cnet>

Marcelo Tosatti wrote:
>> another one. This time the vm where booted sequentialy:
>>
>> [  253.268993] kvm: 2907: cpu0 unimplemented perfctr wrmsr: 0xc0010003  
>> data 0x0
>> [  475.036542] rmap_remove: ffff8800cdb913b0 10 0->BUG
>>     
> 					      ^^^
>
> So 0x10 is 1 bit different from 0x00, which would be the no present
> entry for AMD.
>
> Usually an indication of hardware problems. Perhaps you want to try
> the test Lucas mentioned.
>   

It's actually the PCD bit, not that it affects your analysis.  Strange 
that we see this pattern (1 bit differences on sptes) on both AMD and 
Intel.  Very suspicious.


-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2009-05-24 11:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 21:12 just a dump Hans de Bruin
2009-05-12 22:20 ` Hans de Bruin
2009-05-15 14:49   ` Marcelo Tosatti
2009-05-16  8:38     ` Hans de Bruin
     [not found]       ` <20090516131046.GB3153@amt.cnet>
2009-05-21 10:22         ` Hans de Bruin
2009-05-21 10:36           ` Hans de Bruin
2009-05-21 11:03             ` Hans de Bruin
2009-05-23 21:47             ` Marcelo Tosatti
2009-05-24  8:47               ` Hans de Bruin
2009-05-24 11:49               ` Avi Kivity [this message]
2009-05-25 18:47                 ` Marcelo Tosatti
2009-05-21 13:51       ` Lucas Meneghel Rodrigues
2009-05-27  7:43         ` Hans de Bruin
2009-05-28 13:39           ` Lucas Meneghel Rodrigues
2009-07-05 18:40       ` Hans de Bruin
2009-07-06  7:39         ` Avi Kivity

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=4A19344B.8070503@redhat.com \
    --to=avi@redhat.com \
    --cc=bruinjm@xs4all.nl \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.