From: Jan Kiszka <jan.kiszka@domain.hid>
To: Luotao Fu <l.fu@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] strangeness at kernel configuration
Date: Thu, 20 Apr 2006 13:54:48 +0200 [thread overview]
Message-ID: <44477688.3070505@domain.hid> (raw)
In-Reply-To: <20060419152914.GB13542@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2002 bytes --]
Luotao Fu wrote:
> Hi Philipe,
>
> On Tue, Apr 18, 2006 at 06:03:43PM +0200, Philippe Gerum wrote:
>> Luotao Fu wrote:
>> Your configuration works perfectly here over #944. You might want to
>> restart building from a freshly patched kernel anew, there seems to be
>> something badly broken in your current tree, perhaps some mismatching
>> modules that have not been recompiled properly?
>>
>> --
>>
>> Philippe.
> Thanx for testing. I, however could locate the problem at the APIC
> Timer function in the kernel: With
> ......
> CONFIG_X86_UP_APIC=y
> CONFIG_X86_UP_IOAPIC=y
> CONFIG_X86_LOCAL_APIC=y
> CONFIG_X86_IO_APIC=y
> ......
> I could reproduce the problem (loading rtdm driver causes oops, cannot run
> any application using native or posix skin) reliably on my machine.
> (Celeron 733MHz. 256MB RAM...a normal PC) Shutting off the APIC stuffs,
> however, solves the problem........ Have I overlooked
> anything or does Xenomai have problems with the apic controller on
> celeron (since it seems to work for you)?
>
Do you pass "lapic" via the kernel command line? If lapic is missing,
this would not work anyway. This illegal combination used to cause
crashes, but the detection should have been fixed some weeks ago.
I just tried to reproduce your scenario - and I was "successful": All
APIC stuff on, up to RTDM all xeno stuff built in, "forgotten" lapic in
bootparam, and then modprobe xeno_timerbench, oops.
The oops is a minor issue which I will try to address more gracefully
later. The major issue is that missing lapic. You should have this in
your kernel log:
...
Xenomai: Local APIC absent or disabled!
Disable APIC support or pass "lapic=1" as bootparam.
Xenomai: system init failed, code -19.
Xenomai: starting POSIX services.
Xenomai: POSIX skin init failed, code -19.
Xenomai: RTDM skin init failed, code -19.
...
So, all fine from the xenomai POV, except for that bug in
rtdm_dev_register().
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-04-20 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 14:41 [Xenomai-help] strangeness at kernel configuration Luotao Fu
2006-04-18 15:35 ` Luotao Fu
2006-04-18 16:03 ` Philippe Gerum
2006-04-19 15:29 ` Luotao Fu
2006-04-19 15:42 ` Philippe Gerum
2006-04-20 11:54 ` Jan Kiszka [this message]
2006-04-20 12:26 ` Luotao Fu
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=44477688.3070505@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=l.fu@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.