Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755517AbYGXKs3 (ORCPT ); Thu, 24 Jul 2008 06:48:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752617AbYGXKsV (ORCPT ); Thu, 24 Jul 2008 06:48:21 -0400 Received: from wf-out-1314.google.com ([209.85.200.172]:15700 "EHLO wf-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752413AbYGXKsU (ORCPT ); Thu, 24 Jul 2008 06:48:20 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=XR1GIWQR5X+ZMpUqcz+PW9SKKQJYHzldjXpC3dnyzlLObLcs7MdqSnH8mVvr/qclJL elBsffkXvBL9GusQdCL+5vMgpzE/WWB5cdvkTTrKSWVXnDUkB/iuSsSEowZEvSA+Mhll z7kaXZPjH3H8yYIac5mLJdUeBDUI9LsKXoulg= Message-ID: <19f34abd0807240348n4c31e6el7358d3fc4d10e392@mail.gmail.com> Date: Thu, 24 Jul 2008 12:48:19 +0200 From: "Vegard Nossum" To: "the arch/x86 maintainers" , "Mike Travis" , LKML Subject: latest -git: kernel BUG at arch/x86/kernel/microcode.c:142! MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2543 Lines: 64 Hi, I just got this when doing CPU hotplug: ------------[ cut here ]------------ kernel BUG at arch/x86/kernel/microcode.c:142! invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC Pid: 4140, comm: bash Not tainted (2.6.26-06371-g338b9bb-dirty #14) EIP: 0060:[] EFLAGS: 00210202 CPU: 0 EIP is at __mc_sysdev_add+0x1ee/0x200 EAX: 00000000 EBX: c1f61028 ECX: 01798000 EDX: c081ac80 ESI: 00000001 EDI: 00000001 EBP: f5bcbe24 ESP: f5bcbdcc DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Process bash (pid: 4140, ti=f5bca000 task=f4066f90 task.ti=f5bca000) Stack: 00000000 f5bcbe24 c028300b 00000001 000000d0 c06d8dc3 f73f77d0 00000000 00000000 00000014 00000000 00000000 c0829254 f4f0fa00 f6e950f0 00200282 f6d5180c 00000002 00000003 00000002 00000001 c1f61028 f5bcbe2c c0117f3a Call Trace: [] ? kobject_uevent_env+0xdb/0x380 [] ? mc_sysdev_add+0xa/0x10 [] ? mc_cpu_callback+0x1ea/0x240 [] ? notifier_call_chain+0x37/0x70 [] ? __raw_notifier_call_chain+0x19/0x20 [] ? raw_notifier_call_chain+0x1a/0x20 [] ? _cpu_up+0xa7/0x100 [] ? cpu_up+0x49/0x80 [] ? store_online+0x58/0x80 [] ? store_online+0x0/0x80 [] ? sysdev_store+0x2c/0x40 [] ? sysfs_write_file+0xa2/0x100 [] ? vfs_write+0x96/0x130 [] ? sysfs_write_file+0x0/0x100 [] ? sys_write+0x3d/0x70 [] ? sysenter_do_call+0x12/0x3f ======================= Code: 4d d8 c7 01 00 00 00 00 b8 00 1a 6f c0 e8 fb 46 47 00 8d 55 f0 64 a1 00 90 7c c0 e8 0d 75 01 00 8b 45 d4 83 c4 4c 5b 5e 5f 5d c3 <0f> 0b eb fe 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 55 31 d2 EIP: [] __mc_sysdev_add+0x1ee/0x200 SS:ESP 0068:f5bcbdcc ---[ end trace 8c86c730d90bf362 ]--- It's this one: /* We should bind the task to the CPU */ BUG_ON(raw_smp_processor_id() != cpu_num); Maybe related to recently merged per-cpu changes? (Yesterday's tests ran fine.) It seems 100% reproducible, so I'll start bisecting it. Vegard -- "The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036 -- 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/