LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* 2.6.20-rc6-rt1 timekeeping_is_continuous question
@ 2007-01-25 11:36 Rui Nuno Capela
2007-01-25 12:36 ` Ingo Molnar
0 siblings, 1 reply; 2+ messages in thread
From: Rui Nuno Capela @ 2007-01-25 11:36 UTC (permalink / raw)
To: Ingo Molnar; +Cc: linux-rt-users, linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: 2.6.20-rc6-rt1 timekeeping_is_continuous question
2007-01-25 11:36 2.6.20-rc6-rt1 timekeeping_is_continuous question Rui Nuno Capela
@ 2007-01-25 12:36 ` Ingo Molnar
0 siblings, 0 replies; 2+ messages in thread
From: Ingo Molnar @ 2007-01-25 12:36 UTC (permalink / raw)
To: Rui Nuno Capela; +Cc: linux-rt-users, linux-kernel
* Rui Nuno Capela <rncbc@rncbc.org> wrote:
> I'm having the following traces on every boot; are they of any
> concern, or should I just ignore and carry on?
please ignore them - i've removed them from the current tree.
Ingo
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-01-25 12:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-01-25 11:36 2.6.20-rc6-rt1 timekeeping_is_continuous question Rui Nuno Capela
2007-01-25 12:36 ` Ingo Molnar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).