From: Gautam Thaker <gthaker@atl.lmco.com>
To: Rui Nuno Capela <rncbc@rncbc.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: 2.6.19-rt11 boot failure
Date: Sun, 10 Dec 2006 17:47:16 -0500 [thread overview]
Message-ID: <457C8E74.9090301@atl.lmco.com> (raw)
In-Reply-To: <60535.192.168.1.8.1165699722.squirrel@www.rncbc.org>
[-- Attachment #1: Type: text/plain, Size: 235 bytes --]
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
[-- Attachment #2: 2.6.19-rt11.bug.1 --]
[-- Type: text/plain, Size: 1005 bytes --]
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
[<c0104c54>] dump_trace+0x69/0x1ac
[<c0104dae>] show_trace_log_lvl+0x17/0x2b
[<c041e7f9>] pmap_getport_ops+0xbc5/0x5df00
DWARF2 unwinder stuck at pmap_getport_ops+0xbc5/0x5df00
Leftover inexact backtrace:
[<c01050fc>] show_trace+0xf/0x11
[<c0105111>] dump_stack+0x13/0x15
[<c011bf16>] __WARN_ON+0x5b/0x89
[<c01237ce>] run_timer_softirq+0xd8/0xb21
[<c0102ed6>] __switch_to+0x19/0x182
[<c012d5cc>] posix_cpu_timers_thread+0x0/0xc3
[<c03feec9>] preempt_schedule_irq+0x37/0x58
[<c011f968>] ksoftirqd+0x0/0x179
[<c03ff378>] schedule+0xc6/0xe2
[<c011f968>] ksoftirqd+0x0/0x179
[<c011fa53>] ksoftirqd+0xeb/0x179
[<c012bbbe>] kthread+0xac/0xda
[<c012bb12>] kthread+0x0/0xda
[<c01049f3>] 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:
[-- Attachment #3: 2.6.19-rt11.bug.2 --]
[-- Type: text/plain, Size: 1465 bytes --]
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
[<c0104c54>] dump_trace+0x69/0x1ac
[<c0104dae>] show_trace_log_lvl+0x17/0x2b
[<c041e7f9>] pmap_getport_ops+0xbc5/0x5df00
DWARF2 unwinder stuck at pmap_getport_ops+0xbc5/0x5df00
Leftover inexact backtrace:
[<c01050fc>] show_trace+0xf/0x11
[<c0105111>] dump_stack+0x13/0x15
[<c011bf16>] __WARN_ON+0x5b/0x89
[<c01237ce>] run_timer_softirq+0xd8/0xb21
[<c012d5cc>] posix_cpu_timers_thread+0x0/0xc3
[<c0102ed6>] __switch_to+0x19/0x182
[<c012d5cc>] posix_cpu_timers_thread+0x0/0xc3
[<c011f968>] ksoftirqd+0x0/0x179
[<c03ff378>] schedule+0xc6/0xe2
[<c011f968>] ksoftirqd+0x0/0x179
[<c011fa53>] ksoftirqd+0xeb/0x179
[<c012bbbe>] kthread+0xac/0xda
[<c012bb12>] kthread+0x0/0xda
[<c01049f3>] kernel_thread_helper+0x7/0x10
=======================
BUG: time warp detected!
prev > now, 1d2da428324317aa > e312d9e1df154b25:
= 4186881206986329221 delta, on CPU#0
[<c0104c54>] dump_trace+0x69/0x1ac
[<c0104dae>] show_trace_log_lvl+0x17/0x2b
[<c041e7f9>] pmap_getport_ops+0xbc5/0x5df00
DWARF2 unwinder stuck at pmap_getport_ops+0xbc5/0x5df00
Leftover inexact backtrace:
[<c01050fc>] show_trace+0xf/0x11
[<c0105111>] dump_stack+0x13/0x15
[<c01232fe>] do_gettimeofday+0x151/0x17f
[<c011f001>] sys_time+0x9/0x2d
[<c0103e49>] sysenter_past_esp+0x56/0x79
=======================
prev parent reply other threads:[~2006-12-10 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 21:28 2.6.19-rt11 boot failure Rui Nuno Capela
2006-12-09 21:37 ` Thomas Gleixner
2006-12-10 0:54 ` Rui Nuno Capela
2006-12-10 8:02 ` Ingo Molnar
2006-12-10 22:47 ` Gautam Thaker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=457C8E74.9090301@atl.lmco.com \
--to=gthaker@atl.lmco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rncbc@rncbc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox