From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: mmu.c:307 BUG with kvm-48 Date: Mon, 29 Oct 2007 13:06:50 +0100 Message-ID: <20071029120650.GD23491@bingen.suse.de> References: <200710291131.48929.ak@suse.de> <1193654536.4484.14.camel@izike-woof.qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Andi Kleen To: Izik Eidus Return-path: Content-Disposition: inline In-Reply-To: <1193654536.4484.14.camel-siXIhNkUrCXckEVJwWePHtCfPAL7FxvL@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org On Mon, Oct 29, 2007 at 12:42:16PM +0200, Izik Eidus wrote: > On Mon, 2007-10-29 at 11:31 +0100, Andi Kleen wrote: > > FYI, > > > > I got this BUG while playing around with some guests with kvm-48 > > on a Core2 system. Base kernel was 2.6.23+ff patches > > (that is why you see the LBR output; BTW that makes KVM complain > > too when it happens in a guest) . Haven't looked at it closely. > > > > -Andi > it look like the slab cache is not initlized for some reason, > there was fix in kvm-49 that initied the slab cache in another place. > (check out commits arround b95061aec006bc4c44e4b244e4ec15c009ab880a) > > can you please check if it happen in kvm-49 as well? I can try it next time and see if it happens again. It is not easily reproducible (that would fit the uninitialized memory theory) -Andi > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/