From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4EB6CE93.4060801@domain.hid>
Date: Sun, 06 Nov 2011 19:14:43 +0100
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
MIME-Version: 1.0
References: <4EB6CA3B.1040608@domain.hid> <4EB6CB8A.2020303@domain.hid>
	<4EB6CDB0.6070306@domain.hid>
In-Reply-To: <4EB6CDB0.6070306@domain.hid>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Xenomai-help] Xenomai 2.6.0 - kernel seg faults on AT91
List-Id: Help regarding installation and common use of Xenomai
	<xenomai.xenomai.org>
List-Unsubscribe: <https://mail.gna.org/options/xenomai-help>,
	<mailto:xenomai-help-request@domain.hid>
List-Archive: </public/xenomai-help>
List-Post: <mailto:xenomai@xenomai.org>
List-Help: <mailto:xenomai-help-request@domain.hid>
List-Subscribe: <https://mail.gna.org/listinfo/xenomai-help>,
	<mailto:xenomai-help-request@domain.hid>
To: at91_enthus <nwromania@domain.hid>
Cc: xenomai@xenomai.org

On 11/06/2011 07:10 PM, at91_enthus wrote:
> On 11/06/2011 12:01 PM, Gilles Chanteperdrix wrote:
>> On 11/06/2011 06:56 PM, at91_enthus wrote:
>>> Hi.
>>>
>>> I gave Xenomai 2.6.0 a try and installed a newly patched kernel on my
>>> AT91SAM9G20 board.
>>>
>>> Here is my setup:
>>>
>>> proc:   AT91SAM9G20
>>> kernel: 2.6.35.9
>>> OS: embedded Debian Squeeze
>>>
>>> The board boots fine up to stage 2 (user terminal). Sometimes, I am able
>>> to get a login terminal, despite seg fault messages.
>>>
>>> A similar behavior occurs in a Xenomai capable 2.6.37 kernel, only
>>> without the fault messages. In this case the board simply freezes.
>>>
>>> I included the files (.config and fault messages) in the attachments.
>>>
>> You enabled CONFIG_FCSE_GUARANTEED, I do not think Debian squeeze can
>> boot with that, you need a real embedded filesystem, or use
>> CONFIG_FCSE_BEST_EFFORT.
>>
>>
> 
> Since I've started looking in to Xenomai, I have been using FCSE
> "guaranteed" and "best efort"  along with both Debian Squeeze and Lenny
> (Xenomai 2.5 series) without any issues.
> 
> I'll change the FCSE setting to see if I get a different behavior.

If the problem is due to processes trying to go over the 32MB limit, you
can enable CONFIG_ARM_FCSE_MESSAGES, and observe the kernel console,
with this option enabled, you should get clear error messages.

Otherwise, enable CONFIG_DEBUG_USER, and pass debug_user=29 on the
kernle command line to know the origin of the fault, still with
CONFIG_ARM_FCSE_MESSAGES on for additional details.


-- 
                                                                Gilles.