From: Jan Kiszka <jan.kiszka@domain.hid>
To: VEYSSIERE Nicolas <nicolas.veyssiere@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Kernel panic on boot with 2.5.6
Date: Wed, 22 Jun 2011 14:32:46 +0200 [thread overview]
Message-ID: <4E01E0EE.90002@domain.hid> (raw)
In-Reply-To: <17288_1308741885_4E01D0FD_17288_343_1_ECB646CBB62FD044927FDEDF0252D3E701E388B36206@domain.hid>
On 2011-06-22 13:24, VEYSSIERE Nicolas wrote:
> First time for me here.
>
> The log are in the attachement.
>
...
> [ 0.383950] ------------[ cut here ]------------
> [ 0.384950] WARNING: at arch/x86/kernel/apic/apic.c:1289 setup_local_APIC+0x1e1/0x2cb()
> [ 0.385950] Hardware name: VirtualBox
> [ 0.386950] Modules linked in:
> [ 0.389949] Pid: 1, comm: swapper Not tainted 2.6.38-xenomai-r6 #1
What's your host system, Windows? If it's Linux, don't use VBox, use
QEMU/KVM (it's know to host Xenomai x86 without major problems, it's my
primary test platform for years).
What may help if you can't avoid VBox is to provide the host's CPU
frequency statically to Xenomai (xeno_hal.cpufreq=...) and enforce the
tsc as clocksource (clocksource=tsc). Timekeeping may go mad in the
guest, but it's for testing purposes only anyway.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-06-22 12:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 10:44 [Xenomai-help] Kernel panic on boot with 2.5.6 VEYSSIERE Nicolas
2011-06-22 10:57 ` Gilles Chanteperdrix
2011-06-22 11:10 ` VEYSSIERE Nicolas
2011-06-22 11:12 ` Gilles Chanteperdrix
2011-06-22 11:24 ` VEYSSIERE Nicolas
2011-06-22 12:32 ` Jan Kiszka [this message]
2011-06-22 12:47 ` VEYSSIERE Nicolas
2011-06-22 12:55 ` Jan Kiszka
2011-06-23 9:31 ` VEYSSIERE Nicolas
2011-06-23 9:53 ` varname
2011-06-23 10:08 ` Jan Kiszka
2011-06-22 10:58 ` Sambasiva Rao Manchili
2011-06-22 11:09 ` Sambasiva Rao Manchili
2011-06-22 11:11 ` VEYSSIERE Nicolas
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=4E01E0EE.90002@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=nicolas.veyssiere@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.