From: "Rui Nuno Capela" <rncbc@rncbc.org>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: 2.6.20-rc6-rt1 timekeeping_is_continuous question
Date: Thu, 25 Jan 2007 11:36:47 -0000 (WET) [thread overview]
Message-ID: <11401.194.65.103.1.1169725008.squirrel@www.rncbc.org> (raw)
Hi,
I'm having the following traces on every boot; are they of any concern, or
should I just ignore and carry on?
(machine is an Intel Core2 Duo T7200 2.0Ghz laptop)
Linux version 2.6.20-rc6-rt1.0 (root@zeta) (gcc version 4.1.2 20061115
(prerelease) (SUSE Linux)) #1 SMP PREEMPT Thu Jan 25 10:02:28 WET 2007
[...]
Total of 2 processors activated (7985.17 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
timekeeping_is_continuous(jiffies): 0
[<c0105068>] dump_trace+0x63/0x1ec
[<c010520b>] show_trace_log_lvl+0x1a/0x2f
[<c0105836>] show_trace+0x12/0x14
[<c01058c9>] dump_stack+0x16/0x18
[<c012715f>] timekeeping_is_continuous+0x58/0x60
[<c0135c71>] tick_check_oneshot_change+0x3e/0x111
[<c013220b>] hrtimer_run_queues+0x40/0x26a
[<c012680b>] run_timer_softirq+0x785/0x975
[<c012313a>] ksoftirqd+0xfd/0x1a2
[<c012f947>] kthread+0xb5/0xde
[<c0104c33>] kernel_thread_helper+0x7/0x10
=======================
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Brought up 2 CPUs
timekeeping_is_continuous(jiffies): 0
[<c0105068>] dump_trace+0x63/0x1ec
[<c010520b>] show_trace_log_lvl+0x1a/0x2f
[<c0105836>] show_trace+0x12/0x14
[<c01058c9>] dump_stack+0x16/0x18
[<c012715f>] timekeeping_is_continuous+0x58/0x60
[<c0135c71>] tick_check_oneshot_change+0x3e/0x111
[<c013220b>] hrtimer_run_queues+0x40/0x26a
[<c012680b>] run_timer_softirq+0x785/0x975
[<c012313a>] ksoftirqd+0xfd/0x1a2
[<c012f947>] kthread+0xb5/0xde
[<c0104c33>] kernel_thread_helper+0x7/0x10
=======================
migration_cost=34
Booting paravirtualized kernel on bare hardware
[...]
Time: tsc clocksource has been installed.
timekeeping_is_continuous(tsc): 0
[<c0105068>] dump_trace+0x63/0x1ec
[<c010520b>] show_trace_log_lvl+0x1a/0x2f
[<c0105836>] show_trace+0x12/0x14
[<c01058c9>] dump_stack+0x16/0x18
[<c012715f>] timekeeping_is_continuous+0x58/0x60
[<c0135c71>] tick_check_oneshot_change+0x3e/0x111
[<c013220b>] hrtimer_run_queues+0x40/0x26a
[<c012680b>] run_timer_softirq+0x785/0x975
[<c012313a>] ksoftirqd+0xfd/0x1a2
[<c012f947>] kthread+0xb5/0xde
[<c0104c33>] kernel_thread_helper+0x7/0x10
=======================
timekeeping_is_continuous(tsc): 0
[<c0105068>] dump_trace+0x63/0x1ec
[<c010520b>] show_trace_log_lvl+0x1a/0x2f
[<c0105836>] show_trace+0x12/0x14
[<c01058c9>] dump_stack+0x16/0x18
[<c012715f>] timekeeping_is_continuous+0x58/0x60
[<c0135c71>] tick_check_oneshot_change+0x3e/0x111
[<c013220b>] hrtimer_run_queues+0x40/0x26a
[<c012680b>] run_timer_softirq+0x785/0x975
[<c012313a>] ksoftirqd+0xfd/0x1a2
[<c012f947>] kthread+0xb5/0xde
[<c0104c33>] kernel_thread_helper+0x7/0x10
=======================
Write protecting the kernel read-only data: 794k
timekeeping_is_continuous(tsc): 1
timekeeping_is_continuous(tsc): 1
[<c0105068>] dump_trace+0x63/0x1ec
[<c010520b>] show_trace_log_lvl+0x1a/0x2f
[<c0105836>] show_trace+0x12/0x14
[<c01058c9>] dump_stack+0x16/0x18
[<c012715f>] timekeeping_is_continuous+0x58/0x60
[<c0135c71>] tick_check_oneshot_change+0x3e/0x111
[<c013220b>] hrtimer_run_queues+0x40/0x26a
[<c012680b>] run_timer_softirq+0x785/0x975
[<c012313a>] ksoftirqd+0xfd/0x1a2
[<c012f947>] kthread+0xb5/0xde
[<c0104c33>] kernel_thread_helper+0x7/0x10
=======================
Switched to high resolution mode on CPU 1
[<c0105068>] dump_trace+0x63/0x1ec
[<c010520b>] show_trace_log_lvl+0x1a/0x2f
[<c0105836>] show_trace+0x12/0x14
[<c01058c9>] dump_stack+0x16/0x18
[<c012715f>] timekeeping_is_continuous+0x58/0x60
[<c0135c71>] tick_check_oneshot_change+0x3e/0x111
[<c013220b>] hrtimer_run_queues+0x40/0x26a
[<c012680b>] run_timer_softirq+0x785/0x975
[<c012313a>] ksoftirqd+0xfd/0x1a2
[<c012f947>] kthread+0xb5/0xde
[<c0104c33>] kernel_thread_helper+0x7/0x10
=======================
Switched to high resolution mode on CPU 0
[...]
Bye.
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
next reply other threads:[~2007-01-25 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 11:36 Rui Nuno Capela [this message]
2007-01-25 12:36 ` Ingo Molnar
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=11401.194.65.103.1.1169725008.squirrel@www.rncbc.org \
--to=rncbc@rncbc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®