From: Jiri Slaby <jirislaby@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, the arch/x86 maintainers <x86@kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>
Subject: WARNING: kernel/smp.c:292 smp_call_function_single [Was: mmotm 2009-11-24-16-47 uploaded]
Date: Fri, 27 Nov 2009 16:03:26 +0100 [thread overview]
Message-ID: <4B0FEA3E.5050108@gmail.com> (raw)
In-Reply-To: <200911250111.nAP1BFg5030254@imap1.linux-foundation.org>
On 11/25/2009 01:47 AM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2009-11-24-16-47 has been uploaded to
Hi, when executing qemu-kvm I often get following warning and a hard lockup.
WARNING: at kernel/smp.c:292 smp_call_function_single+0xbd/0x140()
Hardware name: To Be Filled By O.E.M.
Modules linked in: kvm_intel kvm fuse ath5k ath
Pid: 3265, comm: qemu-kvm Not tainted 2.6.32-rc8-mm1_64 #912
Call Trace:
[<ffffffff81039678>] warn_slowpath_common+0x78/0xb0
[<ffffffffa007fd50>] ? __vcpu_clear+0x0/0xd0 [kvm_intel]
[<ffffffff810396bf>] warn_slowpath_null+0xf/0x20
[<ffffffff8106410d>] smp_call_function_single+0xbd/0x140
[<ffffffffa0080af6>] vmx_vcpu_load+0x46/0x170 [kvm_intel]
[<ffffffffa004dd94>] kvm_arch_vcpu_load+0x24/0x60 [kvm]
[<ffffffffa0047a8d>] kvm_sched_in+0xd/0x10 [kvm]
[<ffffffff8102de37>] finish_task_switch+0x67/0xc0
[<ffffffff814699f8>] schedule+0x2f8/0x9c0
[<ffffffffa0063538>] ? kvm_apic_has_interrupt+0x48/0x90 [kvm]
[<ffffffffa0062a58>] ? kvm_cpu_has_interrupt+0x58/0x70 [kvm]
[<ffffffffa0047c9d>] kvm_vcpu_block+0x6d/0xb0 [kvm]
[<ffffffff81050f60>] ? autoremove_wake_function+0x0/0x40
[<ffffffffa0055a5a>] kvm_arch_vcpu_ioctl_run+0x3fa/0xb80 [kvm]
[<ffffffffa0049955>] kvm_vcpu_ioctl+0x435/0x590 [kvm]
[<ffffffff8102f4ce>] ? enqueue_entity+0x6e/0xe0
[<ffffffff8102f5eb>] ? enqueue_task_fair+0x3b/0x80
[<ffffffff8102f6c3>] ? task_new_fair+0x93/0x120
[<ffffffff810cd848>] vfs_ioctl+0x38/0xd0
[<ffffffff810cdd8a>] do_vfs_ioctl+0x8a/0x5a0
[<ffffffff81062926>] ? sys_futex+0xc6/0x170
[<ffffffff810ce2ea>] sys_ioctl+0x4a/0x80
[<ffffffff81002eeb>] system_call_fastpath+0x16/0x1b
---[ end trace ced05997e63d4d13 ]---
It is a regression against 2009-11-13-19-59.
Any ideas?
thanks,
--
js
next prev parent reply other threads:[~2009-11-27 15:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 0:47 mmotm 2009-11-24-16-47 uploaded akpm
2009-11-25 15:12 ` BUG at scsi_lib.c:1108 [Was: mmotm 2009-11-24-16-47 uploaded] Jiri Slaby
2009-11-25 15:19 ` James Bottomley
2009-11-25 20:22 ` Jiri Slaby
2009-11-25 21:13 ` Neil Brown
2009-11-26 10:17 ` Boaz Harrosh
2009-11-27 4:17 ` Neil Brown
2009-11-27 10:20 ` Jiri Slaby
2009-11-26 1:46 ` mmotm 2009-11-24-16-47 uploaded (gpio_max7301) Randy Dunlap
2009-11-28 16:21 ` Wolfram Sang
2009-12-15 22:43 ` Andrew Morton
2009-12-15 22:46 ` Randy Dunlap
2009-12-15 23:10 ` Andrew Morton
2009-12-16 11:30 ` Wolfram Sang
2009-11-27 10:33 ` ugly sound output (intel-hda) [was: mmotm 2009-11-24-16-47 uploaded] Jiri Slaby
2009-11-27 10:33 ` Jiri Slaby
2009-11-27 10:45 ` Takashi Iwai
2009-11-27 10:45 ` Takashi Iwai
2009-11-27 11:07 ` Jiri Slaby
2009-11-27 11:07 ` Jiri Slaby
2009-11-27 11:18 ` Takashi Iwai
2009-11-27 11:18 ` Takashi Iwai
2009-11-27 12:22 ` Jiri Slaby
2009-11-27 12:22 ` Jiri Slaby
2009-11-27 12:26 ` Takashi Iwai
2009-11-27 12:26 ` Takashi Iwai
2009-11-27 15:03 ` Jiri Slaby [this message]
2009-11-27 15:17 ` WARNING: kernel/smp.c:292 smp_call_function_single [Was: " Peter Zijlstra
2009-11-27 16:37 ` Thomas Gleixner
2009-11-27 16:44 ` Thomas Gleixner
2009-11-28 12:12 ` Avi Kivity
2009-11-30 8:58 ` Tejun Heo
2009-11-30 9:41 ` Avi Kivity
2009-11-30 10:02 ` Thomas Gleixner
2009-11-30 10:45 ` Tejun Heo
2009-11-30 11:02 ` [PATCH tip/sched/urgent] sched: revert 498657a478c60be092208422fefa9c7b248729c2 Tejun Heo
2009-11-30 11:13 ` 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=4B0FEA3E.5050108@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peterz@infradead.org \
--cc=x86@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 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.