All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Yinghai Lu <yhlu.kernel@gmail.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: kvm hangs w/o nolapic
Date: Fri, 20 Nov 2009 21:18:15 +0300	[thread overview]
Message-ID: <20091120181815.GA8779@lenovo> (raw)
In-Reply-To: <1258715515.7094.51.camel@johannes.local>

On Fri, Nov 20, 2009 at 12:11:55PM +0100, Johannes Berg wrote:
> My 2.6.32-rc7 kvm (both guest+host, x86_64) hangs w/o "nolapic" here:
> 
>   while (lapic_cal_loops <= LAPIC_CAL_LOOPS)
>      cpu_relax();
> 
> because lapic_cal_loops never changes from -1.
> 
> Code was last changed by
> commit 2f04fa888d270951b9e0fe9e641ddd560d77ad1b
> Author: Yinghai Lu <yhlu.kernel@gmail.com>
> Date:   Sun Aug 24 02:01:54 2008 -0700
> 
>     x86: apic copy calibrate_APIC_clock to each other in apic_32/64.c
> 
> but I haven't tested reverting that.
> 
> johannes

Hi Johannes,

It will be not easy to revert since the commit was "preparing to merge"
apic_32/64.c. It rather seems there is a problem with timer(s) other then
APIC's one (ie PIT, HPET, PM). And since you're under kvm -- it could be
a corner case as well.

I've just booted a latest -tip with kvm without problems.
I've been using

|
| QEMU PC emulator version 0.9.1 (kvm-84)
|

Perhaps you could capture console with "debug apic=debug") and to gather
more info? And .config?

	-- Cyrill

  reply	other threads:[~2009-11-20 18:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 11:11 kvm hangs w/o nolapic Johannes Berg
2009-11-20 18:18 ` Cyrill Gorcunov [this message]
2009-11-20 21:25   ` Johannes Berg
2009-11-22 20:44     ` Cyrill Gorcunov
2009-11-23 19:05     ` Marcelo Tosatti
2009-11-23 23:57       ` Johannes Berg

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=20091120181815.GA8779@lenovo \
    --to=gorcunov@gmail.com \
    --cc=avi@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mtosatti@redhat.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=yhlu.kernel@gmail.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.