Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758100AbZKRRo5 (ORCPT ); Wed, 18 Nov 2009 12:44:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758071AbZKRRo5 (ORCPT ); Wed, 18 Nov 2009 12:44:57 -0500 Received: from relay1.sgi.com ([192.48.179.29]:48732 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758070AbZKRRo4 (ORCPT ); Wed, 18 Nov 2009 12:44:56 -0500 Message-ID: <4B043298.1010208@sgi.com> Date: Wed, 18 Nov 2009 09:44:56 -0800 From: Mike Travis User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Yinghai Lu CC: "H. Peter Anvin" , Ingo Molnar , Thomas Gleixner , Andrew Morton , Heiko Carstens , Roland Dreier , Randy Dunlap , Tejun Heo , Andi Kleen , Greg Kroah-Hartman , David Rientjes , Steven Rostedt , Rusty Russell , Hidetoshi Seto , Jack Steiner , Frederic Weisbecker , x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/5] x86: Limit the number of processor bootup messages References: <20091117191752.164451000@alcatraz.americas.sgi.com> <20091117191757.651569000@alcatraz.americas.sgi.com> <86802c440911171210x4780c08cg3b3260afd5d2bc5d@mail.gmail.com> <4B030799.9020402@zytor.com> <86802c440911171311s1313abf5h4059422b1214ec75@mail.gmail.com> <86802c440911171838q6e96670bnbf4db822484b7204@mail.gmail.com> In-Reply-To: <86802c440911171838q6e96670bnbf4db822484b7204@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3697 Lines: 91 Is this a bug report? Can you supply the system configuration, config file and the kernel release/patched status? I've tested the patches on a few different (Intel) architectures and haven't encountered any panics yet. Thanks, Mike Yinghai Lu wrote: > On Tue, Nov 17, 2009 at 1:11 PM, Yinghai Lu wrote: >> On Tue, Nov 17, 2009 at 12:29 PM, H. Peter Anvin wrote: >>> On 11/17/2009 12:10 PM, Yinghai Lu wrote: >>>>> The following lines have been removed: >>>>> >>>>> CPU: Physical Processor ID: >>>>> CPU: Processor Core ID: >>>>> CPU %d/0x%x -> Node %d >>>> please don't. >>>> >>> Why not? >>> >>> Or, more formally: please state the rationale for keeping them. >>> >> at least one distribution: SLES 11 mess it up when BSP is from socket >> 1 instead of socket0 >> >> and above message does show kernel think BSP still from socket0, and >> other cores in that package are from socket1. > > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 0 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 256K > CPU: L3 cache: 24576K > BUG: unable to handle kernel paging request at ffffffffc07129b0 > IP: [] init_intel+0xea/0x14b > PGD 203067 PUD 204067 PMD 0 > Oops: 0000 [1] SMP > last sysfs file: > CPU 0 > Modules linked in: > Supported: Yes > Pid: 0, comm: swapper Not tainted 2.6.27.19-5-default #1 > RIP: 0010:[] [] init_intel+0xea/0x14b > RSP: 0018:ffffffff80965f48 EFLAGS: 00010202 > RAX: 0000000020000000 RBX: 0000000000000044 RCX: 00000000000001a0 > RDX: ffffffff808cbd14 RSI: 0000000000000046 RDI: 0000000020000000 > RBP: 0000000020000000 R08: 0000000000000000 R09: 0000000000000000 > R10: 000000000000000a R11: ffffffff802223f1 R12: 0000000000000000 > R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 > FS: 0000000000000000(0000) GS:ffffffff80a40080(0000) knlGS:0000000000000000 > CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b > CR2: ffffffffc07129b0 CR3: 0000000000201000 CR4: 00000000000006a0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 > Process swapper (pid: 0, threadinfo ffffffff80964000, task ffffffff806da380) > Stack: 0000000100000003 0000000100000000 ffffffff808cbd00 ffffe20000000000 > 0000007800000000 ffffffff804943ef 0000000000000000 ffffffff80974fda > 0000000000000000 ffffffff8096de10 0000000000000000 ffffffff809a1510 > Call Trace: > [] identify_cpu+0x3c/0xa3 > [] check_bugs+0x9/0x2e > [] start_kernel+0x313/0x324 > [] x86_64_start_kernel+0xde/0xe4 > > > Code: 0f a2 a8 1f 74 07 c1 e8 1a ff c0 eb 05 b8 01 00 00 00 66 89 85 d8 00 00 00 > 65 44 8b 24 25 24 00 00 00 e8 c3 66 d8 ff 89 c5 48 98 <0f> bf 9c 00 b0 29 71 80 > 83 fb ff 74 0d 0f a3 1d 91 a1 4c 00 19 > RIP [] init_intel+0xea/0x14b > RSP > CR2: ffffffffc07129b0 > ---[ end trace 4eaa2a86a8e2da22 ]--- > > > 2.6.32 kernel corresponding part: > > [ 0.128855] CPU: Physical Processor ID: 1 > [ 0.129856] CPU: Processor Core ID: 0 > [ 0.130845] CPU: L1 I cache: 32K, L1 D cache: 32K > [ 0.151454] CPU: L2 cache: 256K > [ 0.152463] CPU: L3 cache: 24576K > [ 0.153471] CPU 0/0x20 -> Node 0 > [ 0.168552] CPU 0 microcode level: 0xffff0008 > [ 0.169901] mce: CPU supports 22 MCE banks -- 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/