All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Stephan Zimmermann <s.zimmermann@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] fata: removing non-linked element...
Date: Fri, 16 Feb 2007 18:11:31 +0100	[thread overview]
Message-ID: <45D5E5C3.7030508@domain.hid> (raw)
In-Reply-To: <45D59F98.8020006@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]

Stephan Zimmermann wrote:
> Hi again,
> we did some testing with the different verions you told us on some
> different Systems. I will try to sum up what we experienced.
> 
> Testsystems:
> --------------------------------------------
> SMP1 - AMDx2 with Kernel 2.6.19
> SMP2 - AMDx2 with Kernel 2.6.17
> PM1 - Celeron M with Kernel 2.6.17 (ETX Industrial Board)
> PM2 - Pentium M with Kernel 2.6.17 (Notebook)
> 
> Testet revisions where 2077, 2092, 2108, 2184
> 
> The test was running and terminating our application continuously,
> reloading xenomai modules between each start.
> 
> Results:
> --------------------------------------------
> SMP1:
> The application runs as intended. While rebooting the system the kernel
> showed some backtraces according to bad paages. Revision 2184 leads to a
> complete crashed  System like I described in the original mail (2187 on
> Kernel 2.6.20 does that too). It is possible to work around this crash
> by disabling priority coupling (activating the option in kernel config).

I-pipe version? 1.7-00/01 was fragile for me too, 1.7-02 looks fine so
far. This could be one bug, anything on 2.6.17 must be something else.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  parent reply	other threads:[~2007-02-16 17:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 12:12 [Xenomai-help] fata: removing non-linked element Stephan Zimmermann
2007-02-09 12:28 ` Jan Kiszka
2007-02-09 14:04   ` Stephan Zimmermann
2007-02-13 13:36   ` Stephan Zimmermann
2007-02-13 13:42   ` Stephan Zimmermann
2007-02-13 14:07     ` Jan Kiszka
2007-02-13 14:25       ` Philippe Gerum
2007-02-13 14:28         ` Jan Kiszka
2007-02-13 14:47           ` Philippe Gerum
2007-02-13 16:55           ` Philippe Gerum
2007-02-13 18:17             ` Jan Kiszka
2007-02-13 18:58               ` Philippe Gerum
2007-02-16 12:12                 ` Stephan Zimmermann
2007-02-16 17:06                   ` Jan Kiszka
2007-02-16 17:58                     ` Jan Kiszka
2007-02-16 18:15                       ` Philippe Gerum
2007-02-16 18:25                         ` Jan Kiszka
2007-02-16 18:34                           ` Philippe Gerum
2007-02-16 18:38                             ` Jan Kiszka
2007-02-16 18:47                               ` Philippe Gerum
2007-02-22 13:27                                 ` Stephan Zimmermann
2007-02-22 13:50                                   ` Jan Kiszka
2007-02-22 15:49                                     ` Stephan Zimmermann
2007-02-16 17:11                   ` Jan Kiszka [this message]
2007-02-09 13:44 ` Gilles Chanteperdrix
2007-02-09 14:08   ` Stephan Zimmermann

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=45D5E5C3.7030508@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=s.zimmermann@domain.hid \
    --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.