From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: BUG: using smp_processor_id() in preemptible Date: Mon, 29 Jun 2009 12:08:40 +0300 Message-ID: <4A488498.1030102@redhat.com> References: <1245852919.21314.56.camel@johannes.local> <4A477A14.8070801@redhat.com> <1246264335.7775.5.camel@johannes.local> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Johannes Berg Return-path: Received: from mx2.redhat.com ([66.187.237.31]:60287 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751445AbZF2JHM (ORCPT ); Mon, 29 Jun 2009 05:07:12 -0400 In-Reply-To: <1246264335.7775.5.camel@johannes.local> Sender: kvm-owner@vger.kernel.org List-ID: On 06/29/2009 11:32 AM, Johannes Berg wrote: > On Sun, 2009-06-28 at 17:11 +0300, Avi Kivity wrote: > > >>> 1) I get the $subject warning a lot, when starting kvm: >>> [85763.262707] BUG: using smp_processor_id() in preemptible [00000000] code: kvm/13877 >>> [85763.262719] caller is kvm_write_guest_time+0x40/0x220 [kvm] >>> [85763.262722] Pid: 13877, comm: kvm Not tainted 2.6.30-wl-26837-g0ee651a-dirty #54 >>> [85763.262725] Call Trace: >>> [85763.262729] [] debug_smp_processor_id+0xf2/0x100 >>> [85763.262741] [] kvm_write_guest_time+0x40/0x220 [kvm] >>> [85763.262753] [] vcpu_enter_guest+0x320/0x580 [kvm] >>> [85763.262780] [] __vcpu_run+0x74/0x2f0 [kvm] >>> [85763.262792] [] kvm_arch_vcpu_ioctl_run+0x8f/0x200 [kvm] >>> [85763.262804] [] kvm_vcpu_ioctl+0x4b8/0x900 [kvm] >>> [85763.262816] [] vfs_ioctl+0x36/0xb0 >>> [85763.262819] [] do_vfs_ioctl+0x89/0x320 >>> [85763.262826] [] sys_ioctl+0x4f/0x80 >>> [85763.262830] [] system_call_fastpath+0x16/0x1b >>> >>> >>> >> ISTR this was fixed... >> >> >>> That kernel version is wireless-testing, which is currently based on >>> v2.6.30, and the -dirty is for some wireless patches I did. >>> >>> >> Please post the output of 'git merge-base wireless-testing >> origin/master' so I can know what tree to look at. >> > > ITYM > > $ git merge-base wireless-testing/master linux-2.6/master > 07a2039b8eb0af4ff464efd3dfd95de5c02648c6 > $ git describe 07a2039b8eb0af4ff464efd3dfd95de5c02648c6 > v2.6.30 > > since my personal 'origin' branch is something completely different. > > Yes. It was fixed in mainline by 2dea4c84bc. I'll prepare something for -stable. >> You can see where it hangs using the monitor 'info registers' and 'x/30i >> $eip' commands. >> > > not much luck since it doesn't hang at a specific instruction: > You can try mapping these with gdb (in fact, you can have gdb connect to qemu and do source level debugging). -- error compiling committee.c: too many arguments to function