From: Jan Kiszka <jan.kiszka@domain.hid>
To: "Rosenow, Jim" <Jim.Rosenow@domain.hid>
Cc: xenomai@xenomai.org, wallace@domain.hid
Subject: Re: [Xenomai-help] Almost running - kernel BUG in add_preempt_count at kernel/sched.c:2819!
Date: Fri, 19 May 2006 21:48:23 +0200 [thread overview]
Message-ID: <446E2107.8060504@domain.hid> (raw)
In-Reply-To: <B4D14EA407C38B4DAF92B8EAC9249D7F02D0F285@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]
Rosenow, Jim wrote:
> Sorry for the missing history.
>
> I started with a vanilla 2.6.14-7 kernel from kernel.org, I patched it
> with a Motorola patch to enable the features specific to the mvme5500.
> I built under ELDK 4.0 and the kernel ran just fine.
>
> Next I retrieved xenomai-2.1.1 and followed the install instructions.
> The adeos version adeos-ipipe-2.6.14-1.2.03.patch. This patch applied
> and I rebuilt the kernel. I ran into a problem with xmon not compiling
> so I removed that switch from the kernel hacking menu and it built fine.
>
> That brings us to now.
>
> In reference to your recommendation, can I simply disable ipipe and
> leave xenomai enabled and expect the kernel to run? I thought there was
> a pretty close coupling between the two.
No, you are right, this is not possible. I meant booting with both ipipe
and xenomai disabled.
Is your board able to boot without the Motorola patches? If yes, does
the problem persist? BTW, did the ipipe patch apply cleanly on top of
the Motorola patch or did you have to fix some hunks?
@all: What will help to track this down are back-traces of the crash.
Does the console contain a stack trace as well? If not, try using the
ipipe-tracer (additional patch [1]) and put an
ipipe_trace_panic_freeze() + ipipe_trace_panic_dump() before that BUG()
(with the same condition, of course). Actually, this tool can report
more than a stack trace. It records a full function call history and may
reveal where the ipipe patch left the correct path.
Jan
PS: Just in case you thought about this, switching the ipipe patch to
1.3 may only hide the problem. The newer patches contain optimisations,
not bug fixes of the 1.2 series.
[1] http://download.gna.org/adeos/patches/v2.6/ppc/tracer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-05-19 19:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 18:28 [Xenomai-help] Almost running - kernel BUG in add_preempt_count at kernel/sched.c:2819! Rosenow, Jim
2006-05-19 19:48 ` Jan Kiszka [this message]
2006-05-19 20:19 ` Gary Wallace
2006-05-20 17:55 ` Jan Kiszka
2006-05-20 21:11 ` Philippe Gerum
2006-05-22 19:25 ` Gary Wallace
2006-05-22 21:29 ` Philippe Gerum
-- strict thread matches above, loose matches on Subject: below --
2006-05-22 21:49 Gary Wallace
2006-05-23 7:32 ` Philippe Gerum
2006-05-23 9:24 ` Philippe Gerum
2006-05-23 14:51 ` Philippe Gerum
2006-05-23 22:48 ` Gary Wallace
2006-05-24 7:01 ` Philippe Gerum
2006-05-19 17:50 Rosenow, Jim
2006-05-19 18:05 ` Jan Kiszka
2006-05-19 18:19 ` Gary Wallace
2006-05-19 21:22 ` Philippe Gerum
2006-05-20 14:59 ` Philippe Gerum
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=446E2107.8060504@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Jim.Rosenow@domain.hid \
--cc=wallace@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.