From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756673Ab2DFLhZ (ORCPT ); Fri, 6 Apr 2012 07:37:25 -0400 Received: from mga14.intel.com ([143.182.124.37]:16045 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753094Ab2DFLhV (ORCPT ); Fri, 6 Apr 2012 07:37:21 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="86042061" Message-ID: <4F7ED569.6080103@intel.com> Date: Fri, 06 Apr 2012 19:37:13 +0800 From: Alex Shi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111229 Thunderbird/9.0 MIME-Version: 1.0 To: "linux-kernel@vger.kernel.org" , paulmck@linux.vnet.ibm.com, Ingo Molnar Subject: kernel panic on NHM EX machine Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The 3.4-rc1 kernel has a kernel panic in idle booting. Actually, from 3.3-rc1 kernel we occasionally find this issue may when do busy hackbench testing. but from rc1 kernel it will happens on each of rebooting. all Trace:^M [] __rcu_pending+0xbd/0x3bf^M [] rcu_check_callbacks+0x69/0xa7^M [] update_process_times+0x3a/0x71^M [] tick_sched_timer+0x6b/0x95^M [] __run_hrtimer+0xb8/0x141^M [] ? tick_nohz_handler+0xd3/0xd3^M [] hrtimer_interrupt+0xdb/0x199^M [] tick_do_broadcast.constprop.3+0x44/0x88^M [] tick_do_periodic_broadcast+0x34/0x3e^M [] tick_handle_periodic_broadcast+0xf/0x40^M [] timer_interrupt+0x10/0x17^M [] handle_irq_event_percpu+0x5a/0x199^M [] handle_irq_event+0x37/0x53^M [] ? ack_apic_edge+0x1f/0x23^M [] handle_edge_irq+0xa1/0xc8^M [] handle_irq+0x125/0x12e^M [] ? irq_enter+0x13/0x64^M [] do_IRQ+0x48/0xa0^M [] common_interrupt+0x6a/0x6a^M [] ? tick_do_periodic_broadcast+0x34/0x3e^M [] ? arch_local_irq_enable+0x8/0xd^M [] __do_softirq+0x5e/0x182^M [] ? update_ts_time_stats+0x2c/0x62^M [] ? sched_clock_idle_wakeup_event+0x12/0x16^M [] call_softirq+0x1c/0x30^M [] do_softirq+0x41/0x7d^M [] irq_exit+0x44/0x9c^M [] scheduler_ipi+0x6b/0x6d^M [] smp_reschedule_interrupt+0x16/0x18^M [] reschedule_interrupt+0x6a/0x70^M [] ? arch_local_irq_enable+0x8/0xd^M [] ? sched_clock_idle_wakeup_event+0x12/0x16^M [] acpi_idle_enter_bm+0x222/0x266^M [] cpuidle_enter+0x12/0x14^M [] cpuidle_idle_call+0xef/0x191^M [] cpu_idle+0x9e/0xe8^M [] rest_init+0x6d/0x6f^M [] cpu_idle+0x9e/0xe8^M [] rest_init+0x6d/0x6f^M [] start_kernel+0x3ad/0x3ba^M [] ? loglevel+0x31/0x31^M [] x86_64_start_reservations+0xae/0xb2^M [] ? early_idt_handlers+0x140/0x140^M [] x86_64_start_kernel+0x102/0x111^M INFO: task swapper/0:1 blocked for more than 120 seconds.^M "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.^M swapper/0 D ffff8810291383b8 0 1 0 0x00000000^M ffff881029133e20 0000000000000046 ffff881029138000 ffff881029133fd8^M ffff881029133fd8 00000000000132c0 ffff8810292b44d0 ffff881029138000^M 0000000000000246 0000000000000008 ffffffff81a2b2e0 00000000000000d0^M Call Trace:^M [] schedule+0x5f/0x61^M [] async_synchronize_cookie_domain+0xb1/0x10d^M [] ? remove_wait_queue+0x35/0x35^M [] async_synchronize_cookie+0x10/0x12^M [] async_synchronize_full+0x10/0x2c^M [] init_post+0x9/0xc0^M [] kernel_init+0x1c2/0x1c2^M [] ? rdinit_setup+0x28/0x28^M [] kernel_thread_helper+0x4/0x10^M [] ? start_kernel+0x3ba/0x3ba^M [] ? gs_change+0x13/0x13^M INFO: task kworker/u:0:5 blocked for more than 120 seconds.^M