From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] latency -t 1 crashes on SMP.
Date: Tue, 11 Apr 2006 18:02:24 +0200 [thread overview]
Message-ID: <17467.54032.226274.987236@domain.hid> (raw)
In-Reply-To: <4439791B.7060003@domain.hid>
Philippe Gerum wrote:
> Gilles Chanteperdrix wrote:
> > I tried latency -t 1 on an SMP machines, and observed a very
> > reproducible crash. Most of the time, the machine locks up
> > completely. The rest of the time, I get :
> >
> > Xenomai: suspending kernel thread e7559044 ('timerbench') at 0xb01051f2 after ex
> > ception #14
> >
> > And the system remains runnable, but 0xb01051f2 is not a valid kernel
> > module text address.
>
> Looks like a kernel-based task stack address on x86.
Actually, this address really is a kernel text address, because I use
the CONFIG_VMSPLIT_3G_OPT, which seems a way to configure a machine with
1GB RAM. The crash also happens with CONFIG_VMSPLIT_3G, but the text
address is 0xc01051f2.
I tried adding a call to show_stack() in xnpod_fault_handler, and it
shows that the crash happens right after the call to rthal_nmi_arm in
xnarch_program_timer_shot:
Xenomai: suspending kernel thread eeed5044 ('timerbench') at 0xc01051f2 after ex
ception #14
ee8c1768 c02d24c1 ee8c1798 f8ff868c 00000000 00000000 eeed53b0 c01051f2
0000000e bfa49f69 58454e4f 0000000e ee8c17a4 f900aca1 ee8c17b0 ee8c17c0
f8ff57b3 ee8c17b0 0000000e ffffffff ee8c183c 00000082 ee8c17dc c0259df0
Call Trace:
[<c0103f6a>] show_stack_log_lvl+0xaa/0xe0
[<c0103fc1>] show_stack+0x21/0x30
[<f8ff868c>] xnpod_fault_handler+0x8c/0x220 [xeno_nucleus]
[<f900aca1>] xnpod_trap_fault+0x61/0x70 [xeno_nucleus]
[<f8ff57b3>] xnarch_trap_fault+0x23/0x30 [xeno_nucleus]
[<c0259df0>] exception_event+0x70/0x80
[<c0142103>] __ipipe_dispatch_event+0x103/0x130
[<c01140ea>] __ipipe_handle_exception+0x2a/0xf0
[<c0103b7c>] error_code+0x54/0x64
[<c0103c42>] nmi_stack_correct+0x1d/0x22
[<f9015141>] xntimer_do_start_aperiodic+0x441/0x560 [xeno_nucleus]
[<f901a380>] xntimer_start+0x130/0x350 [xeno_nucleus]
[<f8ffe4ed>] xnpod_suspend_thread+0x7ad/0xd40 [xeno_nucleus]
[<f8f82749>] rtdm_task_sleep_until+0x179/0x3d0 [xeno_rtdm]
[<f8e83456>] timer_task_proc+0x1c6/0x450 [xeno_timerbench]
[<f8ff7f5d>] xnarch_thread_redirect+0x5d/0x80 [xeno_nucleus]
[<00000000>] _stext+0x3feffd68/0x8
And now the most interesting: when compiling Xenomai in the kernel,
(which moves Xenomai code out of vmalloc'ed memory) the bug disappears.
--
Gilles Chanteperdrix.
prev parent reply other threads:[~2006-04-11 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 14:52 [Xenomai-core] latency -t 1 crashes on SMP Gilles Chanteperdrix
2006-04-09 15:07 ` Jan Kiszka
2006-04-13 13:35 ` Gilles Chanteperdrix
2006-04-13 13:48 ` Jan Kiszka
2006-04-13 15:34 ` Gilles Chanteperdrix
2006-04-09 21:14 ` Philippe Gerum
2006-04-11 16:02 ` Gilles Chanteperdrix [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=17467.54032.226274.987236@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=rpm@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.