public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
To: david ahern <daahern-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: soft lockup  in kvm_flush_remote_tlbs
Date: Thu, 25 Oct 2007 01:15:16 +0200	[thread overview]
Message-ID: <471FD204.6040400@bull.net> (raw)
In-Reply-To: <471FCEA6.6000903-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>

david ahern a écrit :
> I am trying, unsuccessfully so far, to get a vm running with 4 cpus. It is failing with a soft lockup:
> 
> BUG: soft lockup detected on CPU#3!
>  [<c044a05f>] softlockup_tick+0x98/0xa6
>  [<c042ccd4>] update_process_times+0x39/0x5c
>  [<c04176ec>] smp_apic_timer_interrupt+0x5c/0x64
>  [<c04049bf>] apic_timer_interrupt+0x1f/0x24
>  [<f8a3c800>] kvm_flush_remote_tlbs+0xce/0xdb [kvm]
>  [<f8a41a72>] kvm_mmu_pte_write+0x1f2/0x368 [kvm]
>  [<f8a3d335>] emulator_write_emulated_onepage+0x73/0xe6 [kvm]
>  [<f8a4542c>] x86_emulate_insn+0x20d8/0x3348 [kvm]
>  [<f8a43106>] x86_decode_insn+0x624/0x872 [kvm]
>  [<f8a3d764>] emulate_instruction+0x12b/0x258 [kvm]
>  [<f88af2e4>] handle_exception+0x163/0x23f [kvm_intel]
>  [<f88af09b>] kvm_handle_exit+0x70/0x8a [kvm_intel]
>  [<f8a3deae>] kvm_vcpu_ioctl_run+0x234/0x339 [kvm]
>  [<f8a3e27f>] kvm_vcpu_ioctl+0x0/0xa8f [kvm]
>  [<f8a3e33c>] kvm_vcpu_ioctl+0xbd/0xa8f [kvm]
>  [<c0408f60>] save_i387+0x23f/0x273
>  [<c04db730>] __next_cpu+0x12/0x21
>  [<c041c97f>] find_busiest_group+0x177/0x462
>  [<c04031cd>] setup_sigcontext+0x10d/0x190
>  [<c0453bed>] get_page_from_freelist+0x96/0x310
>  [<c0453dfd>] get_page_from_freelist+0x2a6/0x310
>  [<c0415a5c>] flush_tlb_others+0x83/0xb3
>  [<c0415d63>] flush_tlb_page+0x74/0x77
>  [<c0454cf1>] set_page_dirty_balance+0x8/0x35
>  [<c0459c1b>] do_wp_page+0x3a5/0x3bd
>  [<c042e97e>] dequeue_signal+0x2d/0x9c
>  [<c045af6b>] __handle_mm_fault+0x81b/0x87b
>  [<f8a3e27f>] kvm_vcpu_ioctl+0x0/0xa8f [kvm]
>  [<c0479cac>] do_ioctl+0x1c/0x5d
>  [<c0479f37>] vfs_ioctl+0x24a/0x25c
>  [<c0479f91>] sys_ioctl+0x48/0x5f
>  [<c0403eff>] syscall_call+0x7/0xb
> 
> 
> I am working with kvm-48, but also tried the 20071020 snapshot. The stuck code is kvm_flush_remote_tlbs():
> 
> 	while (atomic_read(&completed) != needed) {
> 		cpu_relax();
> 		barrier();
> 	}
> 

This part has been removed by commit 49d3bd7e2b990e717aa66e229410b8f5096c4956, 
perhaps you could try it ?

commit 49d3bd7e2b990e717aa66e229410b8f5096c4956
Author: Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
Date:   Mon Oct 22 16:33:07 2007 +0200

     KVM: Use new smp_call_function_mask() in kvm_flush_remote_tlbs()

     In kvm_flush_remote_tlbs(), replace a loop using smp_call_function_single()
     by a single call to smp_call_function_mask() (which is new for x86_64).

     Signed-off-by: Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
     Signed-off-by: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

> which I take to mean one of the CPUs is not ack'ing the TLB flush request. 

Yes, it seems...

> Is this is a known bug and any options to correct it? It works fine with 2 vcpus, but for a comparison with xen I'd like to get the vm working with 4.
> 
> 
> Host stats:
> OS: RHEL5
> Processors: 2-Core 2 Duos (4 processors)
> KVM:  kvm-48 and kvm-20071020-1 snapshot rpms
> QEMU command:
> 
> qemu-kvm -boot c -localtime -hda /opt/kvm/images/cucm.img -m 1536 -smp 4 -serial file:/tmp/serial.log -net nic,macaddr=00:1a:4b:34:74:52,model=rtl8139 -net tap,ifname=tap0,script=/bin/true -vnc :2 -monitor stdio
> 
> 
> thanks,
> 
> david
> 
> -------------------------------------------------------------------------
> 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/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
> 


-- 
---------------- Laurent.Vivier-6ktuUTfB/bM@public.gmane.org  -----------------
"Given enough eyeballs, all bugs are shallow" E. S. Raymond


-------------------------------------------------------------------------
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/

  parent reply	other threads:[~2007-10-24 23:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 23:00 soft lockup in kvm_flush_remote_tlbs david ahern
     [not found] ` <471FCEA6.6000903-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2007-10-24 23:15   ` Laurent Vivier [this message]
     [not found]     ` <471FD204.6040400-6ktuUTfB/bM@public.gmane.org>
2007-10-25  4:26       ` david ahern
2007-10-25  6:47   ` Avi Kivity
     [not found]     ` <47203BEB.9070509-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-25 13:30       ` david ahern
     [not found]         ` <47209A77.3090503-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2007-10-25 13:46           ` Avi Kivity
     [not found]             ` <47209E23.8080808-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-25 14:07               ` david ahern
2007-10-25 18:34               ` david ahern
     [not found]                 ` <4720E19B.20802-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2007-10-25 18:35                   ` Avi Kivity
     [not found]                     ` <4720E1EB.6020700-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-25 23:05                       ` david ahern

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=471FD204.6040400@bull.net \
    --to=laurent.vivier-6ktuutfb/bm@public.gmane.org \
    --cc=daahern-FYB4Gu1CFyUAvxtiuMwx3w@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