2.6.20-rc6-rt1 timekeeping_is_continuous question

["Rui Nuno Capela" <rncbc@rncbc.org>]

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
-
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/