Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762253AbWLJWrQ (ORCPT ); Sun, 10 Dec 2006 17:47:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761978AbWLJWrQ (ORCPT ); Sun, 10 Dec 2006 17:47:16 -0500 Received: from mail.atl.external.lmco.com ([192.35.37.50]:44935 "EHLO enterprise.atl.lmco.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1762253AbWLJWrO (ORCPT ); Sun, 10 Dec 2006 17:47:14 -0500 Message-ID: <457C8E74.9090301@atl.lmco.com> Date: Sun, 10 Dec 2006 17:47:16 -0500 From: Gautam Thaker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rui Nuno Capela Cc: Ingo Molnar , linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org Subject: Re: 2.6.19-rt11 boot failure References: <60535.192.168.1.8.1165699722.squirrel@www.rncbc.org> In-Reply-To: <60535.192.168.1.8.1165699722.squirrel@www.rncbc.org> Content-Type: multipart/mixed; boundary="------------000005040100020107090600" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3534 Lines: 109 This is a multi-part message in MIME format. --------------000005040100020107090600 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I see the attached two messages on the console output. In one case for me 2.6.19-rt11 seemed to boot ok, in other case it do not seem to. I am not sure if this problem is related to disabled HPET, but I will try that also. Gautam --------------000005040100020107090600 Content-Type: text/plain; name="2.6.19-rt11.bug.1" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="2.6.19-rt11.bug.1" Kernel 2.6.19-rt11-UNI on an i686 a.simple-2-nodes.corbatests.emulab.net login: softirq-timer/0/4[CPU#0]: BUG in update_wall_time0 [] dump_trace+0x69/0x1ac [] show_trace_log_lvl+0x17/0x2b [] pmap_getport_ops+0xbc5/0x5df00 DWARF2 unwinder stuck at pmap_getport_ops+0xbc5/0x5df00 Leftover inexact backtrace: [] show_trace+0xf/0x11 [] dump_stack+0x13/0x15 [] __WARN_ON+0x5b/0x89 [] run_timer_softirq+0xd8/0xb21 [] __switch_to+0x19/0x182 [] posix_cpu_timers_thread+0x0/0xc3 [] preempt_schedule_irq+0x37/0x58 [] ksoftirqd+0x0/0x179 [] schedule+0xc6/0xe2 [] ksoftirqd+0x0/0x179 [] ksoftirqd+0xeb/0x179 [] kthread+0xac/0xda [] kthread+0x0/0xda [] kernel_thread_helper+0x7/0x10 ======================= Fedora Core release 4 (Stentz) Kernel 2.6.19-rt11-UNI on an i686 a.simple-2-nodes.corbatests.emulab.net login: --------------000005040100020107090600 Content-Type: text/plain; name="2.6.19-rt11.bug.2" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="2.6.19-rt11.bug.2" Boot Complete Fedora Core release 4 (Stentz) Kernel 2.6.19-rt11-UNI on an i686 a.simple-2-nodes.corbatests.emulab.net login: softirq-timer/0/4[CPU#0]: BUG in update_wall_time0 [] dump_trace+0x69/0x1ac [] show_trace_log_lvl+0x17/0x2b [] pmap_getport_ops+0xbc5/0x5df00 DWARF2 unwinder stuck at pmap_getport_ops+0xbc5/0x5df00 Leftover inexact backtrace: [] show_trace+0xf/0x11 [] dump_stack+0x13/0x15 [] __WARN_ON+0x5b/0x89 [] run_timer_softirq+0xd8/0xb21 [] posix_cpu_timers_thread+0x0/0xc3 [] __switch_to+0x19/0x182 [] posix_cpu_timers_thread+0x0/0xc3 [] ksoftirqd+0x0/0x179 [] schedule+0xc6/0xe2 [] ksoftirqd+0x0/0x179 [] ksoftirqd+0xeb/0x179 [] kthread+0xac/0xda [] kthread+0x0/0xda [] kernel_thread_helper+0x7/0x10 ======================= BUG: time warp detected! prev > now, 1d2da428324317aa > e312d9e1df154b25: = 4186881206986329221 delta, on CPU#0 [] dump_trace+0x69/0x1ac [] show_trace_log_lvl+0x17/0x2b [] pmap_getport_ops+0xbc5/0x5df00 DWARF2 unwinder stuck at pmap_getport_ops+0xbc5/0x5df00 Leftover inexact backtrace: [] show_trace+0xf/0x11 [] dump_stack+0x13/0x15 [] do_gettimeofday+0x151/0x17f [] sys_time+0x9/0x2d [] sysenter_past_esp+0x56/0x79 ======================= --------------000005040100020107090600-- - 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/