Re: Rtai Digest, Vol 104, Issue 12

Il giorno gio 25 ago 2016 alle ore 10:37 <[email protected]> ha scritto:

> Send Rtai mailing list submissions to
>         [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
> or, via email, send a message with subject or body 'help' to
>         [email protected]
>
> You can reach the person managing the list at
>         [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Rtai digest..."
>
>
> Today's Topics:
>
>    1. Re: calibration fails with alert....... (YamatoKira)
>    2. Building RTAI [SEC=UNCLASSIFIED] (Thamm, Russell)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 25 Aug 2016 10:28:03 +0800
> From: YamatoKira <[email protected]>
> To: Mantegazza Paolo <[email protected]>, "[email protected]"
>         <[email protected]>
> Subject: Re: [Rtai] calibration fails with alert.......
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="gb2312"
>
>
>
>
>
>
>
>
>
>
> Thanks,
> Paolo, for your kindheartedness
> This
> morning I also run the six test procedures under /realtime/testsuite
> directory. The three ones under /kern sub-directory can generate an
> result, while the other three under /user sub-directory fails with
> the similar page request. The inserting of .ko files with insmod
> command fails too, which cause the system to be responseless.
>
>
>
> Do
> you think this phenomenon relates to the configuration of the
> kernel/RTAI? Or do I have to reinstall the Ubuntu and RTAI5.0 as you
> indicated?
>
>
>
>
>
>                 yours
> C.P.
>
>
>
> > From: [email protected]
> > To: [email protected]; [email protected]
> > Subject: RE: [Rtai] calibration fails with alert.......
> > Date: Wed, 24 Aug 2016 20:44:15 +0000
> >
> > I do not think that the calibration failed, as you can see the following
> logged: RTAI[sched]: timer setup = 160 ns, resched latency = 3783 ns.
> > Then there is a strange page  fault, associated to an RTAI call
> (rtai_lxrt_invoke).
> > I suggest passing to the newer rtai-5.0-test2.
> >
> > Paolo
> >
> > ________________________________________
> > From: Rtai [[email protected]] on behalf of YamatoKira [
> [email protected]]
> > Sent: Wednesday, August 24, 2016 4:27 PM
> > To: [email protected]
> > Subject: [Rtai] calibration fails with alert.......
> >
> > Hello everyone~
> > I meet some problem when using RTAI
> > Can you help me to figure it out?
> >
> > My platform is Ubuntu 14.02 with a kernel 3.16.0 and RTAI 4.1.1
> > I compiled the RTAI and run the test procedure, and the calibration
> fails and I saw the alert message by dmesg:
> > kern  :info  : [ 1645.358113] I-pipe: head domain RTAI registered.
> > kern  :info  : [ 1645.358117] RTAI[hal]: compiled with gcc version 4.8.4
> (Ubuntu 4.8.4-2ubuntu1~14.04.3) .
> > kern  :info  : [ 1645.358123] RTAI[hal]: mounted (IPIPE-NOTHREADS,
> IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
> > kern  :warn  : [ 1645.358125] SYSINFO: CPUs 1, LINUX APIC IRQ 4353,
> TIM_FREQ 6235909, CLK_FREQ 2294727000, CPU_FREQ 2294727000
> > kern  :warn  : [ 1645.358126] RTAI_APIC_TIMER_IPI: RTAI DEFINED 4354,
> VECTOR 4355; LINUX_APIC_TIMER_IPI: RTAI DEFINED 4353, VECTOR 4353
> > kern  :warn  : [ 1645.358128] TIMER NAME: lapic; VARIOUSLY FOUND APIC
> FREQs: 6235909, 6235909, 6235750
> > kern  :info  : [ 1645.651156] RTAI[malloc]: global heap size = 2097152
> bytes, <BSD>.
> > kern  :warn  : [ 1645.651175] , kstacks pool size = 524288 bytes.
> > kern  :info  : [ 1645.651177] RTAI[sched]: hard timer type/freq =
> APIC/6235909(Hz); default timing: periodic; linear timed lists.
> > kern  :info  : [ 1645.651178] RTAI[sched]: Linux timer freq = 250 (Hz),
> TimeBase freq = 2294727000 hz.
> > kern  :info  : [ 1645.651179] RTAI[sched]: timer setup = 160 ns, resched
> latency = 3783 ns.
> > kern  :alert : [ 1645.669339] BUG: unable to handle kernel paging
> request at 00007fff08c89e50
> > kern  :alert : [ 1645.669368] IP: [<ffffffffc0c36856>]
> rtai_lxrt_invoke+0x496/0x1180 [rtai_sched]
> > kern  :warn  : [ 1645.669396] PGD 6df25067 PUD 375df067 PMD 58dbc067 PTE
> 8000000059a65867
> > kern  :warn  : [ 1645.669420] Oops: 0001 [#2] SMP
> > kern  :warn  : [ 1645.669432] Modules linked in: rtai_sched(OE)
> rtai_hal(OE) rfcomm(E) bnep(E) nls_iso8859_1(E) snd_hda_codec_hdmi(E)
> snd_hda_codec_realtek(E) snd_hda_codec_generic(E) intel_rapl(E)
> x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) kvm(E)
> crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E) aesni_intel(E)
> aes_x86_64(E) lrw(E) gf128mul(E) glue_helper(E) arc4(E) ablk_helper(E)
> iwlmvm(E) mac80211(E) uvcvideo(E) cryptd(E) videobuf2_vmalloc(E) joydev(E)
> serio_raw(E) videobuf2_memops(E) videobuf2_core(E) v4l2_common(E)
> videodev(E) media(E) btusb(E) lpc_ich(E) mac_hid(E) snd_hda_intel(E)
> snd_hda_controller(E) snd_hda_codec(E) iwlwifi(E) bluetooth(E) snd_hwdep(E)
> snd_pcm(E) snd_seq_midi(E) snd_seq_midi_event(E) snd_rawmidi(E) snd_seq(E)
> snd_seq_device(E) snd_timer(E) snd(E) 6lowpan_iphc(E) cfg80211(E) radeon(E)
> i915(E) ttm(E) soundcore(E) drm_kms_helper(E) parport_pc(E) ppdev(E) lp(E)
> parport(E) drm(E) mei_me(E) rtsx_pci_ms(E) memstick(E) mei(E)
> i2c_algo_bit(E)
>  shpchp(E) hid_generic(E) usbhid(E) hid(E) rtsx_pci_sdmmc(E) r8169(E)
> mii(E) rtsx_pci(E) ahci(E) libahci(E) [last unloaded: rtai_hal]
> > kern  :warn  : [ 1645.673932] CPU: 0 PID: 19075 Comm: calibration_hel
> Tainted: G      D    OE 3.16.0-rtai #1
> > kern  :warn  : [ 1645.675002] task: ffff8801337fe540 ti:
> ffff880058f7c000 task.ti: ffff880058f7c000
> > kern  :warn  : [ 1645.676047] RIP: 0010:[<ffffffffc0c36856>]
> [<ffffffffc0c36856>] rtai_lxrt_invoke+0x496/0x1180 [rtai_sched]
> > kern  :warn  : [ 1645.677087] RSP: 0018:ffff880058f7fef8  EFLAGS:
> 00010202
> > kern  :warn  : [ 1645.678094] RAX: ffff8801337fe540 RBX:
> 0000000000000000 RCX: 00007f4b0957d709
> > kern  :warn  : [ 1645.679086] RDX: 00000000000003ea RSI:
> 00007fff08c89e50 RDI: 00000000003ea828
> > kern  :warn  : [ 1645.680051] RBP: ffff880058f7ff50 R08:
> 000000000000000f R09: 00007fff08c89e50
> > kern  :warn  : [ 1645.680989] R10: 0000000000000001 R11:
> 0000000000003206 R12: 00007fff08c89e50
> > kern  :warn  : [ 1645.681911] R13: 00000000003ea828 R14:
> 0000000000000000 R15: 0000000000000000
> > kern  :warn  : [ 1645.682825] FS:  00007f4b09e8a740(0000)
> GS:ffff88015ec00000(0000) knlGS:0000000000000000
> > kern  :warn  : [ 1645.683732] CS:  0010 DS: 0000 ES: 0000 CR0:
> 000000008005003b
> > kern  :warn  : [ 1645.684631] CR2: 00007fff08c89e50 CR3:
> 0000000058e87000 CR4: 00000000003407f0
> > kern  :warn  : [ 1645.685535] DR0: 0000000000000000 DR1:
> 0000000000000000 DR2: 0000000000000000
> > kern  :warn  : [ 1645.686431] DR3: 0000000000000000 DR6:
> 00000000fffe0ff0 DR7: 0000000000000400
> > kern  :warn  : [ 1645.687336] I-pipe domain Linux
> > kern  :warn  : [ 1645.688225] Stack:
> > kern  :warn  : [ 1645.689108]  ffff880058f7ff24 ffff880058f7ff50
> ffffffff821758b3 00000001337fe540
> > kern  :warn  : [ 1645.690011]  ffff8801335b2e60 0000000100000000
> 00007fff08c89dd0 0000000000400dd0
> > kern  :warn  : [ 1645.690909]  00007fff08c89fe0 0000000000000000
> 0000000000000000 ffff880058f7ff68
> > kern  :warn  : [ 1645.691805] Call Trace:
> > kern  :warn  : [ 1645.692699]  [<ffffffff821758b3>] ?
> __mm_populate+0x113/0x130
> > kern  :warn  : [ 1645.693606]  [<ffffffffc0c3598d>]
> lxrt_intercept_syscall+0x8d/0x130 [rtai_sched]
> > kern  :warn  : [ 1645.694518]  [<ffffffff82102697>]
> __ipipe_notify_syscall+0x17/0x30
> > kern  :warn  : [ 1645.695435]  [<ffffffff82698f4e>]
> pipeline_syscall+0xa/0x17
> > kern  :warn  : [ 1645.696338] Code: e2 ff 07 00 00 31 ff e8 41 78 00 00
> e9 40 fe ff ff 48 c7 c7 e8 11 c4 c0 31 c0 e8 86 53 f7 ff 48 c7 c0 da ff ff
> ff e9 b1 fc ff ff <48> 8b 1e 8d 8a 18 fc ff ff 83 f9 20 48 89 d8 0f 87 aa
> 0c 00 00
> > kern  :alert : [ 1645.698298] RIP  [<ffffffffc0c36856>]
> rtai_lxrt_invoke+0x496/0x1180 [rtai_sched]
> > kern  :warn  : [ 1645.699260]  RSP <ffff880058f7fef8>
> > kern  :warn  : [ 1645.700215] CR2: 00007fff08c89e50
> > kern  :warn  : [ 1645.701162] ---[ end trace a0735b74567a0a8b ]---
> > kern  :warn  : [ 1645.720355] RTAI[malloc]: unloaded.
> > kern  :info  : [ 1651.447510] RTAI[sched]: unloaded (forced
> hard/soft/hard transitions: traps 0, syscalls 0).
> > kern  :info  : [ 1651.657784] I-pipe: head domain RTAI unregistered.
> > kern  :info  : [ 1651.657791] RTAI[hal]: unmounted.
> >
> > I  really wonder how the alert is generated........
> > BTW: although the calibration can not run , the kernel latency test has
> an output and I saw that the rtai modules were loaded by lsmod.
> >
> > Thank you for your patience and kindness
> >
> >
>                                              Yours: C.P.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.rtai.org/pipermail/rtai/attachments/20160825/6ef97c62/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Thu, 25 Aug 2016 00:05:19 +0000
> From: "Thamm, Russell" <[email protected]>
> To: "[email protected]" <[email protected]>
> Subject: [Rtai] Building RTAI [SEC=UNCLASSIFIED]
> Message-ID:
>         <
> 5D28B2B70064DB478038C53DF4F4CADF464ED3FE@EDNREX523.dsto.defence.gov.au>
>
> Content-Type: text/plain; charset="us-ascii"
>
> UNCLASSIFIED
> Hi,
>
> I am trying to install RTAI on CentOS 7 but I can't get the patched kernel
> to boot.
>
> I am trying to follow the installation instructions
> (RTAI_User_Manual_34_03.pdf).
>
> I downloaded a kernel (3.10.32) that is close to the current kernel and
> has RTAI patches.
> I patched and configured , built and installed this kernel.
>
> When I try to boot this kernel, I just see a blinking cursor.
>
> It seems that the patched kernel fails at the start of the boot process.
> There appears to be no entry in /var/log/messages from attempting to boot
> the modified kernel.
>
> I tried repeating the exercise without applying the RTAI patch.
> This boots and everything appears to run correctly.
>
> I have tried this several times, the unpatched kernel will boot and the
> patched kernel doesn't.
>
> I tried configuring RTAI before building the kernel but it reported no
> error.
>
> I note that there is no configuration item for "Use register arguments",
> so I cannot disable this.
>
> Any ideas?
>
> Alternately any suggestions for a suitable distribution to use instead of
> CentOS


Have you disabled legacy ipipe support ?
BTW I can recommend you to use ubuntu or debian jessie 14.04 since there
are a lot of guides about rtai kernel patching\compiling on the net and is
proven to work.
Personally I succesfully installed RTAI on Arch Linux, Debian Jessie,
Debian Stretch, Tanglu, openSUSE and Ubuntu but never tried
Fedora\RHEL\CentOS\ScientificLinux.


> Cheers
> Russell
>
> IMPORTANT: This email remains the property of the Department of Defence
> and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If
> you have received this email in error, you are requested to contact the
> sender and delete the email.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.rtai.org/pipermail/rtai/attachments/20160825/0188d839/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Rtai mailing list
> [email protected]
> https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
>
> ------------------------------
>
> End of Rtai Digest, Vol 104, Issue 12
> *************************************
>

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