From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Arnaud Degroote <arnaud.degroote@isae.fr>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Support of Beagleboard xm rev C on 3.14-ipipe
Date: Tue, 01 Jul 2014 11:24:43 +0200 [thread overview]
Message-ID: <53B27E5B.10507@xenomai.org> (raw)
In-Reply-To: <20140701083910.GA28764@dmia-degroote.isae.fr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/01/2014 10:39 AM, Arnaud Degroote wrote:
> On 30/Jun - 21:06, Gilles Chanteperdrix wrote:
>> On 06/30/2014 08:41 PM, DEGROOTE Arnaud wrote:
>>>
>>> On Monday, June 30, 2014 18:13 CEST, Gilles Chanteperdrix
>>> <gilles.chanteperdrix@xenomai.org> wrote:
>>>
>>> On 06/30/2014 06:06 PM, Arnaud Degroote wrote:
>>>>>> On 30/Jun - 17:48, Gilles Chanteperdrix wrote:
>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>>>>>
>>>>>>> On 06/30/2014 05:45 PM, Arnaud Degroote wrote:
>>>>>>>> On 30/Jun - 17:26, Gilles Chanteperdrix wrote:
>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>>>>>>>
>>>>>>>>> On 06/30/2014 05:18 PM, Arnaud Degroote wrote:
>>>>>>>>>> On 30/Jun - 14:37, Arnaud Degroote wrote: [snip]
>>>>>>>>>>>> Have you checked that the exact same kernel
>>>>>>>>>>>> configuration, only without CONFIG_IPIPE and
>>>>>>>>>>>> CONFIG_XENOMAI runs correctly under load?
>>>>>>>>>>>
>>>>>>>>>>> The system seems to hang even without
>>>>>>>>>>> CONFIG_IPIPE. The linux-yocto kernel seems to
>>>>>>>>>>> work properly (it looks like a 3.14rc8), I will
>>>>>>>>>>> check precisely against linux kernel v3.14.
>>>>>>>>>>
>>>>>>>>>> Some additional information
>>>>>>>>>>
>>>>>>>>>> linux mainstream kernel on tag v3.14 runs fine on
>>>>>>>>>> the platform. The system hangs with ipipe branch
>>>>>>>>>> ipipe-3.14 (without xenomai stuff, and without
>>>>>>>>>> CONFIG_IPIPE).
>>>>>>>>>
>>>>>>>>> In the two cases the configuration is exactly the
>>>>>>>>> same?
>>>>>>>>>
>>>>>>>> Yes, there are no semantic difference. The only diff
>>>>>>>> are
>>>>>>>>
>>>>>>>> CONFIG_LOCALVERSION
>>>>>>>>
>>>>>>>> and the ipipe kernel has the extra line
>>>>>>>>
>>>>>>>> # CONFIG_IPIPE is not set
>>>>>>>>
>>>>>>> If you have a rootfs without hardfp (based on the
>>>>>>> codesourcery toolchain for instance), could you try to
>>>>>>> boot without CONFIG_VFP?
>>>>>>
>>>>>> I don't have such toolchain for the moment, but I can try
>>>>>> to hack
>>>
>>>>>> my current yocto toolchain to test without hardfp.
>>>
>>> The codesourcery toolchain is available for download, already
>>> compiled.
>>>
>>>>>> Still, I have compiled a kernel without CONFIG_VFP but it
>>>>>> still hangs in the same place, so I don't think it is
>>>>>> related to the current issue.
>>>
>>> If you are running a rootfs with hardfp with a kernel without
>>> CONFIG_VFP, the system should not finish booting.
>>>
>>>> Yes obviously, but at the moment, I don't arrive to the call
>>>> to /sbin/init
>>>
>>> Where does the system hang exactly? We were talking about a
>>> hang when running switchtest. How do you produce the hang on a
>>> system without CONFIG_XENOMAI, since obviously you can not run
>>> switchtest?
>>>
>>>> Yes, sorry, I was not very precise. I get the same behaviour
>>>> than described in the beginning of the thread, i.e. the
>>>> kernel hangs during the boot (and nothing happens after
>>>> that). As I said previously, the hang happens with
>>>> linux-ipipe without CONFIG_IPIPE. The various change of
>>>> configuration makes it "work" by accident.
>>>
>>>> An hanging kernel boot msg is available on my mail of 24
>>>> June, 14:21 CEST. I cannont reproduce it at the moment, as
>>>> I'm not anymore at work.
>>
>> As I said in an earlier mail, please do not mix everything, and
>> try and debug one issue at the time.
>>
>> From your configuration I gather you do not use the serial
>> console (CONFIG_PINCTRL_SINGLE is missing), could you enable the
>> serial console to try and obtain more information about this
>> kernel freeze?
>
> I'm already using the serial console. PINCTRL_SINGLE is not
> necessary for beagleboard xM AFAIU.
Finding a reproducible freeze location is relatively easy, enable
CONFIG_DEBUG_LL, and put calls to printascii in the initialization
functions, starting with init/main.c, and refining inside these
functions when you know a bit more.
>>
>> Or alternatively, could you restore the configuration options
>> which "get the system working", so that we can go back to what we
>> were testing: the configuration where switchtest hangs, without
>> CONFIG_IPIPE, and generate some load with the hackbench test, to
>> try and simulate a bit what switchtest is doing. I am also
>> interested by the same configuration with CONFIG_XENOMAI, but
>> without CONFIG_VFP, and running the switchtest rtk0 rtk0 test.
>
> I don't have any working configuration with linux-ipipe without
> CONFIG_IPIPE, it always hang during the boot, through I don't try
> yet with CONFIG_IPIPE, without CONFIG_XENOMAI. Does it make any
> sense to do some test in this configuration ?
>
> Otherwise, I will build a toolchain without hardfp to do the last
> test.
As I said, you can install the codesourcery toolchain, you do not need
to build it. Anyway, let us wait to know in what function the freeze
occurs.
- --
Gilles.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iD8DBQFTsn5bGpcgE6m/fboRArF2AJ4jH6yzQLrDOeFodbKJedQAJxKtEQCcCIHk
bvRDa6k0hp8SA3zlnO0um8w=
=rUNd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-07-01 9:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 9:08 [Xenomai] Support of Beagleboard xm rev C on 3.14-ipipe Arnaud Degroote
2014-06-23 9:22 ` Gilles Chanteperdrix
2014-06-23 11:18 ` Arnaud Degroote
2014-06-23 23:45 ` Gilles Chanteperdrix
2014-06-24 6:23 ` Arnaud Degroote
2014-06-24 6:29 ` Gilles Chanteperdrix
2014-06-24 12:21 ` Arnaud Degroote
2014-06-24 18:31 ` Gilles Chanteperdrix
2014-06-25 8:11 ` Arnaud Degroote
2014-06-25 8:37 ` Gilles Chanteperdrix
2014-06-25 9:47 ` Arnaud Degroote
2014-06-25 17:01 ` Gilles Chanteperdrix
2014-06-25 22:23 ` Gilles Chanteperdrix
2014-06-26 7:56 ` Arnaud Degroote
2014-06-26 11:08 ` Gilles Chanteperdrix
2014-06-26 11:19 ` Arnaud Degroote
2014-06-26 17:27 ` Gilles Chanteperdrix
2014-06-27 7:22 ` Arnaud Degroote
2014-06-27 16:27 ` Gilles Chanteperdrix
2014-06-30 8:16 ` Arnaud Degroote
2014-06-30 8:26 ` Arnaud Degroote
2014-06-30 8:59 ` Gilles Chanteperdrix
2014-06-30 9:13 ` Arnaud Degroote
2014-06-30 9:36 ` Gilles Chanteperdrix
2014-06-30 10:16 ` Gilles Chanteperdrix
2014-06-30 12:01 ` Arnaud Degroote
2014-06-30 12:07 ` Gilles Chanteperdrix
2014-06-30 12:37 ` Arnaud Degroote
2014-06-30 12:44 ` Gilles Chanteperdrix
2014-06-30 15:18 ` Arnaud Degroote
2014-06-30 15:26 ` Gilles Chanteperdrix
2014-06-30 15:45 ` Arnaud Degroote
2014-06-30 15:48 ` Gilles Chanteperdrix
2014-06-30 16:06 ` Arnaud Degroote
2014-06-30 16:13 ` Gilles Chanteperdrix
2014-06-30 18:41 ` DEGROOTE Arnaud
2014-06-30 19:06 ` Gilles Chanteperdrix
2014-07-01 8:39 ` Arnaud Degroote
2014-07-01 9:24 ` Gilles Chanteperdrix [this message]
2014-07-01 15:51 ` Arnaud Degroote
2014-07-01 19:22 ` Gilles Chanteperdrix
2014-07-02 11:41 ` Arnaud Degroote
2014-07-02 17:59 ` Gilles Chanteperdrix
2014-07-03 8:38 ` Arnaud Degroote
2014-07-03 12:34 ` Gilles Chanteperdrix
2014-07-04 7:19 ` Arnaud Degroote
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=53B27E5B.10507@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=arnaud.degroote@isae.fr \
--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.