From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <44302585.1080201@domain.hid> Date: Sun, 02 Apr 2006 21:27:01 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Xenomai-help] Kernel Panic at boot 2.6.15 References: <6ee4c8380604021056q15faf58udc083b8bb13dcb50@domain.hid> In-Reply-To: <6ee4c8380604021056q15faf58udc083b8bb13dcb50@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig045CBE88C9D34188702C90D1" Sender: jan.kiszka@domain.hid List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Brian L." Cc: xenomai@xenomai.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig045CBE88C9D34188702C90D1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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. >=20 > When I boot the kernel, I get a kernel panic. Here's some important > bits (everything above this is cut off and obviously, unscrollable): =2E..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=3Dc12900000, task=3Dc1283a30) > Stack: ... > Call Trace: > [] 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? > [] xnpod_get_time+0x8/0x20 > [] xnpod_set_time+0x44/0xb0 > [] xnpod_start_timer+0x1a5/0x260 > [] xnpod_announce_tick+0x0/0x100 > [] xnpod_announce_tick+0x0/0x100 > [] xnpod_init+0x46a/0x510 > [] xnpod_announce_tick+0x0/0x100 > [] __ipipe_flush_printk+0x80/0xa0 > [] xncore_attach+0x4a/0x60 > [] __native_skin_init+0xc/0xf0 > [] do_initcalls+0x2c/0xd0 > [] init+0x0/0x170 > [] init+0x3c/0x170 > [] kernel_thread_helper+0x5/0xc > Code: ... > <0>Kernel panic - not syncing: Attempted to kill init! >=20 > ------ >=20 > 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. >=20 > 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 --------------enig045CBE88C9D34188702C90D1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEMCWFniDOoMHTA+kRAnqXAJ4uSk50ukbOkWXahdN7yRReKBjHewCfbp8p /TzHuMY1cHypAgzc1qVCAjo= =Ogxt -----END PGP SIGNATURE----- --------------enig045CBE88C9D34188702C90D1--