From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <44303CFF.7000009@domain.hid> Date: Sun, 02 Apr 2006 23:07:11 +0200 From: Philippe Gerum MIME-Version: 1.0 Subject: Re: [Xenomai-help] Kernel Panic at boot 2.6.15 References: <6ee4c8380604021056q15faf58udc083b8bb13dcb50@domain.hid> <17456.13053.959905.931606@domain.hid> In-Reply-To: <17456.13053.959905.931606@domain.hid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: xenomai@xenomai.org, "Brian L." Gilles Chanteperdrix wrote: > 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): > > > > Pricess swapper (pid: 1, threadinfo=c12900000, task=c1283a30) > > Stack: ... > > Call Trace: > > [] rthalbroadcast_to_local_timers+0x0/0x30 > > [] 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! > > This really looks like : > https://mail.gna.org/public/xenomai-help/2006-03/msg00112.html > Indeed, comparing to the traces I have received on the other issue, this must be the same problem. > Which was fixed by revision 786 in trunk and 787 in v2.1.x branch. > > The real issue is that you enabled support for APIC in kernel > configuration, and your CPU either has no APIC, or it is disabled by > Linux because disabled by BIOS. > > Try adding "lapic" as a kernel parameter, and if it still does not work, > disable support for APIC in the kernel configuration and rebuild your > kernel. > -- Philippe.