All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Morris <john@zultron.com>
To: Xenomai <xenomai@xenomai.org>
Subject: [Xenomai] Kernel OOPS during regression tests
Date: Sat, 12 Jan 2013 11:26:57 -0600	[thread overview]
Message-ID: <50F19CE1.5080106@zultron.com> (raw)

Hi list,

The el6 packages are coming along nicely:

https://github.com/zultron/kernel-ml/tree/branch3.5.3-xeno

Still a few problems when running xeno-regression-test.

1)  Most worrisome is "kernel BUG at mm/mmap.c:2313!   invalid opcode:
0000 [#2] SMP".  Is this related to HEAPSZ or STACKPOOLSZ?  My mind is
getting foggy about all the things I've seen, but it seems like it was
happening earlier in the tests until these config values were quadrupled.

2)  posix/mprotect is failing:  "FAILURE: sigdebug_handler triggered,
reason 2    memory write after exec enable".

3)  FPU warning:  "fptest.h:24: Warning: Linux is compiled to use FPU in
kernel-space.    For this reason, switchtest can not test using FPU in
Linux kernel-space."

Regression test run log:
http://www.zultron.com/static/2013/01/xenomai/foo-xeno-regression-test.log

Log of dmesg with oops at end:
http://www.zultron.com/static/2013/01/xenomai/foo-oops.log

Kernel .config:
www.zultron.com/static/2013/01/xenomai/foo-kernel.config

The kernel is built from the elrepo.org kernel, and this config file
overrides the upstream config; makes it easy to see the Xenomai-specific
changes:
https://github.com/zultron/kernel-ml/blob/branch3.5.3-xeno/config-3.5.3-xenomai-x86_64

Any help is greatly appreciated!  These RPMs are part of my effort to
enable RH-like distros to run LinuxCNC and expand the pool of potential
users, so if I'm successful, many folks will benefit.

	John


             reply	other threads:[~2013-01-12 17:26 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12 17:26 John Morris [this message]
2013-01-12 17:31 ` [Xenomai] Kernel OOPS during regression tests Gilles Chanteperdrix
2013-01-13  4:36   ` John Morris
2013-01-13 12:16     ` Gilles Chanteperdrix
2013-01-13 19:14       ` [Xenomai] 3.5.7 "I-pipe: could not find timer" (Was: Re: Kernel OOPS during regression tests) John Morris
2013-01-13 19:41         ` Gilles Chanteperdrix
2013-01-14  4:47           ` [Xenomai] 3.5.7 posix/mprotect failure; "I-pipe: could not find timer" fixed! John Morris
2013-01-14 11:57             ` Gilles Chanteperdrix
2013-01-14 12:00               ` Jan Kiszka
2013-01-14 13:36                 ` Jan Kiszka
2013-01-14 20:52                   ` John Morris
2013-01-14 22:54                     ` Gilles Chanteperdrix
2013-01-15  7:16                       ` [Xenomai] 3.5.7 posix/mprotect fixed; (Was: posix/mprotect failure) John Morris
2013-01-15  7:31                         ` Gilles Chanteperdrix
2013-01-18  3:56                           ` John Morris
2013-01-18  4:31                             ` Gilles Chanteperdrix
2013-01-14 19:50             ` [Xenomai] 3.5.7 posix/mprotect failure; "I-pipe: could not find timer" fixed! Gilles Chanteperdrix
2013-01-14 20:56               ` John Morris
2013-01-14 22:57                 ` Gilles Chanteperdrix
2013-01-14 12:00           ` [Xenomai] 3.5.7 "I-pipe: could not find timer" (Was: Re: Kernel OOPS during regression tests) Jan Kiszka
2013-01-14 18:50             ` Gilles Chanteperdrix
2013-01-14 19:13               ` Jan Kiszka
2013-01-14 19:15                 ` Gilles Chanteperdrix
2013-01-14 19:37                   ` Jan Kiszka
2013-01-14 20:39                     ` Gilles Chanteperdrix
2013-01-15 11:35                       ` Jan Kiszka
2013-01-15 12:06                         ` Gilles Chanteperdrix
2013-01-15 12:09                           ` Philippe Gerum
2013-01-15 12:21                             ` Jan Kiszka
2013-01-15 13:44                               ` Philippe Gerum
2013-01-15 13:48                                 ` Jan Kiszka
2013-01-15 13:58                                   ` Philippe Gerum
2013-01-15 14:10                                     ` Jan Kiszka
2013-01-15 19:39                                     ` Gilles Chanteperdrix
2013-01-16  8:02                                       ` Jan Kiszka
2013-01-16  8:44                                         ` Jan Kiszka
2013-01-16  9:41                                           ` Philippe Gerum
2013-01-16  9:48                                             ` Jan Kiszka
2013-01-16 10:37                                               ` Philippe Gerum
2013-01-16 12:03                                                 ` Gilles Chanteperdrix
2013-01-16 12:18                                                   ` Jan Kiszka
2013-01-15 13:59                                   ` Jan Kiszka
2013-01-12 19:02 ` [Xenomai] Kernel OOPS during regression tests Gilles Chanteperdrix
2013-01-13  6:50   ` John Morris
2013-01-13 11:23     ` Jan Kiszka
2013-01-13 12:18       ` Gilles Chanteperdrix
2013-01-13 19:34         ` [Xenomai] 3.5.3 posix/mprotect fail "sigdebug_handler triggered" (Was: Re: Kernel OOPS during regression tests) John Morris
2013-01-13 19:42           ` Gilles Chanteperdrix
2013-01-12 19:03 ` [Xenomai] Kernel OOPS during regression tests Gilles Chanteperdrix
2013-01-13  4:40   ` John Morris
2013-01-13 13:53     ` Gilles Chanteperdrix
2013-01-13 19:36       ` [Xenomai] SMI workarounds in one-size-fits-all kernel packages (Was: Re: Kernel OOPS during regression tests) John Morris
2013-01-13 19:45         ` Gilles Chanteperdrix
2013-01-14  5:33           ` John Morris

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=50F19CE1.5080106@zultron.com \
    --to=john@zultron.com \
    --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.