Yes, my host is Windows, I can't change anything about that, and yes it is only for testing.
I changed my boot line : [ 0.000000] Kernel command line: root=/dev/sda3 xeno_hal.cpufreq=1200 clocksource=tsc console=tty0 console=ttyS0,115200 noapic acpi=noirq video=vesafb:mtrr:3,ywrap vga=6 But I didn't find the range or the unit for cpufreq, and maybe I had to prefix clocksource with xeno_hal ? But I noticed this in the log : [ 1.202694] BUG: unable to handle kernel NULL pointer dereference at 00000920 [ 1.202694] IP: [<c10736fe>] __xirq_end+0x12/0x2e [ 1.202694] *pde = 00000000 [ 1.202694] Oops: 0000 [#1] SMP Can it be because SMP is activated and that virtualbox is enabling only 1 processor with 1 core ? -- Nicolas VEYSSIERE -----Message d'origine----- De : Jan Kiszka [mailto:[email protected]] Envoyé : mercredi 22 juin 2011 14:33 À : VEYSSIERE Nicolas Cc : Gilles Chanteperdrix; [email protected] Objet : Re: Kernel panic on boot with 2.5.6 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 _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
