[Xenomai] kernel problem xenomai 2.6.4 - linux 3.8.13

[Xenomai] kernel problem xenomai 2.6.4 - linux 3.8.13

[Frederik Bayart]

Hallo,

I'm using xenomai 2.6.4 on kernel 3.8.13 (patch ipipe-core-3.8.13-x86-4.patch)

In attachment you find the kernel config.

When I boot the kernel on a recent pc's (Intel(R) Core(TM) i5), I don't get problems, but if I install the same image on an older pc, (Intel(R) Core(TM) Duo CPU      T2500  @ 2.00GHz), I get periodic kernel traces after booting without running any real-time process (see below). In the dmesg in attachment, I see a stack trace.
(If I build a normal linux kernel without ipipe patch, I get no kernel traces.)

Has anyone has a suggestion what could go wrong ?

Kind regards,

Frederik


Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.236006] BUG: soft lockup - CPU#0 stuck for 41s! [swapper/0:0]

Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.236006] I-pipe domain Linux

Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.236006] Process swapper/0 (pid: 0, ti=c15a8000 task=c15b5280 task.ti=c15a8000)

Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.236006] Stack:

Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.236006] Call Trace:

Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.236006] Code:  Bad EIP value.

Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.240001] BUG: soft lockup - CPU#1 stuck for 41s! [swapper/1:0]

Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.240001] I-pipe domain Linux

Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.240001] Process swapper/1 (pid: 0, ti=decb6000 task=decaa490 task.ti=decb6000)

Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.240001] Stack:

Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.240001] Call Trace:

Message from syslogd@alsipmcp at Nov  6 17:48:01 ...
 kernel:[   71.240001] Code:  Bad EIP value.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: config-3.8.13_x86-xeno-2.6.4_3p.0.3
Type: application/octet-stream
Size: 99653 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20151106/2fb9b344/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.log
Type: text/x-log
Size: 42515 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20151106/2fb9b344/attachment.bin>

Re: [Xenomai] kernel problem xenomai 2.6.4 - linux 3.8.13

[Gilles Chanteperdrix]

On Fri, Nov 06, 2015 at 04:58:40PM +0000, Frederik Bayart wrote:
> Hallo,
> 
> I'm using xenomai 2.6.4 on kernel 3.8.13 (patch ipipe-core-3.8.13-x86-4.patch)
> 
> In attachment you find the kernel config.
> 
> When I boot the kernel on a recent pc's (Intel(R) Core(TM) i5), I don't get problems, but if I install the same image on an older pc, (Intel(R) Core(TM) Duo CPU      T2500  @ 2.00GHz), I get periodic kernel traces after booting without running any real-time process (see below). In the dmesg in attachment, I see a stack trace.
> (If I build a normal linux kernel without ipipe patch, I get no kernel traces.)
> 
> Has anyone has a suggestion what could go wrong ?

The NULL EIP suggest an NULL handler. Any chance to test something
more recent? Like xenomai 2.6 git head, with the latest I-pipe patch
for 3.18?

-- 
					    Gilles.
https://click-hack.org

Re: [Xenomai] kernel problem xenomai 2.6.4 - linux 3.8.13

[Frederik Bayart]

>On Sunday, 8 November 2015, 19:04, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
>
>On Fri, Nov 06, 2015 at 04:58:40PM +0000, Frederik Bayart wrote:
>
>> Hallo,
>>
>> I'm using xenomai 2.6.4 on kernel 3.8.13 (patch ipipe-core-3.8.13-x86-4.patch)
>>
>> In attachment you find the kernel config.
>>
>> When I boot the kernel on a recent pc's (Intel(R) Core(TM) i5), I don't get problems, but if I install the same image on an older pc, (Intel(R) Core(TM) Duo CPU      T2500  @ 2.00GHz), I get periodic kernel traces after booting without running any real-time process (see below). In the dmesg in attachment, I see a stack trace.
>> (If I build a normal linux kernel without ipipe patch, I get no kernel traces.)
>>
>> Has anyone has a suggestion what could go wrong ?
>
>
>The NULL EIP suggest an NULL handler. Any chance to test something
>more recent? Like xenomai 2.6 git head, with the latest I-pipe patch
>for 3.18?
>
>Gilles.

First impression is that building and installing xenomai 2.6 git head with ipipe-core-3.18.20-x86-3.patch seems to solve the problem.
The problem was still existing in xenomai 2.6.4 and kernel 3.14.17, so I guess the problem might been fixed after the release of 2.6.4
I will test further.

Thanks for the help.

Frederik

Re: [Xenomai] kernel problem xenomai 2.6.4 - linux 3.8.13

[Gilles Chanteperdrix]

On Tue, Nov 10, 2015 at 05:16:15PM +0000, Frederik Bayart wrote:
> >On Sunday, 8 November 2015, 19:04, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
> >
> >On Fri, Nov 06, 2015 at 04:58:40PM +0000, Frederik Bayart wrote:
> >
> >> Hallo,
> >>
> >> I'm using xenomai 2.6.4 on kernel 3.8.13 (patch ipipe-core-3.8.13-x86-4.patch)
> >>
> >> In attachment you find the kernel config.
> >>
> >> When I boot the kernel on a recent pc's (Intel(R) Core(TM) i5), I don't get problems, but if I install the same image on an older pc, (Intel(R) Core(TM) Duo CPU      T2500  @ 2.00GHz), I get periodic kernel traces after booting without running any real-time process (see below). In the dmesg in attachment, I see a stack trace.
> >> (If I build a normal linux kernel without ipipe patch, I get no kernel traces.)
> >>
> >> Has anyone has a suggestion what could go wrong ?
> >
> >
> >The NULL EIP suggest an NULL handler. Any chance to test something
> >more recent? Like xenomai 2.6 git head, with the latest I-pipe patch
> >for 3.18?
> >
> >Gilles.
> 
> First impression is that building and installing xenomai 2.6 git head with ipipe-core-3.18.20-x86-3.patch seems to solve the problem.
> The problem was still existing in xenomai 2.6.4 and kernel 3.14.17, so I guess the problem might been fixed after the release of 2.6.4
> I will test further.

As a rule of thumb, when using an old version of Xenomai, you should
update the I-pipe to the latest version corresponding to the branch
you cant to use. So, for 3.14, you should use this Ipipe patch:
http://xenomai.org/downloads/ipipe/v3.x/x86/ipipe-core-3.14.44-x86-10.patch

Regards.

-- 
					    Gilles.
https://click-hack.org