From: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
To: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
Subject: Re: mmu.c:307 BUG with kvm-48
Date: Mon, 29 Oct 2007 13:06:50 +0100 [thread overview]
Message-ID: <20071029120650.GD23491@bingen.suse.de> (raw)
In-Reply-To: <1193654536.4484.14.camel-siXIhNkUrCXckEVJwWePHtCfPAL7FxvL@public.gmane.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/
next prev parent reply other threads:[~2007-10-29 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 10:31 mmu.c:307 BUG with kvm-48 Andi Kleen
[not found] ` <200710291131.48929.ak-l3A5Bk7waGM@public.gmane.org>
2007-10-29 10:42 ` Izik Eidus
[not found] ` <1193654536.4484.14.camel-siXIhNkUrCXckEVJwWePHtCfPAL7FxvL@public.gmane.org>
2007-10-29 12:06 ` Andi Kleen [this message]
[not found] ` <20071029120650.GD23491-KvMlXPVkKihbpigZmTR7Iw@public.gmane.org>
2007-10-30 3:29 ` 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=20071029120650.GD23491@bingen.suse.de \
--to=ak-l3a5bk7wagm@public.gmane.org \
--cc=izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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