Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266427AbUJLReZ (ORCPT ); Tue, 12 Oct 2004 13:34:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266271AbUJLRGY (ORCPT ); Tue, 12 Oct 2004 13:06:24 -0400 Received: from gateway-1237.mvista.com ([12.44.186.158]:24302 "EHLO av.mvista.com") by vger.kernel.org with ESMTP id S266245AbUJLQ75 (ORCPT ); Tue, 12 Oct 2004 12:59:57 -0400 Subject: Re: [patch] VP-2.6.9-rc4-mm1-T6 From: Daniel Walker Reply-To: dwalker@mvista.com To: linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Organization: MontaVista Message-Id: <1097600394.9548.1.camel@dhcp153.mvista.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-4) Date: 12 Oct 2004 09:59:55 -0700 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1341 Lines: 36 On Tue, 2004-10-12 at 09:39, Mark_H_Johnson@raytheon.com wrote: > Had to cycle power to get the machine back. Rebooting with max_cpus=1 > crashed in a different way. Was able to get past mounting the disks and > some of the init script items before stopping at the same location with > a different call trace: > > Call Trace: > [] scheduler_tick+0x148/0x490 > [] update_process_times+0x43/0x60 > [] mcount+0x14/0x18 > [] update_process_times_0x4f/0x60 > [] smp_apic_timer_interrupt+0xe1/0xf0 > [] scheduler_tick+0x16e/0x490 > [] apic_timer_interrupt+0x1a/0x20 > [] unix_stream_recvmsg+0x5b/0x450 > [] scheduler_tick+0x16e/0x490 > [] update_process_times+0x43/0x60 > [] mcount+0x14/0x18 > [] update_process_times+0x4f/0x60 > [] smp_apic_timer_interrupt+0xe1/0xf0 > [] release_console_sem+0x64/0xe0 > [] printk+0x1d/0x30 Do you have hyper threading turned on? Seems like I've seen this trace a few times before.. Daniel Walker - 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/