Re: sched: problem with paging request on linux 3.16

What happened is what I expected: the fact that kernel space tests work, 
but not user space ones, confirms that RTAI own syscalls from user space 
are not working on your system.
As I said, the only case I saw was because of syscalls audite working, 
which requires its enabling in the kernel and a related daemon set to do so.

Since the mechanism used by RTAI-lxrt has been at the base of user space 
real time for quite more than a decade, I've no further clue for it at 
the moment, beside those you have carried out, even in a negative sense.

Since problems like this may happen during development, showroom CVS has 
some tests to help diagnose the cause through RTAI own srq and without 
using the scheduler.  You can find them in showroom/v3.x/hal_test.

If you want to go on and diagnose it, to avoid flooding this list with 
something that may be of little interest to RTAI users, I'd suggest to 
continue this thread privately. We'll report back to the list if and 
when we'll fix it.

Paolo

On 05/10/2017 02:15 PM, PAUL-SOFTWARE wrote:
>
> Hello Paolo,
>
> Sorry to bother you again..
>
> I hope I did it the right way.
>
> First I  „insmod rtai_sched.ko kernel_latency=1000 user_latency=1000“.
>
> I get the usual ops:
>
> I-pipe: head domain RTAI registered.
>
> RTAI[hal]: mounted. ISOL_CPUS_MASK: 0.
>
> SYSINFO - # CPUs: 2, TIMER NAME: 'lapic', TIMER IRQ: 2305, TIMER FREQ: 
> 99748999, CLOCK NAME: 'tsc', CLOCK FREQ: 3191983000, CPU FREQ: 
> 3191983000, LINUX TIMER IRQ: 2305.
>
> RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
>
> , kstacks pool size = 524288 bytes.
>
> RTAI[sched]: hard timer type/freq = lapic/99748999(Hz); timing: 
> ONESHOT; linear timed lists.
>
> RTAI[sched]: Linux timer freq = 1000 (Hz), TimeBase freq = 3191983000 hz.
>
> RTAI[sched]: timer setup = 66 ns, resched latency = 0 ns.
>
> RTAI[usi]: enabled.
>
> BUG: unable to handle kernel paging request at bfd95d0c
>
> IP: [<f878403d>] rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched]
>
> *pde = c29cf067
>
>  Oops: 0001 [#1] PREEMPT SMP
>
>  Modules linked in: rtai_sched(O+) rtai_hal(O) i915 drm_kms_helper drm 
> i2c_algo_bit cfg80211 rfkill nfsd auth_rpcgss oid_registry nfs_acl nfs 
> lockd fscache sunrpc coretemp kvm crc32_pclmul snd_hda_codec_hdmi 
> aesni_intel aes_i586 snd_hda_codec_realtek snd_hda_codec_generic 
> snd_hda_intel snd_hda_controller snd_hda_codec snd_pcsp snd_hwdep 
> snd_pcm xts snd_timer snd lrw mxm_wmi evdev gf128mul ablk_helper 
> soundcore cryptd serio_raw video thermal_sys tpm_tis tpm wmi shpchp 
> button fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache 
> jbd2 hid_generic usbhid sg sd_mod crc_t10dif crct10dif_generic 
> crct10dif_common crc32c_intel 8139cp ahci libahci xhci_hcd libata 
> scsi_mod r8169 mii usbcore usb_common i2c_hid hid i2c_core
>
> CPU: 0 PID: 1291 Comm: calibrate Tainted: G           O  3.16-rtai #15
>
> Hardware name: System manufacturer System Product Name/H110M-C, BIOS 
> 3402 04/06/2017
>
> task: ee726090 ti: ee53c000 task.ti: ee53c000
>
> EIP: 0060:[<f878403d>] EFLAGS: 00010206 CPU: 0
>
> EIP is at rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched]
>
> EAX: 0040780c EBX: 00000000 ECX: 00000407 EDX: bfd95d0c
>
> ESI: bfd95d0c EDI: 0040780c EBP: ee53df84 ESP: ee53df34
>
> DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
>
> CR0: 8005003b CR2: bfd95d0c CR3: 2e54e000 CR4: 00340790
>
> I-pipe domain Linux
>
> Stack:
>
>   00000200 f77c8840 c1095c3d 00000000 c16be840 c15cabc0 ee53df98 00000001
>
>   fffffffe ee53df64 c1095d8c 00000000 ee53dfac c11456a8 ee53df98 ee4b7540
>
>   ee5f08c0 ee53dfb4 bfd95c68 b7586848 ee53dfa4 f8781fad 00000000 bfd96f48
>
> Call Trace:
>
>   [<c1095c3d>] ? __call_rcu.constprop.58+0xcd/0x200
>
>   [<c1095d8c>] ? call_rcu+0x1c/0x20
>
>   [<c11456a8>] ? SyS_access+0x188/0x1e0
>
>   [<f8781fad>] ? lxrt_intercept_syscall+0xad/0x1b0 [rtai_sched]
>
>   [<c10c65c4>] ? __ipipe_notify_syscall+0x14/0x30
>
> [<c1457296>] ? pipeline_sysenter+0x7/0x1e
>
> Code: 10 8b 56 0c 89 54 24 0c 8b 56 08 89 54 24 08 8b 56 04 89 54 24 
> 04 8b 16 89 14 24 ff 50 04 89 44 24 2c 89 54 24 30 e9 2f f6 ff ff <8b> 
> 1a 8d 81 18 fc ff ff 83 f8 20 89 da 0f 87 9b 05 00 00 ff 24
>
> EIP: [<f878403d>] rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched] SS:ESP 
> 0068:ee53df34
>
> CR2: 00000000bfd95d0c
>
> ---[ end trace 4e34e9dee96e2274 ]---
>
> USERMODE CHECK: ERROR.
>
> USERMODE CHECK PROVIDED (ns): KernelLatency 0, UserLatency 0.
>
> FINAL CALIBRATION SUMMARY (ns): KernelLatency 1001, UserLatency 1001.
>
> Then I downloaded the files from showroom and compiled it.
>
> Because the run doesn’t stop, I started them manually. First the 
> ./latency.
>
> I get an additional ops:
>
> BUG: unable to handle kernel paging request at bff6f468
>
> IP: [<f878403d>] rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched]
>
> *pde = c06ba067
>
>  Oops: 0001 [#2] PREEMPT SMP
>
>  Modules linked in: rtai_sched(O) rtai_hal(O) i915 drm_kms_helper drm 
> i2c_algo_bit cfg80211 rfkill nfsd auth_rpcgss oid_registry nfs_acl nfs 
> lockd fscache sunrpc coretemp kvm crc32_pclmul snd_hda_codec_hdmi 
> aesni_intel aes_i586 snd_hda_codec_realtek snd_hda_codec_generic 
> snd_hda_intel snd_hda_controller snd_hda_codec snd_pcsp snd_hwdep 
> snd_pcm xts snd_timer snd lrw mxm_wmi evdev gf128mul ablk_helper 
> soundcore cryptd serio_raw video thermal_sys tpm_tis tpm wmi shpchp 
> button fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache 
> jbd2 hid_generic usbhid sg sd_mod crc_t10dif crct10dif_generic 
> crct10dif_common crc32c_intel 8139cp ahci libahci xhci_hcd libata 
> scsi_mod r8169 mii usbcore usb_common i2c_hid hid i2c_core
>
> CPU: 0 PID: 1309 Comm: latency Tainted: G      D    O  3.16-rtai #15
>
> Hardware name: System manufacturer System Product Name/H110M-C, BIOS 
> 3402 04/06/2017
>
> task: ee5b9ab0 ti: f3cfa000 task.ti: f3cfa000
>
> EIP: 0060:[<f878403d>] EFLAGS: 00010206 CPU: 0
>
> EIP is at rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched]
>
> EAX: 00408804 EBX: 00000000 ECX: 00000408 EDX: bff6f468
>
> ESI: bff6f468 EDI: 00408804 EBP: f3cfbf84 ESP: f3cfbf34
>
> DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
>
> CR0: 8005003b CR2: bff6f468 CR3: 2e691000 CR4: 00340790
>
> I-pipe domain Linux
>
> Stack:
>
>   ee5b9ab0 f3cda238 000000a8 f3cda200 00000004 00000046 ee6faa84 f3cfbf5c
>
>   ee5b9ab0 ee5b9ec4 f3cfbf68 f3cfbf68 0000000e f3cfbfb4 3610a000 c102a31b
>
>   00000046 f3cfbfb4 bff6f3a8 36383669 f3cfbfa4 f8781fad 00000000 f3cfbfb4
>
> Call Trace:
>
>   [<c102a31b>] ? __ipipe_trap_prologue+0xeb/0x240
>
>   [<f8781fad>] ? lxrt_intercept_syscall+0xad/0x1b0 [rtai_sched]
>
>   [<c10c65c4>] ? __ipipe_notify_syscall+0x14/0x30
>
> [<c1457296>] ? pipeline_sysenter+0x7/0x1e
>
> Code: 10 8b 56 0c 89 54 24 0c 8b 56 08 89 54 24 08 8b 56 04 89 54 24 
> 04 8b 16 89 14 24 ff 50 04 89 44 24 2c 89 54 24 30 e9 2f f6 ff ff <8b> 
> 1a 8d 81 18 fc ff ff 83 f8 20 89 da 0f 87 9b 05 00 00 ff 24
>
> EIP: [<f878403d>] rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched] SS:ESP 
> 0068:f3cfbf34
>
> CR2: 00000000bff6f468
>
> ---[ end trace 4e34e9dee96e2275 ]---
>
> Then the ./display.
>
> I got the third ops:
>
> BUG: unable to handle kernel paging request at bfb4195c
>
> IP: [<f868f03d>] rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched]
>
> *pde = c2b65067
>
>  Oops: 0001 [#3] PREEMPT SMP
>
>  Modules linked in: rtai_sched(O) rtai_hal(O) i915 drm_kms_helper drm 
> i2c_algo_bit cfg80211 rfkill nfsd auth_rpcgss oid_registry nfs_acl nfs 
> lockd fscache sunrpc snd_hda_codec_hdmi coretemp kvm 
> snd_hda_codec_realtek snd_hda_codec_generic crc32_pclmul aesni_intel 
> snd_hda_intel aes_i586 snd_hda_controller tpm_tis xts tpm mxm_wmi 
> snd_hda_codec lrw snd_pcsp snd_hwdep evdev snd_pcm snd_timer snd 
> soundcore gf128mul ablk_helper cryptd serio_raw video thermal_sys 
> shpchp wmi button fuse parport_pc ppdev lp parport autofs4 ext4 crc16 
> mbcache jbd2 hid_generic usbhid sg sd_mod crc_t10dif crct10dif_generic 
> crct10dif_common r8169 crc32c_intel xhci_hcd 8139cp mii ahci libahci 
> libata scsi_mod usbcore usb_common i2c_hid hid i2c_core
>
> CPU: 1 PID: 1310 Comm: display Tainted: G      D    O  3.16-rtai #15
>
> Hardware name: System manufacturer System Product Name/H110M-C, BIOS 
> 3402 04/06/2017
>
> task: edda3540 ti: ede50000 task.ti: ede50000
>
> EIP: 0060:[<f868f03d>] EFLAGS: 00013202 CPU: 1
>
> EIP is at rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched]
>
> EAX: 003ea814 EBX: 00000000 ECX: 000003ea EDX: bfb4195c
>
> ESI: bfb4195c EDI: 003ea814 EBP: ede51f84 ESP: ede51f34
>
> DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
>
> CR0: 8005003b CR2: bfb4195c CR3: 2dfbc000 CR4: 00340790
>
> I-pipe domain Linux
>
> Stack:
>
>   bfb44000 00000000 00000053 00000022 bfb22000 ede51f70 c1128ae8 00000000
>
>   00000053 00000000 00000000 ede51f8c bfb44000 bfb22000 edd58630 ede51f9c
>
> c1129013 ede51fb4 bfb418c8 b75f6e18 ede51fa4 f868cfad 00000001 00000000
>
> Call Trace:
>
>   [<c1128ae8>] ? __mlock_vma_pages_range+0x68/0x80
>
>   [<c1129013>] ? __mm_populate+0xf3/0x110
>
>   [<f868cfad>] ? lxrt_intercept_syscall+0xad/0x1b0 [rtai_sched]
>
>   [<c10c65c4>] ? __ipipe_notify_syscall+0x14/0x30
>
> [<c1457296>] ? pipeline_sysenter+0x7/0x1e
>
> Code: 10 8b 56 0c 89 54 24 0c 8b 56 08 89 54 24 08 8b 56 04 89 54 24 
> 04 8b 16 89 14 24 ff 50 04 89 44 24 2c 89 54 24 30 e9 2f f6 ff ff <8b> 
> 1a 8d 81 18 fc ff ff 83 f8 20 89 da 0f 87 9b 05 00 00 ff 24
>
> EIP: [<f868f03d>] rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched] SS:ESP 
> 0068:ede51f34
>
> CR2: 00000000bfb4195c
>
> ---[ end trace c2f4c5949c09edef ]---
>
> About the 8 cores:
>
> A few years ago with rtai 3 I got a new cpu with 4 cores but my rtai 
> was configured only for 2 cores.
>
> Then I searched the usage of the CONFIG_RTAI_CPUS and found that it 
> only limits the maximum number of used cpus.
>
> The number of used cpus is calculated by num_online_cpus().
>
> I found no disadvantage to increase the number.
>
> On this new configuration I set it to 8 – It might be that I will 
> replace the 2 core cpu by a bigger one.
>
> I don’t think that this problem is caused by the 8 possible cores 
> because switching off SMP doesn’t help.
>
> Yet I booted this system with maxcpus=1. The ops still occurred.
>
> What do you think, shall I reconfigure my system with 2 cpus and try 
> it again?
>
> Thank you for your help,
>
> Josef
>
> *Von:*Paolo Mantegazza [mailto:[email protected]]
> *Gesendet:* Mittwoch, 10. Mai 2017 09:43
> *An:* PAUL-SOFTWARE
> *Betreff:* Re: [Rtai] sched: problem with paging request on linux 3.16
>
> I do not understand why some of my messages do not make their way to 
> the list. In any case that is my problem.
>
> That said your test did what I expected. RTAI own syscalls from user 
> space do not work, but since that happens in the user task it does not 
> affect the module insertion. There is now just one test more to carry 
> out, i.e. doing the same test, in the same way, in user space 
> (showroom/v3.x/user/latency) and see what happens, report to me please.
> The results in kernel space are OK, but indicates that in kernel space 
> the latency is around 500 ns, not 3000. Thus in user space you can use 
> "insmod ./rtai_sched.ko kernel_latency=1000 user_latency=1000".
>
> BTW I see that you have 8 cores, I never tested with more than 4. How 
> many cores has your CPU on which RTAI works?
>
> Paolo.
>
>
> On 05/10/2017 08:18 AM, PAUL-SOFTWARE wrote:
>
>     Hello Paolo,
>
>     I patched sched.c and insmoded rtai_sched.ko with the parameters.
>
>     The ops now is different:
>
>     I-pipe: head domain RTAI registered.
>
>       RTAI[hal]: mounted. ISOL_CPUS_MASK: 0.
>
>       SYSINFO - # CPUs: 2, TIMER NAME: 'lapic', TIMER IRQ: 2305, TIMER FREQ: 99748999, CLOCK NAME: 'tsc', CLOCK FREQ: 3191981000, CPU FREQ: 3191981000, LINUX TIMER IRQ: 2305.
>
>       RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
>
>       , kstacks pool size = 524288 bytes.
>
>       RTAI[sched]: hard timer type/freq = lapic/99748999(Hz); timing: ONESHOT; linear timed lists.
>
>       RTAI[sched]: Linux timer freq = 1000 (Hz), TimeBase freq = 3191981000 hz.
>
>       RTAI[sched]: timer setup = 66 ns, resched latency = 0 ns.
>
>       RTAI[usi]: enabled.
>
>       BUG: unable to handle kernel paging request at bf86091c
>
>       IP: [<f878603d>] rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched]
>
>       *pde = c2a4b067
>
>       Oops: 0001 [#1] PREEMPT SMP
>
>       Modules linked in: rtai_sched(O+) rtai_hal(O) i915 drm_kms_helper drm i2c_algo_bit cfg80211 rfkill nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec coretemp snd_hwdep snd_pcsp kvm crc32_pclmul aesni_intel snd_pcm snd_timer snd aes_i586 xts lrw gf128mul ablk_helper cryptd soundcore mxm_wmi evdev serio_raw shpchp video thermal_sys tpm_tis tpm wmi button fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid sg sd_mod crc_t10dif crct10dif_generic crct10dif_common crc32c_intel r8169 8139cp mii xhci_hcd ahci libahci libata scsi_mod usbcore usb_common i2c_hid hid i2c_core
>
>       CPU: 1 PID: 1291 Comm: calibrate Tainted: G           O  3.16-rtai #15
>
>       Hardware name: System manufacturer System Product Name/H110M-C, BIOS 3402 04/06/2017
>
>       task: ea49b5c0 ti: f1a20000 task.ti: f1a20000
>
>       EIP: 0060:[<f878603d>] EFLAGS: 00010206 CPU: 1
>
>       EIP is at rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched]
>
>       EAX: 0040780c EBX: 00000000 ECX: 00000407 EDX: bf86091c
>
>       ESI: bf86091c EDI: 0040780c EBP: f1a21f84 ESP: f1a21f34
>
>        DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
>
>       CR0: 8005003b CR2: bf86091c CR3: 33e85000 CR4: 00340790
>
>       I-pipe domain Linux
>
>       Stack:
>
>        00000200 f77db840 c1095c3d 00000000 c16be840 c15cabc0 f1a21f98 00000001
>
>        fffffffe f1a21f64 c1095d8c 00000000 f1a21fac c11456a8 f1a21f98 eecf84c0
>
>        f3c27140 f1a21fb4 bf860878 b7583848 f1a21fa4 f8783fad 00000000 bf861f48
>
>       Call Trace:
>
>        [<c1095c3d>] ? __call_rcu.constprop.58+0xcd/0x200
>
>        [<c1095d8c>] ? call_rcu+0x1c/0x20
>
>        [<c11456a8>] ? SyS_access+0x188/0x1e0
>
>        [<f8783fad>] ? lxrt_intercept_syscall+0xad/0x1b0 [rtai_sched]
>
>        [<c10c65c4>] ? __ipipe_notify_syscall+0x14/0x30
>
>        [<c1457296>] ? pipeline_sysenter+0x7/0x1e
>
>       Code: 10 8b 56 0c 89 54 24 0c 8b 56 08 89 54 24 08 8b 56 04 89 54 24 04 8b 16 89 14 24 ff 50 04 89 44 24 2c 89 54 24 30 e9 2f f6 ff ff <8b> 1a 8d 81 18 fc ff ff 83 f8 20 89 da 0f 87 9b 05 00 00 ff 24
>
>       EIP: [<f878603d>] rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched] SS:ESP 0068:f1a21f34
>
>       CR2: 00000000bf86091c
>
>       ---[ end trace 019e450374b8e6f2 ]---
>
>       USERMODE CHECK: ERROR.
>
>       USERMODE CHECK PROVIDED (ns): KernelLatency 0, UserLatency 0.
>
>       FINAL CALIBRATION SUMMARY (ns): KernelLatency 3001, UserLatency 3001.
>
>     Then I run the testsuite/kernel/latency:
>
>     CPU USE SUMMARY
>
>       # 0 -> 1075944
>
>       # 1 -> 0
>
>       # 2 -> 0
>
>       # 3 -> 0
>
>       # 4 -> 0
>
>       # 5 -> 0
>
>       # 6 -> 0
>
>       # 7 -> 0
>
>       END OF CPU USE SUMMARY
>
>     Attached you find the output of the latency-run command.
>
>     Thank you,
>
>     Josef
>
>     -----Ursprüngliche Nachricht-----
>
>     Von: Paolo Mantegazza [mailto:[email protected]]
>
>     Gesendet: Dienstag, 9. Mai 2017 19:08
>
>     An: PAUL-SOFTWARE;[email protected] <mailto:[email protected]>
>
>     Betreff: RE: [Rtai] sched: problem with paging request on linux 3.16
>
>     Sorry, I wanted to say:
>
>     What you can still do is to comment out of sched.c the lines 2479 and 2480. With such a patch you should run the kernel latency test in SHOWROOM CVS, see what happens and report.
>
>     Paolo.
>
>     ________________________________________
>
>     From: Rtai [[email protected] <mailto:[email protected]>] on behalf of Paolo Mantegazza [[email protected] <mailto:[email protected]>]
>
>     Sent: Tuesday, May 9, 2017 7:00 PM
>
>     To: PAUL-SOFTWARE;[email protected] <mailto:[email protected]>
>
>     Subject: Re: [Rtai] sched: problem with paging request on linux 3.16
>
>     [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing athttp://aka.ms/LearnAboutSpoofing]
>
>     insmod ./rtai_sched.ko kernel_latency=3000 user_latency=3000, is the right way.
>
>     Nonetheless I would have wished you got on it before releasing 5.0. I should not have missed a trivial commit I forgot.
>
>     It should be OK in VULCANO CVS now.
>
>     I have it clear that your trouble comes from the very first execution of whatever you'll run in user space. A thing I can reproduce if I keep the syscall auditing option in the kernel and have the related deamon installed.
>
>     Yesterday night I tried for a cause the problem with no syscall auditing  for a couple of hours without success.
>
>     With what I  asked you I wanted just to be sure and know either  if the trouble comes when the existence of the calibration files is checked or when the actual calibration is carried out.
>
>     What you can still do is to comment out  use the insmod above and comment out of sched.c the lines 2479 and 2480, suing the above isnmod.
>
>     With such a patch you should run the latency test in showroom, see what happens and report.
>
>     Paolo
>
>     ________________________________________
>
>     From: Rtai [[email protected] <mailto:[email protected]>] on behalf of PAUL-SOFTWARE [[email protected] <mailto:[email protected]>]
>
>     Sent: Tuesday, May 9, 2017 5:41 PM
>
>     To:[email protected] <mailto:[email protected]>
>
>     Subject: Re: [Rtai] sched: problem with paging request on linux 3.16
>
>     Hello Paolo,
>
>     I use the new RTAI 5.0.
>
>     When I do
>
>     insmod ./rtai_sched.ko kernel_latency=3000 user_latency=3000 the parameters aren't known:
>
>     rtai_sched: unknown parameter 'kernel_latency' ignored
>
>     rtai_sched: unknown parameter 'user_latency' ignored And this doesn't help. Calibration is still done.
>
>     Then I tried
>
>     insmod ./rtai_sched.ko KernelLatency=3000 UserLatency=3000
>
>     This parameter are known but the calibration is still done and there is still the kernel ops:
>
>     RTAI[hal]: mounted. ISOL_CPUS_MASK: 0.
>
>     SYSINFO - # CPUs: 2, TIMER NAME: 'lapic', TIMER IRQ: 2305, TIMER FREQ: 99750000, CLOCK NAME: 'tsc', CLOCK FREQ: 3192012000, CPU FREQ: 3192012000, LINUX TIMER IRQ: 2305.
>
>     RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
>
>     , kstacks pool size = 524288 bytes.
>
>     RTAI[sched]: hard timer type/freq = lapic/99750000(Hz); timing: ONESHOT; linear timed lists.
>
>     RTAI[sched]: Linux timer freq = 1000 (Hz), TimeBase freq = 3192012000 hz.
>
>     RTAI[sched]: timer setup = 66 ns, resched latency = 0 ns.
>
>     RTAI[usi]: enabled.
>
>     BUG: unable to handle kernel paging request at bf97c36c
>
>     IP: [<f8795fed>] rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched] *pde = c2b0d067
>
>       Oops: 0001 [#1] PREEMPT SMP
>
>       Modules linked in: rtai_sched(O+) rtai_hal(O) i915 drm_kms_helper drm i2c_algo_bit cfg80211 rfkill nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc snd_hda_codec_hdmi mxm_wmi video thermal_sys snd_hda_codec_realtek snd_hda_codec_generic coretemp serio_raw kvm evdev crc32_pclmul aesni_intel aes_i586 xts lrw gf128mul ablk_helper cryptd tpm_tis tpm shpchp snd_hda_intel snd_hda_controller snd_pcsp snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore button wmi fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid sg sd_mod crc_t10dif crct10dif_generic crct10dif_common crc32c_intel ahci libahci r8169 8139cp mii libata scsi_mod xhci_hcd usbcore usb_common i2c_hid hid i2c_core
>
>     CPU: 1 PID: 1293 Comm: calibrate Tainted: G           O  3.16-rtai #15
>
>     Hardware name: System manufacturer System Product Name/H110M-C, BIOS 3402 04/06/2017
>
>     task: f3c12a70 ti: f3d00000 task.ti: f3d00000
>
>     EIP: 0060:[<f8795fed>] EFLAGS: 00010206 CPU: 1 EIP is at rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched]
>
>     EAX: 0040780c EBX: 00000000 ECX: 00000407 EDX: bf97c36c
>
>     ESI: bf97c36c EDI: 0040780c EBP: f3d01f84 ESP: f3d01f34
>
>        DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
>
>     CR0: 8005003b CR2: bf97c36c CR3: 2dd4b000 CR4: 00340790 I-pipe domain Linux
>
>     Stack:
>
>        00000200 f77db840 c1095c3d 00000000 c16be840 c15cabc0 f3d01f98 00000001
>
>        fffffffe f3d01f64 c1095d8c 00000000 f3d01fac c11456a8 f3d01f98 f1f5b3c0
>
>        f6ea9240 f3d01fb4 bf97c2c8 b750e848 f3d01fa4 f8793f5d 00000000 bf97df48 Call Trace:
>
>        [<c1095c3d>] ? __call_rcu.constprop.58+0xcd/0x200
>
>        [<c1095d8c>] ? call_rcu+0x1c/0x20
>
>        [<c11456a8>] ? SyS_access+0x188/0x1e0
>
>        [<f8793f5d>] ? lxrt_intercept_syscall+0xad/0x1b0 [rtai_sched]
>
>        [<c10c65c4>] ? __ipipe_notify_syscall+0x14/0x30
>
>        [<c1457296>] ? pipeline_sysenter+0x7/0x1e
>
>     Code: 10 8b 56 0c 89 54 24 0c 8b 56 08 89 54 24 08 8b 56 04 89 54 24 04 8b 16 89 14 24 ff 50 04 89 44 24 2c 89 54 24 30 e9 2f f6 ff ff <8b> 1a 8d 81 18 fc ff ff 83 f8 20 89 da 0f 87 9b 05 00 00 ff 24
>
>     EIP: [<f8795fed>] rtai_lxrt_invoke+0xaed/0x13d0 [rtai_sched] SS:ESP 0068:f3d01f34
>
>     CR2: 00000000bf97c36c
>
>     ---[ end trace 4070b2700c0c5ca7 ]---
>
>     USERMODE CHECK: ERROR.
>
>     USERMODE CHECK PROVIDED (ns): KernelLatency 940, UserLatency 940.
>
>     FINAL CALIBRATION SUMMARY (ns): KernelLatency 940, UserLatency 940.
>
>     For testing I switched off SMP at all. Same results.
>
>     I have an Intel i3-6100T processor with 2 cores. Hyperthreading is disabled in the BIOS.
>
>     This is cat /proc/interrupts
>
>                 CPU0       CPU1
>
>        0:         60          0   IO-APIC-edge      timer
>
>        1:        269          0   IO-APIC-edge      i8042
>
>        5:          0          0   IO-APIC-edge      parport0
>
>        8:          1          0   IO-APIC-edge      rtc0
>
>        9:          0          0   IO-APIC-fasteoi   acpi
>
>     136:        146          0   PCI-MSI-edge      xhci_hcd
>
>     137:        878          0   PCI-MSI-edge      eth2
>
>     138:      14209          0   PCI-MSI-edge      ahci
>
>     139:        427          0   PCI-MSI-edge      snd_hda_intel
>
>     NMI:          0          0   Non-maskable interrupts
>
>     LOC:      18609     112842   Local timer interrupts
>
>     SPU:          0          0   Spurious interrupts
>
>     PMI:          0          0   Performance monitoring interrupts
>
>     IWI:          0          0   IRQ work interrupts
>
>     RTR:          0          0   APIC ICR read retries
>
>     RES:       6648       6905   Rescheduling interrupts
>
>     CAL:        360       6161   Function call interrupts
>
>     TLB:        245        380   TLB shootdowns
>
>     ERR:          0
>
>     MIS:          0
>
>     Josef
>
>     Von: Paolo Mantegazza [mailto:[email protected]]
>
>     Gesendet: Montag, 8. Mai 2017 17:31
>
>     An: PAUL-SOFTWARE;[email protected] <mailto:[email protected]>
>
>     Betreff: Re: [Rtai] sched: problem with paging request on linux 3.16
>
>     You could also try the test by inserting the needed modules manually, using "insmod ???/rtai_sched.ko kernel_latency= 3000 user_latency=3000", so to avoid the calibration.
>
>     Paolo
>
>     On 05/08/2017 12:59 PM, PAUL-SOFTWARE wrote:
>
>     Hello Paolo,
>
>     Using the calibration data from the running system doesn't help.
>
>     I have tried RTAI from CVS and the new released RTAI 5.0 without success.
>
>     Even when I use the same kernel settings you have posted a few days ago, the kernel ops with the second hardware still exists.
>
>     The hal patch I use is identically to the one that was in VULCANO CVS.
>
>     But the patch was removed. Do you know why?
>
>     Unfortunately I can't use a newer kernel: The Igh Ethercat Master has only patched diver for network interfaces up to kernel 3.16.
>
>     Josef
>
>     Von: Paolo Mantegazza [mailto:[email protected]]
>
>     Gesendet: Mittwoch, 3. Mai 2017 14:57
>
>     An: PAUL-SOFTWARE;[email protected] <mailto:[email protected]><mailto:[email protected]>
>     <mailto:[email protected]>
>
>     Betreff: Re: [Rtai] sched: problem with paging request on linux 3.16
>
>     Have you configured your kernel for a UP setup?
>
>     The latency calibration failed. you can try copying the file RTAIINSTALLDIR/calibration/latencies that succeeded in the new installation and see what happens.
>
>     Moreover, I do not think that the patch you use is distributed with the test version you are using. Try with one in test2 tarball.
>
>     All in all we are about to release the final 5.0, which is what is in VULCANO CVS. TRy it too.
>
>     Paolo.
>
>     On 05/03/2017 01:53 PM, PAUL-SOFTWARE wrote:
>
>     Hello,
>
>     I installed rtai-5.0-test2 on Debian Jessie with 32Bit kernel 3.16.7, using the hal-patch from magma (hal-linux-3.16.7-x86-5x.patch<https://github.com/ShabbyX/RTAI/blob/master/base/arch/x86/patches/hal-linux-3.16.7-x86-5x.patch>
>     <https://github.com/ShabbyX/RTAI/blob/master/base/arch/x86/patches/hal-linux-3.16.7-x86-5x.patch>).
>
>     Everything works fine on a board with Intel i3-4130 CPU.
>
>     On a system with Intel i3-6110 CPU I get an error when I insert rtai_sched.ko.
>
>     This is the kernel log when I start testsuite/kernel/latency:
>
>     I-pipe: head domain RTAI registered.
>
>     RTAI[hal]: mounted. ISOL_CPUS_MASK: 0.
>
>     SYSINFO - # CPUs: 1, TIMER NAME: 'lapic', TIMER IRQ: 2305, TIMER FREQ: 99758000, CLOCK NAME: 'tsc', CLOCK FREQ: 3192285000, CPU FREQ: 3192285000, LINUX TIMER IRQ: 2305.
>
>     RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
>
>     , kstacks pool size = 524288 bytes.
>
>     RTAI[sched]: hard timer type/freq = lapic/99758000(Hz); timing: oneshot; linear timed lists.
>
>     RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 3192285000 hz..
>
>     RTAI[sched]: timer setup = 64 ns, resched latency = 0 ns.
>
>     RTAI[usi]: enabled.
>
>     BUG: unable to handle kernel paging request at bfebea1c
>
>     IP: [<f86e2845>] rtai_lxrt_invoke+0xae5/0x13c0 [rtai_sched] *pde = 108de067 *pte = 10c15067
>
>     Oops: 0001 [#1] PREEMPT
>
>     Modules linked in: rtai_sched(O+) rtai_hal(O) i915 drm_kms_helper drm i2c_algo_bit cfg80211 rfkill nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc snd_hda_codec_hdmi coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm snd_hda_intel snd_hda_controller snd_hda_codec crc32_pclmul snd_hwdep aesni_intel snd_pcsp aes_i586 xts snd_pcm snd_timer lrw gf128mul snd soundcore ablk_helper cryptd mxm_wmi battery evdev serio_raw tpm_tis tpm shpchp wmi video button fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid sg sd_mod crc_t10dif crct10dif_generic crct10dif_common crc32c_intel ahci libahci xhci_hcd r8169 8139cp mii libata scsi_mod usbcore usb_common fan thermal_sys i2c_hid hid i2c_core
>
>     CPU: 0 PID: 1346 Comm: calibrate Tainted: G           O  3.16-rtai #8
>
>     Hardware name: System manufacturer System Product Name/H110M-C, BIOS 3402 04/06/2017
>
>     task: d08dc010 ti: d08f8000 task.ti: d08f8000
>
>     EIP: 0060:[<f86e2845>] EFLAGS: 00010206 CPU: 0 EIP is at rtai_lxrt_invoke+0xae5/0x13c0 [rtai_sched]
>
>     EAX: 0040780c EBX: 00000000 ECX: 00000407 EDX: bfebea1c
>
>     ESI: bfebea1c EDI: 0040780c EBP: d08f9f84 ESP: d08f9f34
>
>     DS: 007b ES: 007b FS: 0000 GS: 00e0 SS: 0068
>
>     CR0: 8005003b CR2: bfebea1c CR3: 108dd000 CR4: 00340790 I-pipe domain Linux
>
>     Stack:
>
>     d08f9f58 c10863ee c15e4180 c1087745 d08f9f98 c15e4240 d08f9f98 00000001 fffffffe d08f9f64 c108789c 00000000 d08f9fac c1145b90 d08f9f98 ed94bc40
>
>     e19b3ac0 d08f9fb4 bfebe978 b74f6848 d08f9fa4 f86e09dd 00000000 bfebff48 Call Trace:
>
>     [<c10863ee>] ? rcu_is_watching+0x1e/0x40 [<c1087745>] ? __call_rcu.constprop.60+0xa5/0x1e0
>
>     [<c108789c>] ? call_rcu+0x1c/0x20
>
>     [<c1145b90>] ? SyS_access+0x190/0x1f0
>
>     [<f86e09dd>] ? lxrt_intercept_syscall+0x8d/0x190 [rtai_sched] [<c10bdcd4>] ? __ipipe_notify_syscall+0x14/0x30 [<c1468115>] ? pipeline_sysenter+0x7/0x1e
>
>     Code: 10 8b 56 0c 89 54 24 0c 8b 56 08 89 54 24 08 8b 56 04 89 54 24 04 8b 16 89 14 24 ff 50 04 89 44 24 2c 89 54 24 30 e9 37 f6 ff ff <8b> 1a 8d 81 18 fc ff ff 83 f8 20 89 da 0f 87 97 05 00 00 ff 24
>
>     EIP: [<f86e2845>] rtai_lxrt_invoke+0xae5/0x13c0 [rtai_sched] SS:ESP 0068:d08f9f34
>
>     CR2: 00000000bfebea1c
>
>     ---[ end trace 426b8ee3f3f6e396 ]---
>
>     USERMODE CHECK: ERROR.
>
>     USERMODE CHECK PROVIDED (ns): KernelLatency 0, UserLatency 0.
>
>     FINAL CALIBRATION SUMMARY (ns): KernelLatency 1, UserLatency 1.
>
>     Has anybody an idea what causes this ops and how I can avoid it?
>
>     Best regards,
>
>     Josef
>
>     _______________________________________________
>
>     Rtai mailing list
>
>     [email protected] <mailto:[email protected]><mailto:[email protected]>
>     <mailto:[email protected]>
>
>     https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
>
>     _______________________________________________
>
>     Rtai mailing list
>
>     [email protected] <mailto:[email protected]><mailto:[email protected]>
>     <mailto:[email protected]>
>
>     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] <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

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