From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: just a dump Date: Sun, 24 May 2009 14:49:31 +0300 Message-ID: <4A19344B.8070503@redhat.com> References: <4A09E620.3040300@xs4all.nl> <4A09F62A.8010203@xs4all.nl> <20090515144923.GA6304@amt.cnet> <4A0E7B81.6070203@xs4all.nl> <20090516131046.GB3153@amt.cnet> <4A152B7C.4080401@xs4all.nl> <4A152E9B.3060500@xs4all.nl> <20090523214753.GA17590@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Hans de Bruin , kvm@vger.kernel.org To: Marcelo Tosatti Return-path: Received: from mx2.redhat.com ([66.187.237.31]:37023 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752103AbZEXLtc (ORCPT ); Sun, 24 May 2009 07:49:32 -0400 In-Reply-To: <20090523214753.GA17590@amt.cnet> Sender: kvm-owner@vger.kernel.org List-ID: 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