From: Avi Kivity <avi@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: percpu crash on NetBurst
Date: Wed, 21 Sep 2011 17:28:07 +0300 [thread overview]
Message-ID: <4E79F477.2050102@redhat.com> (raw)
In-Reply-To: <20110808095517.GH23937@htj.dyndns.org>
On 08/08/2011 12:55 PM, Tejun Heo wrote:
> Hello, Avi.
>
> On Sun, Aug 07, 2011 at 06:32:35PM +0300, Avi Kivity wrote:
> > qemu, under some conditions (-cpu host or -cpu kvm64), erroneously
> > passes family=15 as the virtual cpuid. This causes a BUG() in
> > percpu code during late boot:
> >
> > ------------[ cut here ]------------
> > kernel BUG at mm/percpu.c:577!
>
<snip>
> > All this applies to v3.0; current upstream (c2f340a69ca) fails even
> > worse, haven't yet determined exactly why.
> >
> > I'm surprised this hasn't been reported before; Ingo, don't you have
> > family=15 hosts in your test farm?
>
> Hmmm... I can't trigger the problem w/ kvm64 (I tried mounting and
> unmounting filesystems but it worked okay) and am quite skeptical this
> is a wide spread problem given that the percpu core code is used very
> widely and hasn't seen a lot of changes lately. Is there anything
> specific you need to do to trigger the condition? Can you try to
> print out the s_files addresses being allocated and freed?
>
Coming back to this, the trigger if cpuid family=6 and model>=13 (model
12 works). Looks like the code disables rep_good is some MSR doesn't
have the expected value. While we should configure the MSR correctly,
it looks like the fallback code for !rep_good is broken. Will look further.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-09-21 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 15:32 percpu crash on NetBurst Avi Kivity
2011-08-08 9:55 ` Tejun Heo
2011-09-21 14:28 ` Avi Kivity [this message]
2011-09-21 15:49 ` 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=4E79F477.2050102@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).