From: Tamas Szklenar <tszklenar@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Xenomai failure
Date: Tue, 04 Jan 2011 16:37:05 -0500 [thread overview]
Message-ID: <4D239301.80803@domain.hid> (raw)
In-Reply-To: <4D239001.9050604@domain.hid>
Hi Gilles,
Sure here is the output:
~$ cat /proc/timer_list
Timer List Version: v0.6
HRTIMER_MAX_CLOCK_BASES: 2
now at 292297967595 nsecs
cpu: 0
clock 0:
.base: ffff880001a0e838
.index: 0
.resolution: 4000250 nsecs
.get_time: ktime_get_real
active timers:
clock 1:
.base: ffff880001a0e870
.index: 1
.resolution: 4000250 nsecs
.get_time: ktime_get
active timers:
#0: <ffff88020a665ac8>, hrtimer_wakeup, S:01
# expires at 308624130994-308654130993 nsecs [in 16326163399 to
16356163398 nsecs]
cpu: 1
clock 0:
.base: ffff880001a4e838
.index: 0
.resolution: 4000250 nsecs
.get_time: ktime_get_real
active timers:
clock 1:
.base: ffff880001a4e870
.index: 1
.resolution: 4000250 nsecs
.get_time: ktime_get
active timers:
#0: <ffffffff81750bf8>, sched_rt_period_timer, S:01
# expires at 293000000000-293000000000 nsecs [in 702032405 to
702032405 nsecs]
#1: <ffff8802086af9a8>, hrtimer_wakeup, S:01
# expires at 293173168132-293174168131 nsecs [in 875200537 to
876200536 nsecs]
#2: <ffff8802086559a8>, hrtimer_wakeup, S:01
# expires at 1013712348906-1013812348906 nsecs [in 721414381311 to
721514381311 nsecs]
cpu: 2
clock 0:
.base: ffff880001a8e838
.index: 0
.resolution: 4000250 nsecs
.get_time: ktime_get_real
active timers:
clock 1:
.base: ffff880001a8e870
.index: 1
.resolution: 4000250 nsecs
.get_time: ktime_get
active timers:
#0: <ffff88020a771ac8>, hrtimer_wakeup, S:01
# expires at 292503107490-292503637489 nsecs [in 205139895 to
205669894 nsecs]
#1: <ffff88020fc8b9a8>, hrtimer_wakeup, S:01
# expires at 292524960948-292529960947 nsecs [in 226993353 to
231993352 nsecs]
#2: <ffff88020e888958>, posix_timer_fn, S:01
# expires at 293134262249-293134262249 nsecs [in 836294654 to
836294654 nsecs]
#3: <ffff88020d1e39a8>, hrtimer_wakeup, S:01
# expires at 315876197364-315906197363 nsecs [in 23578229769 to
23608229768 nsecs]
#4: <ffff88020857fed8>, hrtimer_wakeup, S:01
# expires at 338648664865-338648714865 nsecs [in 46350697270 to
46350747270 nsecs]
#5: <ffff88020d192470>, it_real_fn, S:01
# expires at 1816696421423-1816696421423 nsecs [in 1524398453828 to
1524398453828 nsecs]
#6: <ffff88020a761ed8>, hrtimer_wakeup, S:01
# expires at 3613091023499-3613091073499 nsecs [in 3320793055904 to
3320793105904 nsecs]
#7: <ffff88020a63b9a8>, hrtimer_wakeup, S:01
# expires at 86411067787013-86411167787013 nsecs [in 86118769819418 to
86118869819418 nsecs]
cpu: 3
clock 0:
.base: ffff880001ace838
.index: 0
.resolution: 4000250 nsecs
.get_time: ktime_get_real
active timers:
#0: <ffff88020d00fd68>, hrtimer_wakeup, S:01
# expires at 1294176961287775295-1294176961287825295 nsecs [in
1294176668989807700 to 1294176668989857700 nsecs]
clock 1:
.base: ffff880001ace870
.index: 1
.resolution: 4000250 nsecs
.get_time: ktime_get
active timers:
#0: <ffff8802085999a8>, hrtimer_wakeup, S:01
# expires at 293101174531-293102174530 nsecs [in 803206936 to
804206935 nsecs]
#1: <ffff88020a7299a8>, hrtimer_wakeup, S:01
# expires at 293165117088-293166117087 nsecs [in 867149493 to
868149492 nsecs]
#2: <ffff88020e95b9a8>, hrtimer_wakeup, S:01
# expires at 296121072213-296126072212 nsecs [in 3823104618 to
3828104617 nsecs]
Tick Device: mode: 0
Broadcast device
Clock Event Device: pit
max_delta_ns: 27461866
min_delta_ns: 12571
mult: 5124677
shift: 32
mode: 2
next_event: 9223372036854775807 nsecs
set_next_event: pit_next_event
set_mode: init_pit_timer
event_handler: tick_handle_periodic_broadcast
retries: 0
tick_broadcast_mask: 0000000f
Tick Device: mode: 0
Per CPU device: 0
Clock Event Device: lapic
max_delta_ns: 668154819
min_delta_ns: 1194
mult: 53922821
shift: 32
mode: 1
next_event: 9223372036854775807 nsecs
set_next_event: lapic_next_event
set_mode: lapic_timer_setup
event_handler: tick_handle_periodic
retries: 0
Tick Device: mode: 0
Per CPU device: 1
Clock Event Device: lapic
max_delta_ns: 668154819
min_delta_ns: 1194
mult: 53922821
shift: 32
mode: 1
next_event: 9223372036854775807 nsecs
set_next_event: lapic_next_event
set_mode: lapic_timer_setup
event_handler: tick_handle_periodic
retries: 0
Tick Device: mode: 0
Per CPU device: 2
Clock Event Device: lapic
max_delta_ns: 668154819
min_delta_ns: 1194
mult: 53922821
shift: 32
mode: 1
next_event: 9223372036854775807 nsecs
set_next_event: lapic_next_event
set_mode: lapic_timer_setup
event_handler: tick_handle_periodic
retries: 0
Tick Device: mode: 0
Per CPU device: 3
Clock Event Device: lapic
max_delta_ns: 668154819
min_delta_ns: 1194
mult: 53922821
shift: 32
mode: 1
next_event: 9223372036854775807 nsecs
set_next_event: lapic_next_event
set_mode: lapic_timer_setup
event_handler: tick_handle_periodic
retries: 0
next prev parent reply other threads:[~2011-01-04 21:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 15:20 [Xenomai-help] Xenomai failure Tamas Szklenar
2011-01-04 17:03 ` Stefan Kisdaroczi
2011-01-04 19:40 ` Tamas Szklenar
2011-01-04 19:43 ` Gilles Chanteperdrix
2011-01-04 19:50 ` Tamas Szklenar
2011-01-04 19:52 ` Gilles Chanteperdrix
2011-01-04 19:55 ` Gilles Chanteperdrix
2011-01-04 20:04 ` Tamas Szklenar
2011-01-04 20:12 ` Gilles Chanteperdrix
2011-01-04 20:01 ` Tamas Szklenar
2011-01-04 20:13 ` Gilles Chanteperdrix
2011-01-04 20:23 ` Tamas Szklenar
2011-01-04 21:08 ` Gilles Chanteperdrix
2011-01-04 21:18 ` Tamas Szklenar
2011-01-04 21:24 ` Gilles Chanteperdrix
2011-01-04 21:37 ` Tamas Szklenar [this message]
2011-01-04 21:52 ` Gilles Chanteperdrix
2011-01-05 0:27 ` Tamas Szklenar
2011-01-04 21:19 ` Tamas Szklenar
2011-01-04 21:38 ` Philippe Gerum
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=4D239301.80803@domain.hid \
--to=tszklenar@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.