From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4D237B33.7080100@domain.hid>
Date: Tue, 04 Jan 2011 20:55:31 +0100
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
MIME-Version: 1.0
References: <4D233AB4.5070702@domain.hid>
	<4D2352C9.9050006@domain.hid>	<4D2377B5.1040807@domain.hid>	<4D23785B.5050108@domain.hid>
	<4D2379EF.5@domain.hid> <4D237A89.3010205@domain.hid>
In-Reply-To: <4D237A89.3010205@domain.hid>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Xenomai-help] Xenomai failure
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: Tamas Szklenar <tszklenar@domain.hid>
Cc: xenomai@xenomai.org

Gilles Chanteperdrix wrote:
> Tamas Szklenar wrote:
>> Hi
>>
>> Here is the kern.log, I made some kernel configurations because of the 
>> used hardware parts, but the main systems config was unchanged...
> 
> Could we only have one boot? The one which fails?

Just up to the failing modprobe. As said in the link Stefan pointed you to:

"Please provide the full kernel logs, from the bootloader, up to the bug
itself."

-- 
                                                                Gilles.