From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <49872135.9000404@domain.hid> Date: Mon, 02 Feb 2009 17:37:09 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <8E970E0F84BD44C9B4C41942F86F2F34@domain.hid> <498082B7.2000609@domain.hid> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Xenomai-help] TR: Kernel panic with (Kernel-2.6.27/Xenomai -2.4.6) List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sebastien DI MERCURIO Cc: xenomai@xenomai.org Sebastien DI MERCURIO wrote: > Sorry for the delay. >=20 > It seems it was a problem specific to VirtualBox. The same kernel works= fine > on a real machine. It /might/ be a problem of this VM, but often the different timing of these environments triggers races that only rarely occur on real hw. For x86, I'm doing a lot of debugging and stress testing (not latency testing, of course) under KVM. And I found no problem that was due to the VM - at least on that platform which is, granted, much more hardware-like than VirtualBox as it only uses HVM. So, when time permits, it would be good to try catching the full trace (redirect kernel console to serial port, record output on that virtual serial port) and disassemble (objdump -dS vmlinux) the function that is reported to fail. Thanks, Jan > -----Message d'origine----- > De : Gilles Chanteperdrix [mailto:gilles.chanteperdrix@xenomai.org > Envoy=E9 : mercredi 28 janvier 2009 17:07 > =C0 : Sebastien DI MERCURIO > Cc : xenomai@xenomai.org > Objet : Re: [Xenomai-help] TR: Kernel panic with (Kernel-2.6.27/Xenomai > -2.4.6) >=20 > Sebastien DI MERCURIO wrote: >> Hello, >> =20 >> I have compiled and installed linux kernel 2.6.27 in a fedora distro=20 >> running in Virtualbox. Everything worked fine. >> After that, I patched the kernel using xenomai-2.4.6 script=20 >> "prepare-kernel.sh". So, the adeos patch used was=20 >> adeos-ipie-2.6.27-x86-2.1-01.patch. No problem. >> =20 >> Then I have configured the newly patched kernel for activate xenomai=20 >> and nucleus (find the .config file in attachment). I compiled the=20 >> kernel. No error, no problem. >> =20 >> But when I boot the patched kernel, it produces a panic, apparently in= =20 >> xeno_sys_init (look at the screen copy of vitualbox). >=20 > Do you have the same error if you boot this kernel on a real machine ? >=20 >=20 --=20 Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux