Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759001AbYFDJ5W (ORCPT ); Wed, 4 Jun 2008 05:57:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753209AbYFDJ5M (ORCPT ); Wed, 4 Jun 2008 05:57:12 -0400 Received: from rv-out-0506.google.com ([209.85.198.235]:3639 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753190AbYFDJ5K (ORCPT ); Wed, 4 Jun 2008 05:57:10 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Q4wKXJsoYZkPlSYLzabkb3/QAWXZCPtlZhWOB+7Ae7X+nZ5JYdcVGGJq5PhhUlt7IY Ya4GMHuHiAo598LdyCQwQoKbrMf4FXITeptVx8qwMoAGhurhng3USfdS2HRHaQWxUxwb 5lr2AiDfxod5AIKWPXtv4s9d1c2zsok46ijm0= Message-ID: Date: Wed, 4 Jun 2008 11:57:09 +0200 From: "Zdenek Kabelac" To: "Avi Kivity" Subject: Re: BUG: using smp_processor_id() in preemptible [00000000] code: pm-suspend/17334 Cc: "Jiri Kosina" , linux-kernel@vger.kernel.org, kvm@vger.kernel.org In-Reply-To: <48466349.1030907@qumranet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48466349.1030907@qumranet.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3160 Lines: 85 2008/6/4 Avi Kivity : > Jiri Kosina wrote: >> >> [ re-introduced LKML to CC, and also added KVM CCs] >> >> On Tue, 3 Jun 2008, Zdenek Kabelac wrote: >> >> >>> >>> 2008/6/3 Jiri Kosina : >>> >>>> >>>> On Tue, 3 Jun 2008, Zdenek Kabelac wrote: >>>> >>>> >>>>> >>>>> Another backtrace from suspend code path: >>>>> (T61, 2GB, C2D, no SD card) >>>>> kernel from git 20080603, commit >>>>> 1beee8dc8cf58e3f605bd7b34d7a39939be7d8d2 >>>>> ---- >>>>> agpgart-intel 0000:00:00.0: LATE suspend >>>>> platform bay.0: LATE suspend >>>>> platform dock.0: LATE suspend >>>>> Extended CMOS year: 2000 >>>>> hwsleep-0324 [00] enter_sleep_state : Entering sleep state [S3] >>>>> Back to C! >>>>> BUG: using smp_processor_id() in preemptible [00000000] code: >>>>> pm-suspend/17334 >>>>> caller is do_machine_check+0xa9/0x500 >>>>> Pid: 17334, comm: pm-suspend Not tainted 2.6.26-rc4 #31 >>>>> Call Trace: >>>>> [] debug_smp_processor_id+0xcc/0xd0 >>>>> [] do_machine_check+0xa9/0x500 >>>>> [] ? init_8259A+0x1b/0x120 >>>>> [] mce_init+0x56/0xf0 >>>>> [] mce_resume+0xb/0x10 >>>>> [] __sysdev_resume+0x20/0x60 >>>>> [] sysdev_resume+0x58/0x90 >>>>> [] device_power_up+0x9/0x10 >>>>> [] suspend_devices_and_enter+0x147/0x1a0 >>>>> [] enter_state+0x146/0x1d0 >>>>> [] state_store+0xba/0x100 >>>>> [] kobj_attr_store+0x17/0x20 >>>>> [] sysfs_write_file+0xca/0x140 >>>>> [] vfs_write+0xcb/0x190 >>>>> [] sys_write+0x50/0x90 >>>>> [] system_call_after_swapgs+0x7b/0x80 >>>>> >>>> >>>> This looks very much like the oops you reported here: >>>> http://lkml.org/lkml/2008/4/7/130 >>>> >>>> Is this also a virtual machine run under KVM, as it has been in the >>>> aforementioned thread? >>>> >>> >>> Ahh yes - you are right , I've completely forget about that old post - >>> I've thought that my post are usually getting fixed sooner :) >>> So yes - this is actually the same bug which is still not fixed within >>> the latest kernel - the machine is running qemu guest (which seems to >>> me now somehow also slower) >>> >> >> OK, so it looks like KVM could be wrongly enabling IRQs/preemption on the >> resume path. The original bug-report is on http://lkml.org/lkml/2008/4/7/130 >> >> > > Wait, is this in a virtual machine, or on a host that's also running a > virtual machine (or has the kvm modules loaded)? > > I looked at the kvm host resume path, and it doesn't touch interrupts. Oops is from my real-hardware T61 (host) running the kvm-qemu (guest) and was noticed after suspend. But everything seemed to work just fine - host&guest continued to operate normally after resume. Zdenek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/