From: Jan Kiszka <jan.kiszka@domain.hid>
To: "Brian L." <bluczkie@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Kernel Panic at boot 2.6.15
Date: Sun, 02 Apr 2006 21:27:01 +0200 [thread overview]
Message-ID: <44302585.1080201@domain.hid> (raw)
In-Reply-To: <6ee4c8380604021056q15faf58udc083b8bb13dcb50@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2135 bytes --]
Brian L. wrote:
> I just patched 2.6.15 using the prepare-kernel script and adeos patch
> included in xenomai 2.1.0. I configured the kernel in a sensible way
> for the hardware, but didn't touch anything in the real-time section.
>
> When I boot the kernel, I get a kernel panic. Here's some important
> bits (everything above this is cut off and obviously, unscrollable):
...unfortunately not all of the important bits (i.e. the actual oops
which includes information about what function failed and also register
content).
> Pricess swapper (pid: 1, threadinfo=c12900000, task=c1283a30)
> Stack: ...
> Call Trace:
> [<c025f5f0>] rthalbroadcast_to_local_timers+0x0/0x30
Anyway, this function is the one calling the crashing code, and there
are only APIC related functions in it. You may want to try switching off
local APIC in the kernel config. Does APIC work for standard Linux on
your board?
> [<c0143cf8>] xnpod_get_time+0x8/0x20
> [<c0143c84>] xnpod_set_time+0x44/0xb0
> [<c0144275>] xnpod_start_timer+0x1a5/0x260
> [<c01443d0>] xnpod_announce_tick+0x0/0x100
> [<c01443d0>] xnpod_announce_tick+0x0/0x100
> [<c0140d3a>] xnpod_init+0x46a/0x510
> [<c01443d0>] xnpod_announce_tick+0x0/0x100
> [<c0118500>] __ipipe_flush_printk+0x80/0xa0
> [<c0148bea>] xncore_attach+0x4a/0x60
> [<c014bc9c>] __native_skin_init+0xc/0xf0
> [<c036e8ec>] do_initcalls+0x2c/0xd0
> [<c01002d0>] init+0x0/0x170
> [<c010030c>] init+0x3c/0x170
> [<c01010e9>] kernel_thread_helper+0x5/0xc
> Code: ...
> <0>Kernel panic - not syncing: Attempted to kill init!
>
> ------
>
> The hardware is a UP 440bx with a celeron 566 coppermine.
> CPU/memory/mainboard have been ruled out as failure points. Kernel is
> configured as celeron/coppermine and xenomai as i686.
>
> I trudged through the archives a bit and it seems that this problem is
> somewhat tragically unique. Any xenomai-kernel-internals hackers want
> to give this a go? Is there anywhere I should look first? I'm an
> rtlinux refugee, so my knowledge of adeos/rtai internals is limited.
Err, no RTAI here, you are on Xenomai-core. ;)
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-04-02 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 17:56 [Xenomai-help] Kernel Panic at boot 2.6.15 Brian L.
2006-04-02 19:27 ` Jan Kiszka [this message]
2006-04-02 19:51 ` Philippe Gerum
2006-04-02 20:24 ` Gilles Chanteperdrix
2006-04-02 21:07 ` Philippe Gerum
2006-04-03 5:35 ` emin ak
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=44302585.1080201@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=bluczkie@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.