Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762917AbZFNTk0 (ORCPT ); Sun, 14 Jun 2009 15:40:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754522AbZFNTkS (ORCPT ); Sun, 14 Jun 2009 15:40:18 -0400 Received: from mail-bw0-f213.google.com ([209.85.218.213]:64554 "EHLO mail-bw0-f213.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753445AbZFNTkQ (ORCPT ); Sun, 14 Jun 2009 15:40:16 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; b=XDRDBbqHAiw6Dc0p1yEhv8WSB1twfeBYTn+vEbLXpLU1qZzohuWrfXD1AlvPhYxyQu rvBkY7OHUixfu0KJZ/1mvWfwMkq3XJNvq6pzyqrpo8x9mD//hC3XCRSraKbISJ/2Yott 8gYTzSTueBE0wszh6gFzJqV+hQbRpof/Yy/Js= Date: Sun, 14 Jun 2009 23:40:17 +0400 From: Cyrill Gorcunov To: Simon Holm =?iso-8859-1?Q?Th=F8gersen?= , linux-kernel , Ingo Molnar Cc: Andi Kleen Subject: Re: apic: native_apic_write_dummy warning Message-ID: <20090614194017.GA24604@lenovo> References: <1245006351.5912.174.camel@odie.local> <20090614192220.GB4851@lenovo> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20090614192220.GB4851@lenovo> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2182 Lines: 51 [Cyrill Gorcunov - Sun, Jun 14, 2009 at 11:22:20PM +0400] | [Simon Holm Th?gersen - Sun, Jun 14, 2009 at 09:05:50PM +0200] | | Hi Cyrill | | | | I guess you want to know about these warnings, so here you go | | | | WARNING: at arch/x86/kernel/apic/apic.c:249 native_apic_write_dummy+0x32/0x3e() | | Hardware name: | | Modules linked in: | | Pid: 0, comm: swapper Not tainted 2.6.30-debug-03392-g44b7532 #17 | | Call Trace: | | [] warn_slowpath_common+0x65/0x95 | | [ 0.006956] [] warn_slowpath_null+0x12/0x15 | | [ 0.007031] [] native_apic_write_dummy+0x32/0x3e | | [ 0.007109] [] intel_init_thermal+0xd3/0x178 | | [ 0.007185] [] ? native_read_msr_safe+0x9/0x16 | | [ 0.007263] [] ? __kmalloc+0x117/0x123 | | [ 0.007338] [] mce_intel_feature_init+0x10/0x50 | | [ 0.007416] [] mcheck_init+0x1d5/0x263 | | [ 0.007492] [] identify_cpu+0x369/0x378 | | [ 0.007569] [] ? _spin_unlock+0x3d/0x49 | | [ 0.007644] [] ? proc_register+0x150/0x161 | | [ 0.007721] [] identify_boot_cpu+0xd/0x23 | | [ 0.007796] [] check_bugs+0xb/0xf1 | | [ 0.007872] [] start_kernel+0x293/0x2a7 | | [ 0.008011] [] i386_start_kernel+0x65/0x6a | | | | | | Simon Holm Th?gersen | | Hi Simon, thanks a lot for report! Will take a look. | | -- Cyrill Neither thermal interrupts nor mce will be functional if apic is not properly set up (even having kernel compiled that way it support both). So you may try to pass "lapic" boot option and check if we're lucky in attempt to enable apic via force push. Anyway this warn show that the code is to be fixed (and native_apic_write_dummy done its work great catching useless apic->write operation). I'll handle it but a bit later. Andi CC'ed since he is involved in MCE handling just for the record. -- Cyrill -- 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/