Re: Cannot get basic latency test to work on Intel platform

Paolo Mantegazza <[email protected]> Wed, 1 Mar 2017 08:48:57 +0100
Newsgroups gmane.linux.real-time.rtai
Message-ID <[email protected]>
On 03/01/2017 12:36 AM, Bill Jenkins wrote:
> Hi Asier,
>
>> On Feb 27, 2017, at 3:20 AM, Asier <[email protected] 
>> <mailto:[email protected]>> wrote:
>>
>> Hi Bill,
>>
>> The hangs you mention, well could be similar to the ones I was 
>> experiencing related with Ubuntu console terminal. Could you try 
>> launching the tests from within the tty1-6 terminal consoles or from 
>> "xterm" console instead of the default ubuntu terminal console?
>>
>> If this works,probably in the latest Vulcano CVS you will find the 
>> issue fixed.
>
> Thank you for the suggestion. I did try it with xterm but found the 
> same behavior.

As a further test, can you insmod rtai_hal.ko and rtai_sched.ko by hand, 
just to be sure that is the scheduler initializations that fails.
Once sure of that, for a simple diagnosis it is enough to place a moving 
return in the scheduler module init. It may need a few restarts but once 
the culprit op is framed fixing it should be simple.
Paolo.

>
>>
>> Asier.
>>
>>
>> On Mon, Feb 27, 2017 at 10:22 AM, Paolo Mantegazza 
>> <[email protected] <mailto:[email protected]>> wrote:
>>
>>     Retry the latest Vulcano CVS.. LIkely it will change nothing, but
>>     just to know.
>>     In any case before trying any test watch first what happens when
>>     you work for a bit of time with Linux after having insmoded
>>     rtai_hal.ko.
>>
>
> Paolo, thank you for your response as well.
>
> I got the latest from the Vulcano repository, but as you suspected, it 
> did not change the result.
> If I just generally use the system after only insmodding rtai_hal.ko, 
> the system seems to be
> stable. It is not until I try to insmod rtai_sched.ko that it hangs 
> during insmod.
>
>>     Did you try it on machine that was running RTAI well already?
>>
>
> I have not. Our previous use of RTAI was with the 2.6.32 kernel on 
> older hardware.
Could you? I'm running Vulcano-Linux-4.1.18 on at least 3 old hardwares, 
with TSC.

>
> Best regards,
> Bill
>
>
>>     Paolo.
>>
>>
>>     On 02/27/2017 07:29 AM, Bill Jenkins wrote:
>>
>>         Hi Everyone,
>>
>>         I have been trying to get RTAI up and running with the latest
>>         rtai-5.0-test2
>>         running on a patched 4.1.18 kernel on Intel processors. It
>>         seems to me
>>         that this should work, as there is nothing special I am
>>         trying to do yet
>>         other than just run the latency test in the test suite.
>>
>>         There must be something I am not doing correctly, because it
>>         always fails
>>         the same way and I have tried this on several different
>>         motherboards (processors
>>         I've tried so far include Atom x5, i3, and 3160 braswell).
>>
>>         After patching the kernel and doing the install of rtai, the
>>         system always hangs
>>         when I try to run the kern/latency/run test. The hang happens
>>         when insmod'ing
>>         rtai_sched.
>>
>>         Here are the basic steps I've tried on each system:
>>
>>         1. Install Ubuntu 16.10 (I've also had this problem with
>>         Ubuntu 14.04)
>>         2. Install gcc/g++ 4.9
>>         3. Get 4.1.18 kernel from kernel.org <http://kernel.org/>,
>>         configure it using localmodconfig, and then
>>                 build/install it and reboot into 4.1.18.
>>         4. Get RTAI 5.0-test2 and patch the 4.1.18 kernel with it.
>>         5. Build/install patched 4.1.18 and reboot into the patched
>>         4.1.18 kernel.
>>         6. I take the default configuration values in RTAI, with the
>>         exception of changing
>>                 the number of CPUs to 4. Then build/install RTAI.
>>         7. Try to run the testsuite/kern/latency test and the system
>>         hangs.
>>
>>         Anyone know what I might be missing? I can't imagine that
>>         such a simple
>>         case on Intel processors does not work.
>>
>>         Thanks in advance for any help,
>>         Bill
>>         _______________________________________________
>>         Rtai mailing list
>>         [email protected] <mailto:[email protected]>
>>         https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
>>         <https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai>
>>
>>
>>
>>     _______________________________________________
>>     Rtai mailing list
>>     [email protected] <mailto:[email protected]>
>>     https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
>>     <https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai>
>>
>>
>> _______________________________________________
>> Rtai mailing list
>> [email protected] <mailto:[email protected]>
>> https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
>

_______________________________________________
Rtai mailing list
[email protected]
https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai