From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] latency -t 1 crashes on SMP.
Date: Sun, 09 Apr 2006 17:07:41 +0200 [thread overview]
Message-ID: <4439233D.4050800@domain.hid> (raw)
In-Reply-To: <17465.8101.106079.634470@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
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.
>
> The lock up does not seem to be detected by any Xenomai or Linux
> debug or watchdog. Only enabling the NMI watchdog seems to
> systematically produce the exception 14 instead of the lockup.
>
> I ve tried to put a printk at the beginning of timer_task_proc outer
> loop. It get printed once when getting the exception 14, and twice when
> getting the lock up.
>
> Any idea where to look ?
>
Two proposals to collect information:
o give KGDB a try
o instrument the xenomai exception handler with an ipipe_trace_freeze()
(something which should be merged into SVN later)
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-04-09 15:07 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 [this message]
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
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=4439233D.4050800@domain.hid \
--to=jan.kiszka@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.