From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <5071C0E6.6060203@gmail.com> Date: Sun, 07 Oct 2012 20:50:30 +0300 From: Jari Lietzen MIME-Version: 1.0 References: <5060AFD1.30303@gmail.com> <506373F6.80406@xenomai.org> <5063E8DE.8010303@gmail.com> <50640444.8010703@xenomai.org> <50647502.9020204@gmail.com> <50649906.7080605@xenomai.org> <506BE88A.9020303@gmail.com> <506CB00D.8010105@xenomai.org> <506D9152.2040109@gmail.com> In-Reply-To: <506D9152.2040109@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] Kernel 2.6.37.6 + Xenomai 2.5.6 is ok, but with Xenomai 2.6.1 it won't boot List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenomai@xenomai.org 04.10.2012 16:38, Jari Lietzen kirjoitti: > 04.10.2012 00:37, Gilles Chanteperdrix kirjoitti: >> On 10/03/2012 09:26 AM, Jari Lietzen wrote: >> >>> 27.09.2012 21:20, Gilles Chanteperdrix kirjoitti: >>>> On 09/27/2012 05:47 PM, Jari Lietzen wrote: >>>> >>>>> 27.09.2012 10:46, Gilles Chanteperdrix kirjoitti: >>>>>> On 09/27/2012 07:49 AM, Jari Lietzen wrote: >>>>>> >>>>>>> 27.09.2012 00:30, Gilles Chanteperdrix kirjoitti: >>>>>>>> On 09/24/2012 09:09 PM, Jari Lietzen wrote: >>>>>>>> >>>>>>>>> Hi! >>>>>>>>> >>>>>>>>> Kernel 2.6.37.6 and Xenomai 2.5.6 boots ok, though displaying >>>>>>>>> the error >>>>>>>>> message: "MP-BIOS bug: 8254 timer not connected to IO-APIC". >>>>>>>>> >>>>>>>>> If I try to use Xenomai 2.6.1 the error message displayed is >>>>>>>>> the same >>>>>>>>> and system just hangs after that. No other messages, keyboard >>>>>>>>> doesn't >>>>>>>>> work, nothing. I started with the same kernel configuration, >>>>>>>>> but I have >>>>>>>>> disabled a few options more (e.g. syscall auditing, shared >>>>>>>>> interrupt >>>>>>>>> support). >>>>>>>>> >>>>>>>>> I'm using Intel Core 2 Duo processor with Asus P5LD2-VM >>>>>>>>> motherboard. >>>>>>>>> Obviously I'm missing something, but I can't figure that out. >>>>>>>>> Here is >>>>>>>>> the kernel config file: >>>>>>>> >>>>>>>> >>>>>>>> If you use one of the I-pipe patches whih ship with Xenomai >>>>>>>> 2.6.1, such >>>>>>>> as the patch for linux 3.2, do you also have the issue? >>>>>>>> >>>>>>> >>>>>>> Hi! >>>>>>> >>>>>>> Yes, I have patched the kernel with this: >>>>>>> /usr/src/xenomai/scripts/prepare-kernel.sh --arch=x86_64 >>>>>>> --adeos=/usr/src/xenomai/ksrc/arch/x86/patches/adeos-ipipe-2.6.37.6-x86-2.9-02.patch >>>>>>> >>>>>>> --linux=/usr/src/linux >>>>>>> >>>>>>> xenomai being a link to xenomai-2.6.1 -directory. When I switch >>>>>>> between >>>>>>> Xenomai 2.5.6 and 2.6.1 I remove the whole linux directory and >>>>>>> extract >>>>>>> it from the source again and change the xenomai link accordingly. >>>>>>> With >>>>>>> Xenomai 2.5.6 the patching was done with this: >>>>>>> /usr/src/xenomai/scripts/prepare-kernel.sh --arch=x86_64 >>>>>>> --adeos=/usr/src/xenomai/ksrc/arch/x86/patches/adeos-ipipe-2.6.37-x86-2.9-00.patch >>>>>>> >>>>>>> --linux=/usr/src/linux >>>>>> >>>>>> >>>>>> So, could you try Xenoami 2.5.6 with the 2.9-02 patch, or 2.6.1 >>>>>> with the >>>>>> 2.9-00 patch, or with the patch for linux 3.2 ? >>>>>> >>>>> >>>>> I booted 2.6.37.6 kernel patched with 2.9-00 patch and compiled >>>>> Xenomai >>>>> 2.6.1 with the following commands: >>>> >>>> >>>> I mean Xenomai 2.6.1 kernel with the 2.9-00 patch or Xenomai 2.5.6 >>>> kernel with 2.9-00 patch. Since the kernel is not booting, we do not >>>> care about the user-space at this point. >>>> >>> >>> I tested again the following combinations. Always starting with a fresh >>> kernel tree and patching it: >>> >>> 2.9-00 patch 2.9-02 patch >>> ---------------------------------------------- >>> Xenomai 2.5.6 OK OK >>> >>> Xenomai 2.6.1 boot fails boot fails >> >> >> Hi, >> >> I could reproduce the bug, it should be fixed with the following patch: >> http://git.xenomai.org/?p=xenomai-2.6.git;a=commitdiff;h=28984e66e9e17701354f8883b025fcf83f8b0b68;hp=8417949f5e7d1b4483eb3b6344ec5f3124ecf740 >> >> > > This patch fixed the problem. I tested this with Core 2 Duo processor > and hopefully I have time tomorrow to test it with Atom D2500 board also. > > Thank you for your help! > > Best regards, > > -Jari It's working fine with the Atom D2500 too. Best regards, -Jari