kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, avi@redhat.com
Subject: Re: broken timer
Date: Tue, 28 Jul 2009 09:33:05 +0300	[thread overview]
Message-ID: <20090728063305.GF30449@redhat.com> (raw)
In-Reply-To: <20090727180540.GG4776@poweredge.glommer>

On Mon, Jul 27, 2009 at 03:05:40PM -0300, Glauber Costa wrote:
> Hello, goodfellas
> 
> I'm seeing a strange problem in our much loved qemu-kvm.git
This bug shouldn't depend on qemu-kvm.git at all unless you are running
with no-kvm-irqchip. The only things that involved in APIC timer
calibration are tsc and APIC. (If you don't use apicpmtimer kernel
parameter. Don't you?)

What is you host HW? Which version of kernel modules are you using?
Is your host overcommitted when this happens? Try to load the host with
work (while(1)) and run the guest. Is it easier to reproduce problem
this way?

> It's been there before avi left for vacation, at least.
> 
> The worst part, is that it doesn't happen always, and I don't
> even think it is deterministic in its nature, IOW, there was nothing
> I could do to make it more or less likely to happen.
> 
> It's almost obviously interrupt related, but I can't determine more than that
> As I haven't, and won't have the time to debug this in the near future, here's
> the riddle for you all to appreciate:
> 
> ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1                                                                                                         
> CPU0: QEMU Virtual CPU version 0.10.50 stepping 03                                                                                                           
> Using local APIC timer interrupts.                                                                                                                           
> Detected 0.000 MHz APIC timer.                                                                                                                               
> ------------[ cut here ]------------                                                                                                                         
> WARNING: at kernel/time/clockevents.c:46 clockevent_delta2ns+0x37/0x72() (Not tainted)                                                                       
> Modules linked in:                                                                                                                                           
> Pid: 1, comm: swapper Not tainted 2.6.27.5-117.fc10.x86_64 #1                                                                                                
> 
> Call Trace:
>  [<ffffffff810418f2>] warn_on_slowpath+0x60/0x90
>  [<ffffffff81331c7e>] ? trace_hardirqs_on_thunk+0x3a/0x3c
>  [<ffffffff8159d140>] ? early_idt_handler+0x0/0x72       
>  [<ffffffff8132faf6>] ? printk+0x3c/0x3e                 
>  [<ffffffff8105cb9a>] clockevent_delta2ns+0x37/0x72      
>  [<ffffffff815ad263>] setup_boot_APIC_clock+0x1c2/0x24b  
>  [<ffffffff8132faf6>] ? printk+0x3c/0x3e                 
>  [<ffffffff815ab8a6>] native_smp_prepare_cpus+0x29e/0x2cf
>  [<ffffffff8159d5a8>] kernel_init+0x59/0x214             
>  [<ffffffff81331c7e>] ? trace_hardirqs_on_thunk+0x3a/0x3c
>  [<ffffffff810116e9>] child_rip+0xa/0x11                 
>  [<ffffffff81010a07>] ? restore_args+0x0/0x30            
>  [<ffffffff8159d54f>] ? kernel_init+0x0/0x214            
>  [<ffffffff810116df>] ? child_rip+0x0/0x11
> 
> ---[ end trace 4eaa2a86a8e2da22 ]---
> APIC frequency too slow, disabling apic timer
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
			Gleb.

  reply	other threads:[~2009-07-28  6:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 18:05 broken timer Glauber Costa
2009-07-28  6:33 ` Gleb Natapov [this message]
2009-07-28 13:35   ` Glauber Costa

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=20090728063305.GF30449@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.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).