All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [bug] don't try this at home...
Date: Wed, 30 Nov 2005 18:29:10 +0100	[thread overview]
Message-ID: <438DE166.5090303@domain.hid> (raw)
In-Reply-To: <438DD4E2.9080208@domain.hid>

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

Jan Kiszka wrote:
> Hi Philippe,
> 
> I'm afraid this one is serious: let the attached migration stress test
> run on likely any Xenomai since 2.0, preferably with
> CONFIG_XENO_OPT_DEBUG on. Will give a nice crash sooner or later (I'm
> trying to set up a serial console now).
> 

As it took some time to persuade my box to not just reboot but to give a
message, I'm posting here the kernel dump of the P-III running
nat_migration:

[...]
Xenomai: starting native API services.
ce649fb4 ce648000 00000b17 00000202 c0139246 cdf2819c cdf28070 0b12d310
       00000037 ce648000 00000000 c02f0700 00009a28 00000000 b7e94a70
bfed63c8
       00000000 ce648000 c0102fcb b7e94a70 bfed63dc b7faf4b0 bfed63c8
00000000
Call Trace:
 [<c0139246>] __ipipe_dispatch_event+0x96/0x130
 [<c0102fcb>] work_resched+0x6/0x1c
Xenomai: fatal: blocked thread migration[22175] rescheduled?!
(status=0x300010, sig=0, prev=watchdog/0[3])
 CPU  PID    PRI  TIMEOUT  STAT      NAME
>  0  0      0    0        00500080  ROOT
   0  22175  1    0        00300110  migration
Timer: none

cea05ee4 d0842c62 cdcb0000 cea6d030 c02f0700 c035cbec c02f0700 00000286
       c0139246 00000022 c02f0700 cdf28070 cdf28070 00000022 00000001
c02f0700
       cea6d030 cdf28070 cea6d158 cea05f78 c02b26c0 cea04000 00000238
d1244537
Call Trace:
 [<c0139246>] __ipipe_dispatch_event+0x96/0x130
 [<c02b26c0>] schedule+0x2d0/0x720
 [<c0137b20>] watchdog+0x0/0x80
 [<c02b3967>] schedule_timeout+0x47/0xb0
 [<c0120070>] process_timeout+0x0/0x10
 [<c0120492>] msleep_interruptible+0x42/0x60
 [<c0137b70>] watchdog+0x50/0x80
 [<c012d0ab>] kthread+0x8b/0x90
 [<c012d020>] kthread+0x0/0x90
 [<c0100ef5>] kernel_thread_helper+0x5/0x10


Jan


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

  reply	other threads:[~2005-11-30 17:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30 16:35 [Xenomai-core] [bug] don't try this at home Jan Kiszka
2005-11-30 17:29 ` Jan Kiszka [this message]
2005-11-30 17:45   ` Philippe Gerum
2005-12-07 12:50     ` Jan Kiszka
2005-12-07 13:08       ` Philippe Gerum
2005-12-07 17:44         ` Jan Kiszka
2005-12-09 12:53           ` Philippe Gerum
2005-12-16 20:26     ` Philippe Gerum
2005-12-16 20:56       ` Philippe Gerum
2005-12-16 23:36         ` Philippe Gerum
2005-12-18 13:55           ` Jan Kiszka
2005-12-18 18:30             ` Philippe Gerum
2005-12-18 18:59               ` Jan Kiszka
2005-12-18 19:19                 ` Philippe Gerum
2005-12-22 15:05               ` Jan Kiszka

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=438DE166.5090303@domain.hid \
    --to=kiszka@domain.hid \
    --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.