All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Christensen <jbc@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] kernel threads crash
Date: Mon, 11 Apr 2011 16:20:04 +0200	[thread overview]
Message-ID: <4DA30E14.6070401@domain.hid> (raw)
In-Reply-To: <1302531493.2054.355.camel@domain.hid>

Problem is the NIP in question is the address of the thread structure as
seen in the error message.

/Jesper


On 2011-04-11 16:18, Philippe Gerum wrote:
> On Mon, 2011-04-11 at 16:13 +0200, Jesper Christensen wrote:
>   
>> I have updated to xenomai 2.5.6, but i'm still seeing exceptions
>> (considerably less often though):
>>
>> Xenomai: suspending kernel thread b92a39d0 ('tt_upgw_0') at 0xb92a39d0
>> after exception #1792
>>     
> You should build your code statically into the kernel, not as a module,
> and find out which code raises the MCE.
>
> CONFIG_DEBUG_INFO=y, then objdump -dl vmlinux, looking for the NIP
> mentioned.
>
>   
>> /Jesper
>>
>>
>> On 2011-04-08 15:12, Philippe Gerum wrote:
>>     
>>> On Fri, 2011-04-08 at 14:58 +0200, Jesper Christensen wrote:
>>>   
>>>       
>>>> Hi
>>>>
>>>> I'm trying to implement some gateway functionality in the kernel on a
>>>> emerson CPCI6200 board, but have run into some strange errors. The
>>>> kernel module is made up of two threads that run every 1 ms. I have also
>>>> made use of the rtpc dispatcher in rtnet to dispatch control messages
>>>> from a netlink socket to the RT part of my kernel module.
>>>>
>>>> The problem is that when loaded the threads get suspended due to exceptions:
>>>>
>>>> Xenomai: suspending kernel thread b929cbc0 ('tt_upgw_0') at 0xb929cbc0
>>>> after exception #1792
>>>>
>>>> or
>>>>
>>>> Xenomai: suspending kernel thread b929cbc0 ('tt_upgw_0') at 0x0 after
>>>> exception #1025
>>>>
>>>> or
>>>>
>>>> Xenomai: suspending kernel thread b911f518 ('rtnet-rtpc') at 0xb911f940
>>>> after exception #1792
>>>>
>>>>
>>>> I have ported the "gianfar" driver from linux to rtnet.
>>>>
>>>> The versions and hardware are listed below. The errors are most likely
>>>> due to faulty software on my part, but i would like to ask if there are
>>>> any known issues with the versions or hardware i'm using. I would also
>>>> like to ask if there are any ways of further debugging the errors as i
>>>> am not getting very far with the above messages.
>>>>     
>>>>         
>>> A severe bug at kthread init was fixed in the 2.5.5.2 - 2.5.6 timeframe,
>>> which would cause exactly the kind of weird behavior you are seeing
>>> right now. The bug triggered random code execution due to stack memory
>>> pollution at init on powerpc for Xenomai kthreads:
>>> http://git.xenomai.org/?p=xenomai-rpm.git;a=commit;h=90699565cbce41f2cec193d57857bb5817efc19a
>>> http://git.xenomai.org/?p=xenomai-rpm.git;a=commit;h=da20c20d4b4d892d40c657ad1d32ddb6d0ceb47c
>>> http://git.xenomai.org/?p=xenomai-rpm.git;a=commit;h=a5886b354dc18f054b187b58cfbacfb60bccaf47
>>>
>>> You need at the very least those three patches (from the top of my
>>> head), but it would be much better to upgrade to 2.5.6.
>>>
>>>   
>>>       
>>>>
>>>> System info:
>>>>
>>>> Linux kernel: 2.6.29.6
>>>> i-pipe version: 2.7-04
>>>> processor: powerpc mpc8572
>>>> xenomai version: 2.5.3
>>>> rtnet version: 0.9.12
>>>>
>>>>     
>>>>         
>>>   
>>>       
>>
>> _______________________________________________
>> Xenomai-core mailing list
>> Xenomai-core@domain.hid
>> https://mail.gna.org/listinfo/xenomai-core
>>     
>   



  reply	other threads:[~2011-04-11 14:20 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 12:58 [Xenomai-core] kernel threads crash Jesper Christensen
2011-04-08 13:12 ` Philippe Gerum
2011-04-08 13:20   ` Jesper Christensen
2011-04-08 13:39     ` Philippe Gerum
2011-04-08 13:47       ` Jesper Christensen
2011-04-08 14:33       ` Jesper Christensen
2011-04-11 14:13   ` Jesper Christensen
2011-04-11 14:18     ` Philippe Gerum
2011-04-11 14:20       ` Jesper Christensen [this message]
2011-04-11 14:27         ` Philippe Gerum
2011-04-11 14:32           ` Jesper Christensen
2011-04-11 14:39             ` Philippe Gerum
2011-04-11 14:49               ` Jesper Christensen
2011-04-11 15:31                 ` Jesper Christensen
2011-04-12 13:31                   ` Jesper Christensen
2011-04-12 13:39                     ` Gilles Chanteperdrix
2011-04-12 13:40                       ` Jesper Christensen
2011-04-12 13:40                     ` Jan Kiszka
2011-04-12 13:45                       ` Jesper Christensen
2011-04-12 14:09                       ` Jesper Christensen
2011-04-12 14:14                         ` Jan Kiszka
2011-04-12 14:21                           ` Jesper Christensen
2011-04-12 15:24                             ` Jan Kiszka
2011-04-12 15:50                               ` Jesper Christensen
2011-04-19  7:26                             ` Jesper Christensen
2011-04-19  7:39                               ` Philippe Gerum
2011-04-19  7:58                                 ` Jesper Christensen
2011-04-19  8:02                                   ` Philippe Gerum
2011-04-19  8:42                                     ` Gilles Chanteperdrix
2011-04-19  9:29                                       ` Philippe Gerum
2011-04-19  9:30                                         ` Philippe Gerum
2011-04-19  9:34                                           ` Jesper Christensen
2011-04-11 14:34         ` Philippe Gerum
2011-04-11 14:35           ` Jesper Christensen
2011-04-11 14:23       ` Philippe Gerum
2011-04-11 14:36     ` Gilles Chanteperdrix
2011-04-08 19:15 ` Richard Cochran
2011-04-11  6:52   ` Jesper Christensen
2011-04-11  6:55     ` Richard Cochran
2011-04-11  6:59       ` Jesper Christensen
2011-04-11  9:18         ` Jan Kiszka
2011-04-11  9:26           ` Jesper Christensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DA30E14.6070401@domain.hid \
    --to=jbc@domain.hid \
    --cc=rpm@xenomai.org \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.