* Re: [Xenomai-help] Kernel Panic at boot 2.6.15
2006-04-02 17:56 [Xenomai-help] Kernel Panic at boot 2.6.15 Brian L.
@ 2006-04-02 19:27 ` Jan Kiszka
2006-04-02 19:51 ` Philippe Gerum
` (2 subsequent siblings)
3 siblings, 0 replies; 6+ messages in thread
From: Jan Kiszka @ 2006-04-02 19:27 UTC (permalink / raw)
To: Brian L.; +Cc: xenomai
[-- 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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [Xenomai-help] Kernel Panic at boot 2.6.15
2006-04-02 17:56 [Xenomai-help] Kernel Panic at boot 2.6.15 Brian L.
2006-04-02 19:27 ` Jan Kiszka
@ 2006-04-02 19:51 ` Philippe Gerum
2006-04-02 20:24 ` Gilles Chanteperdrix
2006-04-03 5:35 ` emin ak
3 siblings, 0 replies; 6+ messages in thread
From: Philippe Gerum @ 2006-04-02 19:51 UTC (permalink / raw)
To: Brian L.; +Cc: xenomai
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:
> [<c025f5f0>] rthalbroadcast_to_local_timers+0x0/0x30
> [<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!
>
This is the second time this random bug is reported, so there must be
something fishy here. Please rebuild your kernel with
CONFIG_FRAME_POINTER enabled, so we have a readable backtrace.
> ------
>
> 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.
>
> Thanks,
> Brian
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>
--
Philippe.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] Kernel Panic at boot 2.6.15
2006-04-02 17:56 [Xenomai-help] Kernel Panic at boot 2.6.15 Brian L.
2006-04-02 19:27 ` Jan Kiszka
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
3 siblings, 1 reply; 6+ messages in thread
From: Gilles Chanteperdrix @ 2006-04-02 20:24 UTC (permalink / raw)
To: Brian L.; +Cc: xenomai
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:
> [<c025f5f0>] rthalbroadcast_to_local_timers+0x0/0x30
> [<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!
This really looks like :
https://mail.gna.org/public/xenomai-help/2006-03/msg00112.html
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.
--
Gilles Chanteperdrix.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] Kernel Panic at boot 2.6.15
2006-04-02 20:24 ` Gilles Chanteperdrix
@ 2006-04-02 21:07 ` Philippe Gerum
0 siblings, 0 replies; 6+ messages in thread
From: Philippe Gerum @ 2006-04-02 21:07 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai, 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:
> > [<c025f5f0>] rthalbroadcast_to_local_timers+0x0/0x30
> > [<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!
>
> 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Xenomai-help] Kernel Panic at boot 2.6.15
2006-04-02 17:56 [Xenomai-help] Kernel Panic at boot 2.6.15 Brian L.
` (2 preceding siblings ...)
2006-04-02 20:24 ` Gilles Chanteperdrix
@ 2006-04-03 5:35 ` emin ak
3 siblings, 0 replies; 6+ messages in thread
From: emin ak @ 2006-04-03 5:35 UTC (permalink / raw)
To: Brian L.; +Cc: xenomai
I had this problem before, disabling power management (APIC ) on
kernel configuration solved the problem (but I dont know why?),Maybe a
previous topic named 'Crashing at boot with 2.6.15.4' was related with
this problem that fixed in the newest version, you can have a look at
it.
emin
2006/4/2, Brian L. <bluczkie@domain.hid>:
> 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:
> [<c025f5f0>] rthalbroadcast_to_local_timers+0x0/0x30
> [<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.
>
> Thanks,
> Brian
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>
^ permalink raw reply [flat|nested] 6+ messages in thread