Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH]

Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH]

[kisda]

---- Paul <paul_c@domain.hid> schrieb:
> On Wednesday 18 August 2010, Stefan Kisdaroczi wrote:
> > On 17.08.2010 17:24, Stefan Kisdaroczi wrote:
> > > On 17.08.2010 15:51, Hemal C.Bavishi wrote:
> > >> When I tried to compile it with the latest version of kernel with
> > >> xenomai 2.5.4, I am getting following errors in Xenomai (disable
> > >> CONFIG_SMP, enable CONFIG_X86_UP_APIC and CONFIG_X86_UP_IOAPIC
> > >> (*).)
> > >
> > > Just tested, got the same build error with 2.6.34.
> > > If I patch 2.6.34 with prepare-kernel [1] it compiles,
> > > if I use the debian packaged patch generated with prepare-patch [2]
> > > it fails.
> > >
> > > I guess a fix is needed in prepare-patch for 2.6.34, but no time to
> > > look closer now.
> >
> > patch for prepare-patch.sh attached.
> > prepare-kernel.sh try's to find ipipe.h and uses the old or new tree
> > structure. Is it ok to change this unconditionally in
> > prepare-patch.sh? All adeos-patches in xenomai-2.5.git have ipipe.h
> > in
> > arch/$linux_arch/include/asm/, so i think yes.
> 
> As long as no one tries to include a patch for anything prior to 2.6.28 
> (I think that is when everything moved to arch/*/include/asm) - There 
> is only one ipipe patch in head currently for 2.6.25-ppc, but I doubt 
> if anyone would be using it on a Debian build.
> For that one case, I don't think it worth adding any additional 
> complexity to generate a patch with a limited life span.

It's a 2.4.25-ppc patch (note the 4) and the debian build includes only 2.6.* patches. from prepare-patch.sh:
find $xenomai_root/ksrc/ -name "adeos-ipipe-2.6.*-$supported_arch-*.patch"

Regards, 
Stefan

[Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system

[Theo Veenker]

Hi,

I want to upgrade all our PC's from Ubuntu hardy to lucid and in the process
I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel 2.6.32.11
with Xenomai 2.5.3.

I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy system
and all went fine. But the problem is it just doesn't run on the lucid distro.
However the vanilla kernel runs fine. I also tried with a config based on the
ubuntu lucid config, with relevant modules compiled in (I don't use initrd).

It looks like the same problem as in this thread:
https://mail.gna.org/public/xenomai-help/2010-06/msg00008.html
Just a black screen after the boot loader. The keyboard leds responds to
capslock etc for a few seconds.

What could it be that with identical hardware the same kernel runs fine (with
decent latencies) under ubuntu hardy and not at all under ubuntu lucid? I
also tested another (older) system with a different mobo. Same result.

If there's anyone running a recent kernel with Xenomai 2.5.3 on an ubuntu lucid
system, could you please send me the kernel config?

Thanks,
Theo

Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system

[Gilles Chanteperdrix]

Theo Veenker wrote:
> Hi,
> 
> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the process
> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel 2.6.32.11
> with Xenomai 2.5.3.
> 
> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy system
> and all went fine. But the problem is it just doesn't run on the lucid distro.

This, I do not understand, the kernel does not need any support from the
distribution for booting, how can the same kernel boot with one
distribution, and not with the other? When you say the "same kernel", do
you mean the exact same zImage or bzImage, or do you mean the kernel
with the same configuration, but with a different compiler, or only the
version is identical?

-- 
					    Gilles.

Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system

[Theo Veenker]

Gilles Chanteperdrix wrote:
> Theo Veenker wrote:
>> Hi,
>>
>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the process
>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel 2.6.32.11
>> with Xenomai 2.5.3.
>>
>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy system
>> and all went fine. But the problem is it just doesn't run on the lucid distro.
> 
> This, I do not understand, the kernel does not need any support from the
> distribution for booting, how can the same kernel boot with one
> distribution, and not with the other? When you say the "same kernel", do
> you mean the exact same zImage or bzImage, or do you mean the kernel
> with the same configuration, but with a different compiler, or only the
> version is identical?
> 

It is a complete mystery to me either. I compiled my kernel into a deb package
and installed the very same deb package on three machines:
   MSI p45 neo3 with Hardy on it -> works OK
   MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
   MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)

I'll try the suggestions posted and keep you informed.

Theo

Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system

[Theo Veenker]

On 08/16/2010 04:26 PM, Theo Veenker wrote:
> Gilles Chanteperdrix wrote:
>> Theo Veenker wrote:
>>> Hi,
>>>
>>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
>>> process
>>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
>>> 2.6.32.11
>>> with Xenomai 2.5.3.
>>>
>>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
>>> system
>>> and all went fine. But the problem is it just doesn't run on the
>>> lucid distro.
>>
>> This, I do not understand, the kernel does not need any support from the
>> distribution for booting, how can the same kernel boot with one
>> distribution, and not with the other? When you say the "same kernel", do
>> you mean the exact same zImage or bzImage, or do you mean the kernel
>> with the same configuration, but with a different compiler, or only the
>> version is identical?
>>
>
> It is a complete mystery to me either. I compiled my kernel into a deb
> package
> and installed the very same deb package on three machines:
> MSI p45 neo3 with Hardy on it -> works OK
> MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
>
> I'll try the suggestions posted and keep you informed.

OK. Connected a terminal to catch early kernel messages. Still no output
unfortunately (with the regular kernel I do get output on the terminal,
so the connection works).

Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
I'm clueless. I'm running Xenomai for years on dozens of systems and I've
never run into problems like this. I think I'll have to sit down and take a
close look at what I'm doing. I've always built my kernels using make-kpkg,
maybe that somehow introduces a problem here. I'll try without it.

(unfortunately/luckily I have to work from home for a few days so I can't
get to the test system until later this week)

Theo

Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system

[Philippe Gerum]

On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
> On 08/16/2010 04:26 PM, Theo Veenker wrote:
> > Gilles Chanteperdrix wrote:
> >> Theo Veenker wrote:
> >>> Hi,
> >>>
> >>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
> >>> process
> >>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
> >>> 2.6.32.11
> >>> with Xenomai 2.5.3.
> >>>
> >>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
> >>> system
> >>> and all went fine. But the problem is it just doesn't run on the
> >>> lucid distro.
> >>
> >> This, I do not understand, the kernel does not need any support from the
> >> distribution for booting, how can the same kernel boot with one
> >> distribution, and not with the other? When you say the "same kernel", do
> >> you mean the exact same zImage or bzImage, or do you mean the kernel
> >> with the same configuration, but with a different compiler, or only the
> >> version is identical?
> >>
> >
> > It is a complete mystery to me either. I compiled my kernel into a deb
> > package
> > and installed the very same deb package on three machines:
> > MSI p45 neo3 with Hardy on it -> works OK
> > MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> > MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
> >
> > I'll try the suggestions posted and keep you informed.
> 
> OK. Connected a terminal to catch early kernel messages. Still no output
> unfortunately (with the regular kernel I do get output on the terminal,
> so the connection works).
> 
> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
> never run into problems like this. I think I'll have to sit down and take a
> close look at what I'm doing. I've always built my kernels using make-kpkg,
> maybe that somehow introduces a problem here. I'll try without it.
> 
> (unfortunately/luckily I have to work from home for a few days so I can't
> get to the test system until later this week)

I failed to reproduce the issue yet, but it very much looks like an
I-pipe bug. Could you try the following config variants when time
allows:

- on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
only (*).
- on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
CONFIG_X86_UP_IOAPIC (*).
- on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch

(*) you need to switch off CONFIG_SMP first, to see those knobs appear
in the "processor type and features" menu.

The fact that you did see the panic blinking signal at least once tends
to point the finger at some access fault the kernel tries to recover
without success, rather than a sudden freeze. It must happen early
enough during the boot process, for the console not to be available yet
for reporting what the kernel whines about.

We don't know yet if that bug is either the consequence of some
interrupt delivery, and/or induced by code only involved in SMP. Those
test configs may help in discovering this.

TIA,

-- 
Philippe.

Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system

[Hemal C.Bavishi]

When I tried to compile it with the latest version of kernel with xenomai 2.5.4, I am getting following errors in Xenomai (disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
CONFIG_X86_UP_IOAPIC (*).)


kernel/xenomai/arch/generic/hal.c:47:29: error: asm/xenomai/hal.h: No such file or directory
kernel/xenomai/arch/generic/hal.c:77: error: ‘RTHAL_NR_CPUS’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:79: error: ‘RTHAL_NR_APCS’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:89: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rthal_apc_lock’
kernel/xenomai/arch/generic/hal.c:93: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rthal_domain’
kernel/xenomai/arch/generic/hal.c:97: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rthal_trap_handler’
kernel/xenomai/arch/generic/hal.c:99: error: ‘RTHAL_NR_FAULTS’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_critical_enter’:
kernel/xenomai/arch/generic/hal.c:105: error: implicit declaration of function ‘rthal_grab_superlock’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_critical_exit’:
kernel/xenomai/arch/generic/hal.c:118: error: implicit declaration of function ‘rthal_release_superlock’
kernel/xenomai/arch/generic/hal.c: At top level:
kernel/xenomai/arch/generic/hal.c:169: error: expected declaration specifiers or ‘...’ before ‘rthal_irq_handler_t’
kernel/xenomai/arch/generic/hal.c:170: error: expected declaration specifiers or ‘...’ before ‘rthal_irq_ackfn_t’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_irq_request’:
kernel/xenomai/arch/generic/hal.c:172: error: ‘handler’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:172: error: (Each undeclared identifier is reported only once
kernel/xenomai/arch/generic/hal.c:172: error: for each function it appears in.)
kernel/xenomai/arch/generic/hal.c:175: error: implicit declaration of function ‘rthal_virtualize_irq’
kernel/xenomai/arch/generic/hal.c:175: error: ‘rthal_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:179: error: ‘ackfn’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:180: error: ‘IPIPE_HANDLE_MASK’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:180: error: ‘IPIPE_WIRED_MASK’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:181: error: ‘IPIPE_EXCLUSIVE_MASK’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_irq_release’:
kernel/xenomai/arch/generic/hal.c:215: error: ‘rthal_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:216: error: ‘IPIPE_PASS_MASK’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c: At top level:
kernel/xenomai/arch/generic/hal.c:390: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rthal_trap_catch’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_apc_handler’:
kernel/xenomai/arch/generic/hal.c:400: error: implicit declaration of function ‘rthal_spin_lock’
kernel/xenomai/arch/generic/hal.c:400: error: ‘rthal_apc_lock’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:402: error: implicit declaration of function ‘rthal_processor_id’
kernel/xenomai/arch/generic/hal.c:413: error: implicit declaration of function ‘ffnz’
kernel/xenomai/arch/generic/hal.c:418: error: implicit declaration of function ‘rthal_spin_unlock’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_apc_alloc’:
kernel/xenomai/arch/generic/hal.c:526: error: implicit declaration of function ‘rthal_spin_lock_irqsave’
kernel/xenomai/arch/generic/hal.c:526: error: ‘rthal_apc_lock’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:537: error: implicit declaration of function ‘rthal_spin_unlock_irqrestore’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_apc_schedule’:
kernel/xenomai/arch/generic/hal.c:608: error: implicit declaration of function ‘rthal_local_irq_save’
kernel/xenomai/arch/generic/hal.c:611: error: implicit declaration of function ‘rthal_schedule_irq_root’
kernel/xenomai/arch/generic/hal.c:613: error: implicit declaration of function ‘rthal_local_irq_restore’
kernel/xenomai/arch/generic/hal.c: In function ‘hal_read_proc’:
kernel/xenomai/arch/generic/hal.c:628: error: ‘IPIPE_MAJOR_NUMBER’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:629: error: ‘IPIPE_MINOR_NUMBER’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:630: error: ‘IPIPE_PATCH_NUMBER’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c: In function ‘faults_read_proc’:
kernel/xenomai/arch/generic/hal.c:658: error: ‘rthal_fault_labels’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_add_proc_leaf’:
kernel/xenomai/arch/generic/hal.c:744: error: implicit declaration of function ‘wrap_proc_dir_entry_owner’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_proc_register’:
kernel/xenomai/arch/generic/hal.c:786: error: implicit declaration of function ‘rthal_nmi_proc_register’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_proc_unregister’:
kernel/xenomai/arch/generic/hal.c:793: error: implicit declaration of function ‘rthal_nmi_proc_unregister’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_init’:
kernel/xenomai/arch/generic/hal.c:806: error: implicit declaration of function ‘rthal_arch_init’
kernel/xenomai/arch/generic/hal.c:832: error: invalid use of undefined type ‘struct rthal_calibration_data’
kernel/xenomai/arch/generic/hal.c:833: error: invalid use of undefined type ‘struct rthal_calibration_data’
kernel/xenomai/arch/generic/hal.c:834: error: invalid use of undefined type ‘struct rthal_calibration_data’
kernel/xenomai/arch/generic/hal.c:840: error: implicit declaration of function ‘rthal_alloc_virq’
kernel/xenomai/arch/generic/hal.c:848: error: ‘rthal_current_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:851: error: ‘IPIPE_HANDLE_MASK’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:874: error: implicit declaration of function ‘rthal_register_domain’
kernel/xenomai/arch/generic/hal.c:874: error: ‘rthal_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:876: error: ‘RTHAL_DOMAIN_ID’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:877: error: ‘RTHAL_XENO_PRIO’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:877: error: ‘rthal_domain_entry’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:915: error: implicit declaration of function ‘rthal_free_virq’
kernel/xenomai/arch/generic/hal.c:918: error: implicit declaration of function ‘rthal_arch_cleanup’
kernel/xenomai/arch/generic/hal.c: In function ‘rthal_exit’:
kernel/xenomai/arch/generic/hal.c:931: error: ‘rthal_current_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c:945: error: implicit declaration of function ‘rthal_unregister_domain’
kernel/xenomai/arch/generic/hal.c:945: error: ‘rthal_domain’ undeclared (first use in this function)
kernel/xenomai/arch/generic/hal.c: At top level:
kernel/xenomai/arch/generic/hal.c:1107: error: ‘rthal_irq_enable’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1107: warning: type defaults to ‘int’ in declaration of ‘rthal_irq_enable’
kernel/xenomai/arch/generic/hal.c:1108: error: ‘rthal_irq_disable’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1108: warning: type defaults to ‘int’ in declaration of ‘rthal_irq_disable’
kernel/xenomai/arch/generic/hal.c:1109: error: ‘rthal_irq_end’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1109: warning: type defaults to ‘int’ in declaration of ‘rthal_irq_end’
kernel/xenomai/arch/generic/hal.c:1110: error: ‘rthal_irq_host_request’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1110: warning: type defaults to ‘int’ in declaration of ‘rthal_irq_host_request’
kernel/xenomai/arch/generic/hal.c:1111: error: ‘rthal_irq_host_release’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1111: warning: type defaults to ‘int’ in declaration of ‘rthal_irq_host_release’
kernel/xenomai/arch/generic/hal.c:1113: error: ‘rthal_trap_catch’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1113: warning: type defaults to ‘int’ in declaration of ‘rthal_trap_catch’
kernel/xenomai/arch/generic/hal.c:1114: error: ‘rthal_timer_request’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1114: warning: type defaults to ‘int’ in declaration of ‘rthal_timer_request’
kernel/xenomai/arch/generic/hal.c:1115: error: ‘rthal_timer_release’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1115: warning: type defaults to ‘int’ in declaration of ‘rthal_timer_release’
kernel/xenomai/arch/generic/hal.c:1116: error: ‘rthal_timer_calibrate’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1116: warning: type defaults to ‘int’ in declaration of ‘rthal_timer_calibrate’
kernel/xenomai/arch/generic/hal.c:1124: error: ‘rthal_domain’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1124: warning: type defaults to ‘int’ in declaration of ‘rthal_domain’
kernel/xenomai/arch/generic/hal.c:1135: error: ‘kill_proc_info’ undeclared here (not in a function)
kernel/xenomai/arch/generic/hal.c:1135: warning: type defaults to ‘int’ in declaration of ‘kill_proc_info’
make[6]: *** [kernel/xenomai/arch/generic/hal.o] Error 1
make[5]: *** [kernel/xenomai/arch/generic] Error 2
make[4]: *** [kernel/xenomai/arch] Error 2
make[3]: *** [kernel/xenomai] Error 2
make[2]: *** [kernel] Error 2
make[2]: *** Waiting for unfinished jobs....
  CC      mm/mincore.o
  CC      mm/mlock.o
  CC      mm/mmap.o
  CC      mm/mprotect.o
  CC      mm/mremap.o
  CC      mm/msync.o
  CC      mm/rmap.o
  CC      mm/vmalloc.o
  CC      mm/pagewalk.o
  CC      mm/init-mm.o
  CC      mm/bounce.o
  CC      mm/page_io.o
  CC      mm/swap_state.o
  CC      mm/swapfile.o
  CC      mm/thrash.o
  CC      mm/dmapool.o
  CC      mm/hugetlb.o
  CC      mm/mmu_notifier.o
  CC      mm/ksm.o
  CC      mm/slub.o
  CC      mm/percpu_up.o
  CC      mm/memcontrol.o
  CC      mm/page_cgroup.o
  CC      mm/memory-failure.o
  LD      mm/built-in.o
make[2]: Leaving directory `/root/linux-2.6.34.2'
make[1]: *** [debian/stamp/build/kernel] Error 2
make[1]: Leaving directory `/root/linux-2.6.34.2'
make: *** [debian/stamp/do-build-arch] Error 2
root@domain.hid# cd latency



________________________________________
From: xenomai-help-bounces@domain.hid [xenomai-help-bounces@domain.hid] On Behalf Of Philippe Gerum [rpm@xenomai.org]
Sent: Tuesday, August 17, 2010 3:57 PM
To: Theo Veenker
Cc: Xenomai help
Subject: Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system

On Mon, 2010-08-16 at 21:14 +0200, Theo Veenker wrote:
> On 08/16/2010 04:26 PM, Theo Veenker wrote:
> > Gilles Chanteperdrix wrote:
> >> Theo Veenker wrote:
> >>> Hi,
> >>>
> >>> I want to upgrade all our PC's from Ubuntu hardy to lucid and in the
> >>> process
> >>> I'm also going from kernel 2.6.29.5 with Xenomai 2.4.8 to kernel
> >>> 2.6.32.11
> >>> with Xenomai 2.5.3.
> >>>
> >>> I first built and tested the 2.6.32.11 kernel with 2.5.3 on my hardy
> >>> system
> >>> and all went fine. But the problem is it just doesn't run on the
> >>> lucid distro.
> >>
> >> This, I do not understand, the kernel does not need any support from the
> >> distribution for booting, how can the same kernel boot with one
> >> distribution, and not with the other? When you say the "same kernel", do
> >> you mean the exact same zImage or bzImage, or do you mean the kernel
> >> with the same configuration, but with a different compiler, or only the
> >> version is identical?
> >>
> >
> > It is a complete mystery to me either. I compiled my kernel into a deb
> > package
> > and installed the very same deb package on three machines:
> > MSI p45 neo3 with Hardy on it -> works OK
> > MSI p45 neo3 with Ludid on it -> nothing (works fine with regular kernel)
> > MSI 945P with Lucid on it: -> nothing (works fine with regular kernel)
> >
> > I'll try the suggestions posted and keep you informed.
>
> OK. Connected a terminal to catch early kernel messages. Still no output
> unfortunately (with the regular kernel I do get output on the terminal,
> so the connection works).
>
> Meanwhile also built and tested kernel 2.6.32.15 + xenomai 2.5.4. Still nothing.
> I'm clueless. I'm running Xenomai for years on dozens of systems and I've
> never run into problems like this. I think I'll have to sit down and take a
> close look at what I'm doing. I've always built my kernels using make-kpkg,
> maybe that somehow introduces a problem here. I'll try without it.
>
> (unfortunately/luckily I have to work from home for a few days so I can't
> get to the test system until later this week)

I failed to reproduce the issue yet, but it very much looks like an
I-pipe bug. Could you try the following config variants when time
allows:

- on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC
only (*).
- on 2.6.32.11 or .15, disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
CONFIG_X86_UP_IOAPIC (*).
- on 2.6.32.7, use your normal CONFIG_SMP config, with this patch in:
http://download.gna.org/adeos/patches/v2.6/x86/older/adeos-ipipe-2.6.32.7-x86-2.5-01.patch

(*) you need to switch off CONFIG_SMP first, to see those knobs appear
in the "processor type and features" menu.

The fact that you did see the panic blinking signal at least once tends
to point the finger at some access fault the kernel tries to recover
without success, rather than a sudden freeze. It must happen early
enough during the boot process, for the console not to be available yet
for reporting what the kernel whines about.

We don't know yet if that bug is either the consequence of some
interrupt delivery, and/or induced by code only involved in SMP. Those
test configs may help in discovering this.

TIA,

--
Philippe.



_______________________________________________
Xenomai-help mailing list
Xenomai-help@domain.hid
https://mail.gna.org/listinfo/xenomai-help

Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system

[Stefan Kisdaroczi]

[-- Attachment #1: Type: text/plain, Size: 640 bytes --]

On 17.08.2010 15:51, Hemal C.Bavishi wrote:
> When I tried to compile it with the latest version of kernel with xenomai 2.5.4, I am getting following errors in Xenomai (disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
> CONFIG_X86_UP_IOAPIC (*).)
>   

Just tested, got the same build error with 2.6.34.
If I patch 2.6.34 with prepare-kernel [1] it compiles,
if I use the debian packaged patch generated with prepare-patch [2] it
fails.

I guess a fix is needed in prepare-patch for 2.6.34, but no time to look
closer now.

Stefan

[1] xenomai-2.5.4/scripts/prepare-kernel.sh
[2] xenomai-2.5.4/debian/prepare-patch.sh



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH]

[Stefan Kisdaroczi]

[-- Attachment #1.1: Type: text/plain, Size: 917 bytes --]

On 17.08.2010 17:24, Stefan Kisdaroczi wrote:
> On 17.08.2010 15:51, Hemal C.Bavishi wrote:
>   
>> When I tried to compile it with the latest version of kernel with xenomai 2.5.4, I am getting following errors in Xenomai (disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
>> CONFIG_X86_UP_IOAPIC (*).)
>>   
>>     
> Just tested, got the same build error with 2.6.34.
> If I patch 2.6.34 with prepare-kernel [1] it compiles,
> if I use the debian packaged patch generated with prepare-patch [2] it
> fails.
>
> I guess a fix is needed in prepare-patch for 2.6.34, but no time to look
> closer now.
>   

patch for prepare-patch.sh attached.
prepare-kernel.sh try's to find ipipe.h and uses the old or new tree
structure. Is it ok to change this unconditionally in prepare-patch.sh?
All adeos-patches in xenomai-2.5.git have ipipe.h in
arch/$linux_arch/include/asm/, so i think yes.

Stefan


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-debian-fix-asm-include-directory-linking-in-prepare-.patch --]
[-- Type: text/x-patch; name="0001-debian-fix-asm-include-directory-linking-in-prepare-.patch", Size: 926 bytes --]

From 8e792591e8c42a4c38d16514e02622f3398c9f22 Mon Sep 17 00:00:00 2001
From: Stefan Kisdaroczi <kisda@domain.hid>
Date: Wed, 18 Aug 2010 20:24:15 +0200
Subject: [PATCH] debian: fix asm include directory linking in prepare-patch.sh

---
 debian/prepare-patch.sh |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/debian/prepare-patch.sh b/debian/prepare-patch.sh
index 296638d..6ca734b 100755
--- a/debian/prepare-patch.sh
+++ b/debian/prepare-patch.sh
@@ -112,7 +112,7 @@ for linux_arch in $supported_arch ; do
     esac
 
     patch_link r m ksrc/arch/$base_arch arch/$linux_arch/xenomai
-    patch_link r n include/asm-$base_arch include/asm-$linux_arch/xenomai
+    patch_link r n include/asm-$base_arch arch/$linux_arch/include/asm/xenomai
 
     p="+drivers-\$(CONFIG_XENOMAI)		+= arch/$linux_arch/xenomai/"
     echo $p | patch_append arch/$linux_arch/Makefile
-- 
1.7.1


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH]

[Stefan Kisdaroczi]

[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]

On 18.08.2010 20:45, Stefan Kisdaroczi wrote:
> On 17.08.2010 17:24, Stefan Kisdaroczi wrote:
>   
>> On 17.08.2010 15:51, Hemal C.Bavishi wrote:
>>   
>>     
>>> When I tried to compile it with the latest version of kernel with xenomai 2.5.4, I am getting following errors in Xenomai (disable CONFIG_SMP, enable CONFIG_X86_UP_APIC and
>>> CONFIG_X86_UP_IOAPIC (*).)
>>>   
>>>     
>>>       
>> Just tested, got the same build error with 2.6.34.
>> If I patch 2.6.34 with prepare-kernel [1] it compiles,
>> if I use the debian packaged patch generated with prepare-patch [2] it
>> fails.
>>
>> I guess a fix is needed in prepare-patch for 2.6.34, but no time to look
>> closer now.
>>   
>>     
> patch for prepare-patch.sh attached.
> prepare-kernel.sh try's to find ipipe.h and uses the old or new tree
> structure. Is it ok to change this unconditionally in prepare-patch.sh?
> All adeos-patches in xenomai-2.5.git have ipipe.h in
> arch/$linux_arch/include/asm/, so i think yes.
>
>   

prepare-patch.sh worked with the wrong path until this commit for linux
2.6.33:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=c95fa08a3e17c3f2983c4cbf409f5c9ae47b7dec

> Stefan
>
>   
>
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>   



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: [Xenomai-help] kernel 2.6.32.11 with xenomai 2.5.3 fails to boot on ubuntu lucid system [PATCH]

[Paul]

On Wednesday 18 August 2010, Stefan Kisdaroczi wrote:
> On 17.08.2010 17:24, Stefan Kisdaroczi wrote:
> > On 17.08.2010 15:51, Hemal C.Bavishi wrote:
> >> When I tried to compile it with the latest version of kernel with
> >> xenomai 2.5.4, I am getting following errors in Xenomai (disable
> >> CONFIG_SMP, enable CONFIG_X86_UP_APIC and CONFIG_X86_UP_IOAPIC
> >> (*).)
> >
> > Just tested, got the same build error with 2.6.34.
> > If I patch 2.6.34 with prepare-kernel [1] it compiles,
> > if I use the debian packaged patch generated with prepare-patch [2]
> > it fails.
> >
> > I guess a fix is needed in prepare-patch for 2.6.34, but no time to
> > look closer now.
>
> patch for prepare-patch.sh attached.
> prepare-kernel.sh try's to find ipipe.h and uses the old or new tree
> structure. Is it ok to change this unconditionally in
> prepare-patch.sh? All adeos-patches in xenomai-2.5.git have ipipe.h
> in
> arch/$linux_arch/include/asm/, so i think yes.

As long as no one tries to include a patch for anything prior to 2.6.28 
(I think that is when everything moved to arch/*/include/asm) - There 
is only one ipipe patch in head currently for 2.6.25-ppc, but I doubt 
if anyone would be using it on a Debian build.

For that one case, I don't think it worth adding any additional 
complexity to generate a patch with a limited life span.


Regards, Paul.