Re: RTAI-5 make hangs at self-calibrate.
Paolo Mantegazza <[email protected]>
| Newsgroups | gmane.linux.real-time.rtai |
|---|---|
| Message-ID | <[email protected]> |
On 04/26/2016 05:07 PM, Duane AW. Jeffery wrote: > Modified my kernel config to match the differences you posted below and recompiled, recompiled RTAI against the new kernel, and found the same results. > > Also tried with and without lapic=notscdeadline boot option. > > No change. Still works with /usr/realtime/testsuite/kern/latency/run, does not work with /usr/realtime/testsuite/user/latency/run. Hangs at the same location (line 1935 of base/sched/sched.c, where it tries to go hard real-time by calling: __ipipe_migrate_head();). That call never returns until I Control-C. > > But of course, it helps if I read. Back in January, this thread started by Emmanuel Pacaud: http://mail.rtai.org/pipermail/rtai/2016-January/027047.html speaks of userspace testsuite issues identical to mine, caused by the IPIPE_LEGACY switch being on. I had set it (our RTAI-based software has been around since the early days of RTAI, wasn't sure if I needed it, so I switched it on). > > So I tried setting CONFIG_IPIPE_LEGACY=n (in make menuconfig for linux kernel) which seems to automatically set CONFIG_IPIPE_TARGET_APIREV=2. Recompiled kernel, reboot, recompiled RTAI against my new kernel, and tried again. Well I would have never dreamt of that. In fact I'm wondering how CONFIG_IPIPE_LEGACY could be set if a user does not force it to yes, as the patch explicitly sets it to no. So just a user that knows the patch internals better than I should do that. That's why I assume that when RTAI fails badly that way is just though an improper kernel configuration. I'll se what we can do in RTAI making. Paolo. > Lo and behold, RTAI userspace latency test works! Removed my /usr/realtime/calibration/latencies file and on next insmod, rtai_sched properly completed its calibration! > > Perhaps RTAI-5's configure should fail with an instructive message if /usr/src/linux/.config (or /proc/config.gz) contains CONFIG_IPIPE_LEGACY=y or CONFIG_IPIPE_TARGET_APIREV=1? > > Now on to solve my next problem; rtai_math.ko fails to insert with some unknown symbols. > > -Duane > > -----Original Message----- > From: Francescodario Cuzzocrea [mailto:[email protected]] On Behalf Of Francescodario Cuzzocrea > Sent: Tuesday, April 26, 2016 3:06 AM > To: Duane AW. Jeffery <[email protected]> > Subject: Re: [Rtai] RTAI-5 make hangs at self-calibrate. > > Thank you, I'm watching differences between yout Kconfig and mine. > Could you please do a try modifying the settings of these subsystem as above ? > Remember also to boot with lapic=notscdeadline boot options (just modify /etc/ default/grub and add lapic=notscdeadline to GRUB_CMDLINE_LINUX and run sudo > update-grub) > > # > # CPU/Task time and stats accounting > # > CONFIG_TICK_CPU_ACCOUNTING=y > # CONFIG_IRQ_TIME_ACCOUNTING is not set > # CONFIG_BSD_PROCESS_ACCT is not set > # CONFIG_TASKSTATS is not set > > # RCU Subsystem > # > CONFIG_PREEMPT_RCU=y > CONFIG_SRCU=y > # CONFIG_TASKS_RCU is not set > CONFIG_RCU_STALL_COMMON=y > CONFIG_RCU_FANOUT=64 > CONFIG_RCU_FANOUT_LEAF=16 > # CONFIG_RCU_FANOUT_EXACT is not set > # CONFIG_RCU_FAST_NO_HZ is not set > # CONFIG_TREE_RCU_TRACE is not set > # CONFIG_RCU_BOOST is not set > CONFIG_RCU_KTHREAD_PRIO=0 > # CONFIG_RCU_NOCB_CPU is not set > # CONFIG_RCU_EXPEDITE_BOOT is not set > CONFIG_BUILD_BIN2C=y > CONFIG_IKCONFIG=y > CONFIG_IKCONFIG_PROC=y > CONFIG_LOG_BUF_SHIFT=18 > CONFIG_LOG_CPU_MAX_BUF_SHIFT=12 > CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y > CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y > CONFIG_ARCH_SUPPORTS_INT128=y > CONFIG_CGROUPS=y > # CONFIG_CGROUP_DEBUG is not set > CONFIG_CGROUP_FREEZER=y > CONFIG_CGROUP_DEVICE=y > CONFIG_CPUSETS=y > CONFIG_PROC_PID_CPUSET=y > CONFIG_CGROUP_CPUACCT=y > # CONFIG_MEMCG is not set > # CONFIG_CGROUP_HUGETLB is not set > # CONFIG_CGROUP_PERF is not set > CONFIG_CGROUP_SCHED=y > CONFIG_FAIR_GROUP_SCHED=y > CONFIG_CFS_BANDWIDTH=y > # CONFIG_RT_GROUP_SCHED is not set > CONFIG_BLK_CGROUP=y > # CONFIG_DEBUG_BLK_CGROUP is not set > # CONFIG_CHECKPOINT_RESTORE is not set > CONFIG_NAMESPACES=y > CONFIG_UTS_NS=y > CONFIG_IPC_NS=y > # CONFIG_USER_NS is not set > CONFIG_PID_NS=y > CONFIG_NET_NS=y > # CONFIG_SCHED_AUTOGROUP is not set > # CONFIG_SYSFS_DEPRECATED is not set > CONFIG_RELAY=y > CONFIG_BLK_DEV_INITRD=y > CONFIG_INITRAMFS_SOURCE="" > CONFIG_RD_GZIP=y > CONFIG_RD_BZIP2=y > CONFIG_RD_LZMA=y > CONFIG_RD_XZ=y > CONFIG_RD_LZO=y > CONFIG_RD_LZ4=y > # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_SYSCTL_EXCEPTION_TRACE=y CONFIG_HAVE_PCSPKR_PLATFORM=y CONFIG_BPF=y # CONFIG_EXPERT is not set CONFIG_MULTIUSER=y CONFIG_SGETMASK_SYSCALL=y CONFIG_SYSFS_SYSCALL=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set CONFIG_PRINTK=y # CONFIG_RAW_PRINTK is not set CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y # CONFIG_BPF_SYSCALL is not set CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_ADVISE_SYSCALLS=y CONFIG_PCI_QUIRKS=y # CONFIG_EMBEDDED is not set CONFIG_HAVE_PERF_EVENTS=y > > > # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y # CONFIG_DEBUG_PERF_USE_VMALLOC is not set CONFIG_VM_EVENT_COUNTERS=y # CONFIG_COMPAT_BRK is not set CONFIG_SLAB=y # CONFIG_SLUB is not set CONFIG_SYSTEM_TRUSTED_KEYRING=y # CONFIG_PROFILING is not set CONFIG_HAVE_OPROFILE=y CONFIG_OPROFILE_NMI_TIMER=y # CONFIG_KPROBES is not set # CONFIG_JUMP_LABEL is not set # CONFIG_UPROBES is not set # CONFIG_HAVE_64BIT_ALIGNED_ACCESS is not set CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y > CONFIG_ARCH_USE_BUILTIN_BSWAP=y > CONFIG_HAVE_IOREMAP_PROT=y > CONFIG_HAVE_KPROBES=y > CONFIG_HAVE_KRETPROBES=y > CONFIG_HAVE_OPTPROBES=y > CONFIG_HAVE_KPROBES_ON_FTRACE=y > CONFIG_HAVE_ARCH_TRACEHOOK=y > CONFIG_HAVE_DMA_ATTRS=y > CONFIG_HAVE_DMA_CONTIGUOUS=y > CONFIG_GENERIC_SMP_IDLE_THREAD=y > CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y > CONFIG_HAVE_DMA_API_DEBUG=y > CONFIG_HAVE_HW_BREAKPOINT=y > CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y > CONFIG_HAVE_USER_RETURN_NOTIFIER=y > CONFIG_HAVE_PERF_EVENTS_NMI=y > CONFIG_HAVE_PERF_REGS=y > CONFIG_HAVE_PERF_USER_STACK_DUMP=y > CONFIG_HAVE_ARCH_JUMP_LABEL=y > CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y > CONFIG_HAVE_CMPXCHG_LOCAL=y > CONFIG_HAVE_CMPXCHG_DOUBLE=y > CONFIG_HAVE_ARCH_SECCOMP_FILTER=y > CONFIG_SECCOMP_FILTER=y > CONFIG_HAVE_CC_STACKPROTECTOR=y > # CONFIG_CC_STACKPROTECTOR is not set > CONFIG_CC_STACKPROTECTOR_NONE=y > # CONFIG_CC_STACKPROTECTOR_REGULAR is not set # CONFIG_CC_STACKPROTECTOR_STRONG is not set CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y > CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y > CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y > CONFIG_HAVE_ARCH_HUGE_VMAP=y > CONFIG_HAVE_ARCH_SOFT_DIRTY=y > CONFIG_MODULES_USE_ELF_RELA=y > CONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK=y > CONFIG_ARCH_HAS_ELF_RANDOMIZE=y > > # > # Power management and ACPI options > # > # CONFIG_SUSPEND is not set > # CONFIG_HIBERNATION is not set > CONFIG_PM=y > # CONFIG_PM_DEBUG is not set > # CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set CONFIG_ACPI=y CONFIG_ACPI_LEGACY_TABLES_LOOKUP=y > CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=y > CONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=y > # CONFIG_ACPI_PROCFS_POWER is not set > # CONFIG_ACPI_EC_DEBUGFS is not set > CONFIG_ACPI_AC=y > CONFIG_ACPI_BATTERY=y > CONFIG_ACPI_BUTTON=y > CONFIG_ACPI_VIDEO=y > CONFIG_ACPI_FAN=y > # CONFIG_ACPI_DOCK is not set > # CONFIG_ACPI_PROCESSOR is not set > # CONFIG_ACPI_IPMI is not set > # CONFIG_ACPI_CUSTOM_DSDT is not set > # CONFIG_ACPI_INITRD_TABLE_OVERRIDE is not set # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_PCI_SLOT=y CONFIG_X86_PM_TIMER=y # CONFIG_ACPI_CONTAINER is not set CONFIG_ACPI_HOTPLUG_IOAPIC=y # CONFIG_ACPI_SBS is not set CONFIG_ACPI_HED=y # CONFIG_ACPI_CUSTOM_METHOD is not set # CONFIG_ACPI_BGRT is not set # CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not set CONFIG_HAVE_ACPI_APEI=y CONFIG_HAVE_ACPI_APEI_NMI=y # CONFIG_ACPI_APEI is not set # CONFIG_PMIC_OPREGION is not set # CONFIG_SFI is not set > > # > # GCOV-based kernel profiling > # > # CONFIG_GCOV_KERNEL is not set > CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y > # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y > CONFIG_BASE_SMALL=0 > CONFIG_MODULES=y > CONFIG_MODULE_FORCE_LOAD=y > CONFIG_MODULE_UNLOAD=y > CONFIG_MODULE_FORCE_UNLOAD=y > # CONFIG_MODVERSIONS is not set > # CONFIG_MODULE_SRCVERSION_ALL is not set # CONFIG_MODULE_SIG is not set # CONFIG_MODULE_COMPRESS is not set CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y CONFIG_BLK_DEV_BSG=y CONFIG_BLK_DEV_BSGLIB=y CONFIG_BLK_DEV_INTEGRITY=y CONFIG_BLK_DEV_THROTTLING=y # CONFIG_BLK_CMDLINE_PARSER is not set > > > > In data lunedì 25 aprile 2016 20:24:34 CEST, hai scritto: >> Sorry, I missed this request for my Kernel Config last week. Please >> find it attached. > >> -Duane >> >> From: Rtai [mailto:[email protected]] On Behalf Of Francescodario >> Cuzzocrea > Sent: Tuesday, April 19, 2016 8:34 AM >> To: [email protected] >> Subject: Re: [Rtai] Rtai Digest, Vol 100, Issue 22 >> >> Il giorno mar 19 apr 2016 alle ore 09:19 >> <[email protected]<mailto:[email protected]>> ha scritto: > Send >> Rtai mailing list submissions to >> [email protected]<mailto:[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]<mailto:[email protected]> >> >> You can reach the person managing the list at >> [email protected]<mailto:[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: RTAI-5 make hangs at self-calibrate. (Duane AW. Jeffery) >> 2. Re: RTAI-5 make hangs at self-calibrate. (Paolo Mantegazza) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 18 Apr 2016 19:57:50 +0000 >> From: "Duane AW. Jeffery" >> <[email protected]<mailto:[email protected]>> > To: >> Paolo Mantegazza >> <[email protected]<mailto:[email protected]>>, Felix >> Frey <[email protected]<mailto:[email protected]>>, >> "[email protected]<mailto:[email protected]>" >> <[email protected]<mailto:[email protected]>> >> Subject: Re: [Rtai] RTAI-5 make hangs at self-calibrate. >> Message-ID: >> >> <SN1PR0701MB182171558F09D6BD551440E3BD6B0@SN1PR0701MB1821.namprd07.pro >> d.out >> look.com<mailto:SN1PR0701MB182171558F09D6BD551440E3BD6B0@SN1PR0701MB18 >> 21.nam >> prd07.prod.outlook.com>> > >> Content-Type: text/plain; charset="us-ascii" >> >> I tried it on 4.1.18, no change. Still works in kernel mode, does not >> work in userspace mode. > >> Dmesg does not seem to have any instructive messages either, I don't think. >> Just looks like things loading up and then unloading when I control-C it. > >> For what its worth, each time I've Control-C'd the userspace one, I >> get the same numbers (79, 79, 24641422, 4195964, 4195964, 0) on that >> line. Perhaps they might lead to an answer? > >> -Duane >> Hi Duane, can you please attach your 4.1.18 kernel config ? >> >> -----Original Message----- >> From: Paolo Mantegazza >> [mailto:[email protected]<mailto:[email protected]>] >> Sent: Monday, April 18, 2016 11:55 AM >> To: Duane AW. Jeffery >> <[email protected]<mailto:[email protected]>>; >> Felix Frey <[email protected]<mailto:[email protected]>>; >> [email protected]<mailto:[email protected]> > Subject: Re: [Rtai] RTAI-5 make hangs >> at self-calibrate. >> >> On 04/18/2016 05:33 PM, Duane AW. Jeffery wrote: >> >>> I set /usr/realtime/calibration/latencies to be a text file >>> containing >>> "1201 1700 100000<linefeed>". >>> >>> I tried running /usr/realtime/testsuite/kern/latency/run and got a >>> typical latency report showing ovlmax around 2500ns. In other words >>> -- kernel space seems to be working, not really surprising since we >>> saw that in the attempted calibration. >>> >>> Tried running /usr/realtime/testsuite/user/latency/run and get what >>> appears to start, and then hangs after printing the header line. >>> Control-C pops a single report line >>> >>> >>> >>> RTH | lat min | ovl min | lat avg | lat max | ovl max | overruns >>> ^CRTD >>> >>> | 79 | 79 | 24641422 | 4195964 | 4195964 | 0 >>> >>> >>> >>> Continues to hang until a couple more Control-C's dumps me back to >>> my shell. Seems like something about RTAI's userspace stuff is >>> choking on this machine. >> Yes, it went as expected. In fact the latency calibration does not run >> to an end because user space tasks remains stalled somewhere. > Meanwhile I've had >> the chance of trying RTAI Vulcano on a machine with 3.18.22, not mine. >> At first it seemed it had problems but then we discovered they were >> related to the use of differing compiler versions being used for Linux >> and RTAI. Using the same compiler everything worked as expected. With >> it I've seen RTAI-Vulcano working on 8 different PCs, with quite >> diverse CPUS version and number, chipset and Linux distributions. >> Can you try with Linux-4.1.18? I do not expect any change, just >> curious to see what happens. > >> Paolo >> >> >>> -Duane >>> >>> >>> >>> -----Original Message----- >>> From: Paolo Mantegazza >>> [mailto:[email protected]<mailto:[email protected] >>>> ] >>> Sent: Friday, April 15, 2016 5:45 PM >>> To: Duane AW. Jeffery >>> <[email protected]<mailto:[email protected]>>; >>> Felix Frey > <[email protected]<mailto:[email protected]>>; >>> [email protected]<mailto:[email protected]> Subject: RE: [Rtai] RTAI-5 make >>> hangs at self-calibrate. >>> >>> >>> >>> Let's get rid of the user space calibration and see if RTAI works. >>> For that edit the file rtai_instal_dir/calibrate/latencies and set >>> the only record there as "1201 1700 100000". > Then try the user space latency >>> test. Let's see if it runs and how. Paolo >>> >>> >>> >>> ________________________________________ >>> From: Duane AW. Jeffery >>> [[email protected]<mailto:[email protected]>] > Sent: >>> Friday, April 15, 2016 8:36 PM >>> To: Paolo Mantegazza; Felix Frey; >>> [email protected]<mailto:[email protected]> >>> Subject: RE: [Rtai] RTAI-5 make hangs at self-calibrate. >>> >>> >>> >>> Checking my linux .config, grep for NO_HZ returned >>> >>> >>> >>> CONFIG_NO_HZ_COMMON=y >>> CONFIG_NO_HZ_IDLE=y >>> CONFIG_NO_HZ=y >>> # CONFIG_RCU_FAST_NO_HZ is not set >>> >>> >>> >>> Grep for CPU_IDLE returned >>> >>> >>> >>> # CONFIG_CPU_IDLE is not set >>> >>> >>> >>> Grep for CPU_FREQ returned >>> >>> >>> >>> # CONFIG_CPU_FREQ is not set >>> >>> >>> >>> Attempted your mod to base/arch/x86/calibration/calibrate.c -- I >>> don't see CONFIG_CPU_IDLE in there at all, but I think you meant >>> DIAG_KF_LAT_EVAL, which was #define'd to 0, and used throughout to >>> switch off several rt_printk's. I changed its define to 1, >>> recompiled rtai, rebooted, and tried again, and I found that the >>> result seems to be the same. Dmesg shows the kernel space cal >>> complete ok, and the user space one not start >>> -- no new lines in dmesg at all. Ps aux still shows that calibrate >>> script being called with the same parameters as you'd expect. >>> >>> -Duane >>> >>> >>> >>> -----Original Message----- >>> From: Paolo Mantegazza >>> [mailto:[email protected]<mailto:[email protected] >>>> ] >>> Sent: Friday, April 15, 2016 10:23 AM >>> To: Duane AW. Jeffery >>> <[email protected]<mailto:[email protected]>>; >>> Felix Frey > <[email protected]<mailto:[email protected]>>; >>> [email protected]<mailto:[email protected]> Subject: Re: [Rtai] RTAI-5 make >>> hangs at self-calibrate. >>> >>> >>> >>> With Linux be sure NO_HZ is on, it should by default. Then you do no >>> need the BIOS to fix freq scaling and idlle. > CONFIG_CPU_FREQ and >>> CONFIG_CPU_IDLE can be set while configuring Linux. Even if I find >>> it strange that it does not calibrate user space, after succeeding >>> in kernel space, the method is the same, I'll be happy to have it >>> better. In such a view having troubles on a machine could be a >>> bless. Unfortunately it's not mine. In any case there is still one >>> thing you can try. In base/arch/x86/calibration/calibrate.c there is the macro CONFIG_CPU_IDLE. >>> You should set it to 1 and retry. It will flood your dmesg with 10 >>> thousands lines per second but you'll see what's going on. Take into >>> account that the loop must last, with the default calibration values >>> of RTAI config, no more than 1 sec.> >>> >>> >>> Paolo >>> >>> >>> >>> On 04/15/2016 04:03 PM, Duane AW. Jeffery wrote: >>> >>>> Processor on this machine is an Intel BYT-M 4core 3540, up to >>>> 2.66GHz, so says the sticker on it. >>>> >>>> Cat /proc/cpuinfo seems to call it a Pentium N3540 @ 2.16GHz, and >>>> shows its MHz as 2163.20 (which is the one parameter that seems to >>>> get passed to the calibrate script) The second parameter passed >>>> seems to be the result from the kernel latency test in the "LEAST = xxxx" field. >>>> >>>> Perhaps it's one of these chips that does the frequency scaling and >>>> stuff for battery life and that's making the calibrate hang? On >>>> AMD machines I'm used to turning off some of those things in the >>>> BIOS, but this machine doesn't seem to have any such options. The >>>> kernel config I'm running started as Shahbaz' default 64bit one, >>>> and then I added the things I needed for this machine, so it's pretty minimal. >>>> >>>> I tried manually calling the script from /usr/realtime/calibration >>>> with a ./run, and it hangs in the same place. This time, the >>>> commands in ps aux are slightly different (the LEAST = parameter >>>> has changed a bit), dmesg looks similar, slightly different values of course. >>>> >>>> Not sure what else to try. >>>> >>>> >>>> >>>> -Duane >>>> >>>> >>>> >>>> -----Original Message----- >>>> From: Rtai >>>> [mailto:[email protected]<mailto:[email protected]>] >>>> On Behalf Of Paolo > Mantegazza >>>> Sent: Friday, April 15, 2016 5:52 AM >>>> To: Felix Frey <[email protected]<mailto:[email protected]>>; >>>> [email protected]<mailto:[email protected]> > Subject: Re: [Rtai] RTAI-5 make >>>> hangs at self-calibrate. >>>> >>>> >>>> >>>> On 04/15/2016 11:25 AM, Felix Frey wrote: >>>> >>>>> Just checked with latest Vulcano and kernel 3.18.22 on my AMD GX-210. >>>>> >>>>> >>>>> >>>>> Insmoding rtai_sched tells: >>>>> >>>>> >>>>> >>>>> [ 191.152594] USERMODE CHECK: OK. >>>>> [ 191.152604] USERMODE CHECK PROVIDED (ns): KernelLatency -1, >>>>> UserLatency -1. > [ 191.277545] KERNEL SPACE LATENCY ENDED AT CYCLE: >>>>> 1243, LATENCY = 4271, VARIANCE = 33761/10004569, GAIN = >>>>> 843651/1000000000, LEAST = 3520. [ 191.357327] AFTER KERNEL >>>>> CALIBRATION (WITH RTAI TASK, ns): KernelLatency 3526, UserLatency >>>>> -1 >>>>> (CALIBRATION: PERIOD 10000 (ns), TIME 204699629 (ns)). [ >>>>> 191.480609] USER SPACE LATENCY ENDED AT CYCLE: 1203, LATENCY = >>>>> 4899.93, VARIANCE = 0.00352333, GAIN = 0.000880833, LEAST = 4634. >>>>> [ 191.482291] USERMODE USER SPACE CALIBRATION: OK. >>>>> [ 191.482300] AFTER USER CALIBRATION (ns): KernelLatency 3526, >>>>> UserLatency 4642 (CALIBRATION: PERIOD 10000 (ns), TIME 124954629 >>>>> (ns)). > [ 191.482306] FINAL CALIBRATION SUMMARY (ns): KernelLatency >>>>> 3526, UserLatency 4642.>>> >>>>> >>>>> >>>>> Seems to be ok. >>>> Yes it is, thanks for your patience in pursuing the check. >>>> Paolo. >>>> >>>>> Felix >>>>> >>>>> >>>>> >>>>> >>>>>> I've no clue at the moment. >>>>>> I just know that on my 3 test machines, gcc ranging from >>>>>> 3.something to 4.something, ubunt 8.somenthing to 14.something, P >>>>>> III to XEON, I get the following diagnostic summary: > [ 872.146524] USERMODE CHECK: >>>>>> OK. >>>>>> [ 872.146531] USERMODE CHECK PROVIDED (ns): KernelLatency -1, >>>>>> UserLatency -1. > [ 872.271467] KERNEL SPACE LATENCY ENDED AT CYCLE: >>>>>> 1243, LATENCY = 5519, VARIANCE = 33761/10004569, GAIN = >>>>>> 843651/1000000000, LEAST = 5115. [ 872.348028] AFTER KERNEL >>>>>> CALIBRATION (WITH RTAI TASK, ns): KernelLatency 1698, UserLatency >>>>>> -1 >>>>>> (CALIBRATION: PERIOD 10000 (ns), TIME 201475012 (ns)). [ >>>>>> 872.477559] USER SPACE LATENCY ENDED AT CYCLE: 1203, LATENCY = >>>>>> 11950.4, VARIANCE = 0.00352333, GAIN = 0.000880833, LEAST = >>>>>> 11250. [ 872.496137] USERMODE USER SPACE CALIBRATION: OK. >>>>>> [ 872.496148] AFTER USER CALIBRATION (ns): KernelLatency 1698, >>>>>> UserLatency 3736 (CALIBRATION: PERIOD 10000 (ns), TIME 148104409 >>>>>> (ns)). > [ 872.496152] FINAL CALIBRATION SUMMARY (ns): KernelLatency >>>>>> 1698, UserLatency 3736. Figures can be differ for differing >>>>>> machines but I do not see why anything should hang. Your listing >>>>>> shows that the kernel part has finished, while ps aux shows the >>>>>> user space part running, even if I do not see where >>>>>> /usr/realtime/calibration/latencies 216320 2600 comes from. In >>>>>> any case the user space part, with the defaul frequency and >>>>>> calibration cycles, cannot but last 1 second What is the >>>>>> frequency of your CPU, something about I GHz? So >>>>>> >>>>>> >>>>>> >>>>>> Paolo. >>>>>> >>>>>> >>>>>> >>>>>> ________________________________________ >>>>>> From: Duane AW. Jeffery >>>>>> [[email protected]<mailto:[email protected]>] >>>>>> Sent: Thursday, April 14, 2016 7:24 PM >>>>>> To: Paolo Mantegazza >>>>>> Cc: '[email protected]<mailto:[email protected]>' >>>>>> Subject: RE: [Rtai] RTAI-5 make hangs at self-calibrate. >>>>>> >>>>>> >>>>>> >>>>>> Tried Vulcano just now, after some fiddling, I was able to get it >>>>>> to compile, but then trying to insmod rtai_sched.ko seems to hang >>>>>> the terminal. >>>>>> >>>>>> Checking with another terminal, the last few lines of dmesg are like: >>>>>> >>>>>> >>>>>> >>>>>> USERMODE CHECK: OK >>>>>> USERMODE CHECK PROVIDED (ns): KernelLatency -1, UserLatency -1. >>>>>> KERNEL SPACE LATENCY ENDED AT CYCLE: 1243, LATENCY = 3058, >>>>>> VARIANCE = 33761/10004569, GAIN = 843651/1000000000, LEAST = 2600. > AFTER KERNEL >>>>>> CALIBRATION (WITH RTAI TASK, ns): KernelLatency 1201, UserLatency >>>>>> -1 >>>>>> (CALIBRATION: PERIOD 10000 (ns), TIME 201353401 (ns)).>>>> >>>>>> >>>>>> >>>>>> Ps aux shows the following command running: >>>>>> >>>>>> >>>>>> >>>>>> /usr/realtime/calibration/calibrate >>>>>> /usr/realtime/calibration/latencies 216320 2600 >>>>>> >>>>>> >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> >>>>>> >>>>>> -Duane >>>>>> >>>>>> >>>>>> >>>>>> From: Paolo Mantegazza >>>>>> [mailto:[email protected]<mailto:paolo.mantegazza@polimi >>>>>> .it>] >>>>>> > Sent: Thursday, April 14, 2016 7:03 AM >>>>>> To: Duane AW. Jeffery >>>>>> <[email protected]<mailto:[email protected]>> >>>>>> Subject: Re: [Rtai] RTAI-5 make hangs at self-calibrate. >>>>>> >>>>>> >>>>>> >>>>>> My suggestion is that you try VULCANO CVS. It wil be released as >>>>>> 5.0 >>>>>> test2 next week or so. > One of the new things that come with it is >>>>>> exactly a new calibration procedure. I got a check, witnessed on >>>>>> this list, by just one user but two or three more fedback to me >>>>>> privatly it worked. So another check is welcomed. >>>>>> >>>>>> >>>>>> >>>>>> Paolo >>>>>> >>>>>> >>>>>> >>>>>> On 04/13/2016 10:28 PM, Duane AW. Jeffery wrote: >>>>>> Hi all, >>>>>> >>>>>> >>>>>> >>>>>> I'm working on a new laptop (ASUS E402M) and trying to get RTAI >>>>>> to compile on it. >>>>>> >>>>>> I am running kernel 3.18.22 - updated into what is otherwise a >>>>>> Slackware 14.1 install. I have applied the hal patch and >>>>>> successfully compiled and booted my patched linux kernel. >>>>>> >>>>>> When I go to my RTAI source tree, unpacked into /usr/src/<folder> >>>>>> symlinked to /usr/src/rtai and try to compile it (first make >>>>>> menuconfig to setup, and then make), it begins ok, and then gets >>>>>> to the part where it calls "/bin/sh >>>>>> ../../base/sched/selfcalibrate.sh x86", and then it just hangs there forever. >>>>>> >>>>>> If I switch to another terminal, I can see that lsmod reports >>>>>> rtai_hal and rtai_tmpsched are loaded, and then that dmesg shows >>>>>> some messages that look ok from both the rtai_hal module and the >>>>>> rtai_tmpsched module. Checking ps aux shows that the >>>>>> selfcalibrate.sh script is still running, and has called >>>>>> "/usr/src/rtai/base/arch/x86/calibration/.libs/lt-calibrate >>>>>> ../arch/x86/hal" which is also still running. Along with a "tee >>>>>> tmp_output". >>>>>> >>>>>> Looking at the tmp_output file in /usr/src/rtai/base/sched/ >>>>>> reveals an empty file. Also running is [RTAI_KTHRD_SRVR]. >>>>>> >>>>>> I have tried both RTAI 5.0-test1.tar.bz2 as posted on the main >>>>>> page of www.rtai.org<http://www.rtai.org><http://www.rtai.org>, >>>>>> and also tried ShabbyX's github master tree. Both fail the same way. >>>>>> >>>>>> Anybody have any idea what's going on here? I've compiled RTAI >>>>>> many times before without this problem occurring, but never on >>>>>> this hardware. >>>>>> >>>>>> -Duane >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> >>>>>> >>>>>> >>>>>> Rtai mailing list >>>>>> >>>>>> >>>>>> >>>>>> [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:R >>>>>> tai@rt >>>>>> ai.org>> >>>>>> >>>>>> 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]<mailto:[email protected]> >>>> https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai >> >> >> >> ------------------------------ >> >> Message: 2 >> Date: Tue, 19 Apr 2016 09:19:26 +0200 >> From: Paolo Mantegazza >> <[email protected]<mailto:[email protected]>> > To: "Duane >> AW. Jeffery" >> <[email protected]<mailto:[email protected]>>, >> Felix Frey <[email protected]<mailto:[email protected]>>, >> "[email protected]<mailto:[email protected]>" >> <[email protected]<mailto:[email protected]>> >> Subject: Re: [Rtai] RTAI-5 make hangs at self-calibrate. >> Message-ID: >> <[email protected]<mailto:[email protected]>> >> Content-Type: text/plain; charset="windows-1252"; format=flowed >> >> On 04/18/2016 09:57 PM, Duane AW. Jeffery wrote: >> >>> I tried it on 4.1.18, no change. Still works in kernel mode, does >>> not work in userspace mode. >>> >>> Dmesg does not seem to have any instructive messages either, I don't >>> think. Just looks like things loading up and then unloading when I >>> control-C it. >>> >>> For what its worth, each time I've Control-C'd the userspace one, I >>> get the same numbers (79, 79, 24641422, 4195964, 4195964, 0) on that line. >>> Perhaps they might lead to an answer? >> No hope, it is just the uninitialized buffer of the display task when >> it closes without any communication. >> I've no further clue at the moment. >> The only thing left you could try is the latency test under >> testsuite/kthreads/latency. It is in kernel space but I'm expecting >> it'll behave as its sibling in user space. >> >> Paolo >> >>> >>> -Duane >>> >>> >>> >>> -----Original Message----- >>> From: Paolo Mantegazza >>> [mailto:[email protected]<mailto:[email protected] >>>> ] >>> Sent: Monday, April 18, 2016 11:55 AM >>> To: Duane AW. Jeffery >>> <[email protected]<mailto:[email protected]>>; >>> Felix Frey <[email protected]<mailto:[email protected]>>; >>> [email protected]<mailto:[email protected]> > Subject: Re: [Rtai] RTAI-5 make >>> hangs at self-calibrate. >>> >>> >>> >>> On 04/18/2016 05:33 PM, Duane AW. Jeffery wrote: >>> >>>> I set /usr/realtime/calibration/latencies to be a text file >>>> containing >>>> "1201 1700 100000<linefeed>". >>>> >>>> I tried running /usr/realtime/testsuite/kern/latency/run and got a >>>> typical latency report showing ovlmax around 2500ns. In other >>>> words -- kernel space seems to be working, not really surprising >>>> since we saw that in the attempted calibration. >>>> >>>> Tried running /usr/realtime/testsuite/user/latency/run and get what >>>> appears to start, and then hangs after printing the header line. >>>> Control-C pops a single report line >>>> >>>> >>>> >>>> RTH | lat min | ovl min | lat avg | lat max | ovl max | overruns >>>> ^CRTD >>>> >>>> | 79 | 79 | 24641422 | 4195964 | 4195964 | 0 >>>> >>>> >>>> >>>> Continues to hang until a couple more Control-C's dumps me back to >>>> my shell. Seems like something about RTAI's userspace stuff is >>>> choking on this machine. >>> Yes, it went as expected. In fact the latency calibration does not >>> run to an end because user space tasks remains stalled somewhere. > Meanwhile >>> I've had the chance of trying RTAI Vulcano on a machine with >>> 3.18.22, not mine. At first it seemed it had problems but then we >>> discovered they were related to the use of differing compiler >>> versions being used for Linux and RTAI. Using the same compiler >>> everything worked as expected. With it I've seen RTAI-Vulcano >>> working on 8 different PCs, with quite diverse CPUS version and >>> number, chipset and Linux distributions.> >>> >>> >>> Can you try with Linux-4.1.18? I do not expect any change, just >>> curious to see what happens. >>> >>> Paolo >>> >>> >>> >>>> -Duane >>>> >>>> >>>> >>>> -----Original Message----- >>>> From: Paolo Mantegazza >>>> [mailto:[email protected]<mailto:[email protected] >>>> t>] >>>> Sent: Friday, April 15, 2016 5:45 PM >>>> To: Duane AW. Jeffery >>>> <[email protected]<mailto:[email protected]>>; >>>> Felix Frey > <[email protected]<mailto:[email protected]>>; >>>> [email protected]<mailto:[email protected]> Subject: RE: [Rtai] RTAI-5 make >>>> hangs at self-calibrate. >>>> >>>> >>>> >>>> Let's get rid of the user space calibration and see if RTAI works. >>>> For that edit the file rtai_instal_dir/calibrate/latencies and set >>>> the only record there as "1201 1700 100000". > Then try the user space >>>> latency test. Let's see if it runs and how. Paolo >>>> >>>> >>>> >>>> ________________________________________ >>>> From: Duane AW. Jeffery >>>> [[email protected]<mailto:[email protected]>] > Sent: >>>> Friday, April 15, 2016 8:36 PM >>>> To: Paolo Mantegazza; Felix Frey; >>>> [email protected]<mailto:[email protected]> >>>> Subject: RE: [Rtai] RTAI-5 make hangs at self-calibrate. >>>> >>>> >>>> >>>> Checking my linux .config, grep for NO_HZ returned >>>> >>>> >>>> >>>> CONFIG_NO_HZ_COMMON=y >>>> CONFIG_NO_HZ_IDLE=y >>>> CONFIG_NO_HZ=y >>>> # CONFIG_RCU_FAST_NO_HZ is not set >>>> >>>> >>>> >>>> Grep for CPU_IDLE returned >>>> >>>> >>>> >>>> # CONFIG_CPU_IDLE is not set >>>> >>>> >>>> >>>> Grep for CPU_FREQ returned >>>> >>>> >>>> >>>> # CONFIG_CPU_FREQ is not set >>>> >>>> >>>> >>>> Attempted your mod to base/arch/x86/calibration/calibrate.c -- I >>>> don't see CONFIG_CPU_IDLE in there at all, but I think you meant >>>> DIAG_KF_LAT_EVAL, which was #define'd to 0, and used throughout to >>>> switch off several rt_printk's. I changed its define to 1, >>>> recompiled rtai, rebooted, and tried again, and I found that the >>>> result seems to be the same. Dmesg shows the kernel space cal >>>> complete ok, and the user space one not start -- no new lines in >>>> dmesg at all. Ps aux still shows that calibrate script being >>>> called with the same parameters as you'd expect. >>>> >>>> -Duane >>>> >>>> >>>> >>>> -----Original Message----- >>>> From: Paolo Mantegazza >>>> [mailto:[email protected]<mailto:[email protected] >>>> t>] >>>> Sent: Friday, April 15, 2016 10:23 AM >>>> To: Duane AW. Jeffery >>>> <[email protected]<mailto:[email protected]>>; >>>> Felix Frey > <[email protected]<mailto:[email protected]>>; >>>> [email protected]<mailto:[email protected]> Subject: Re: [Rtai] RTAI-5 make >>>> hangs at self-calibrate. >>>> >>>> >>>> >>>> With Linux be sure NO_HZ is on, it should by default. Then you do >>>> no need the BIOS to fix freq scaling and idlle. > CONFIG_CPU_FREQ and >>>> CONFIG_CPU_IDLE can be set while configuring Linux. Even if I find >>>> it strange that it does not calibrate user space, after succeeding >>>> in kernel space, the method is the same, I'll be happy to have it better. >>>> In such a view having troubles on a machine could be a bless. >>>> Unfortunately it's not mine. In any case there is still one thing >>>> you can try. In base/arch/x86/calibration/calibrate.c there is the >>>> macro CONFIG_CPU_IDLE. You should set it to 1 and retry. It will >>>> flood your dmesg with 10 thousands lines per second but you'll see what's going on. >>>> Take into account that the loop must last, with the default >>>> calibration values of RTAI config, no more than 1 sec.>> >>>> >>>> >>>> Paolo >>>> >>>> >>>> >>>> On 04/15/2016 04:03 PM, Duane AW. Jeffery wrote: >>>> >>>>> Processor on this machine is an Intel BYT-M 4core 3540, up to >>>>> 2.66GHz, so says the sticker on it. >>>>> >>>>> Cat /proc/cpuinfo seems to call it a Pentium N3540 @ 2.16GHz, and >>>>> shows its MHz as 2163.20 (which is the one parameter that seems to >>>>> get passed to the calibrate script) The second parameter passed >>>>> seems to be the result from the kernel latency test in the "LEAST = xxxx" field. >>>>> >>>>> Perhaps it's one of these chips that does the frequency scaling >>>>> and stuff for battery life and that's making the calibrate hang? >>>>> On AMD machines I'm used to turning off some of those things in >>>>> the BIOS, but this machine doesn't seem to have any such options. >>>>> The kernel config I'm running started as Shahbaz' default 64bit >>>>> one, and then I added the things I needed for this machine, so it's pretty minimal. >>>>> >>>>> I tried manually calling the script from /usr/realtime/calibration >>>>> with a ./run, and it hangs in the same place. This time, the >>>>> commands in ps aux are slightly different (the LEAST = parameter >>>>> has changed a bit), dmesg looks similar, slightly different values of course. >>>>> >>>>> Not sure what else to try. >>>>> >>>>> >>>>> >>>>> -Duane >>>>> >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: Rtai >>>>> [mailto:[email protected]<mailto:[email protected]>] >>>>> On Behalf Of Paolo > Mantegazza >>>>> Sent: Friday, April 15, 2016 5:52 AM >>>>> To: Felix Frey <[email protected]<mailto:[email protected]>>; >>>>> [email protected]<mailto:[email protected]> > Subject: Re: [Rtai] RTAI-5 make >>>>> hangs at self-calibrate. >>>>> >>>>> >>>>> >>>>> On 04/15/2016 11:25 AM, Felix Frey wrote: >>>>> >>>>>> Just checked with latest Vulcano and kernel 3.18.22 on my AMD GX-210. >>>>>> >>>>>> >>>>>> >>>>>> Insmoding rtai_sched tells: >>>>>> >>>>>> >>>>>> >>>>>> [ 191.152594] USERMODE CHECK: OK. >>>>>> [ 191.152604] USERMODE CHECK PROVIDED (ns): KernelLatency -1, >>>>>> UserLatency -1. > [ 191.277545] KERNEL SPACE LATENCY ENDED AT CYCLE: >>>>>> 1243, LATENCY = 4271, VARIANCE = 33761/10004569, GAIN = >>>>>> 843651/1000000000, LEAST = 3520. [ 191.357327] AFTER KERNEL >>>>>> CALIBRATION (WITH RTAI TASK, ns): KernelLatency 3526, UserLatency >>>>>> -1 >>>>>> (CALIBRATION: PERIOD 10000 (ns), TIME 204699629 (ns)). [ >>>>>> 191.480609] USER SPACE LATENCY ENDED AT CYCLE: 1203, LATENCY = >>>>>> 4899.93, VARIANCE = 0.00352333, GAIN = 0.000880833, LEAST = 4634. >>>>>> [ 191.482291] USERMODE USER SPACE CALIBRATION: OK. >>>>>> [ 191.482300] AFTER USER CALIBRATION (ns): KernelLatency 3526, >>>>>> UserLatency 4642 (CALIBRATION: PERIOD 10000 (ns), TIME 124954629 >>>>>> (ns)). > [ 191.482306] FINAL CALIBRATION SUMMARY (ns): KernelLatency >>>>>> 3526, UserLatency 4642.>>>> >>>>>> >>>>>> >>>>>> Seems to be ok. >>>>> Yes it is, thanks for your patience in pursuing the check. >>>>> Paolo. >>>>> >>>>>> Felix >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> I've no clue at the moment. >>>>>>> I just know that on my 3 test machines, gcc ranging from >>>>>>> 3.something to 4.something, ubunt 8.somenthing to 14.something, >>>>>>> P III to XEON, I get the following diagnostic summary: > [ 872.146524] USERMODE CHECK: >>>>>>> OK. >>>>>>> [ 872.146531] USERMODE CHECK PROVIDED (ns): KernelLatency -1, >>>>>>> UserLatency -1. > [ 872.271467] KERNEL SPACE LATENCY ENDED AT CYCLE: >>>>>>> 1243, LATENCY = 5519, VARIANCE = 33761/10004569, GAIN = >>>>>>> 843651/1000000000, LEAST = 5115. [ 872.348028] AFTER KERNEL >>>>>>> CALIBRATION (WITH RTAI TASK, ns): KernelLatency 1698, >>>>>>> UserLatency -1 >>>>>>> (CALIBRATION: PERIOD 10000 (ns), TIME 201475012 (ns)). [ >>>>>>> 872.477559] USER SPACE LATENCY ENDED AT CYCLE: 1203, LATENCY = >>>>>>> 11950.4, VARIANCE = 0.00352333, GAIN = 0.000880833, LEAST = >>>>>>> 11250. [ 872.496137] USERMODE USER SPACE CALIBRATION: OK. >>>>>>> [ 872.496148] AFTER USER CALIBRATION (ns): KernelLatency 1698, >>>>>>> UserLatency 3736 (CALIBRATION: PERIOD 10000 (ns), TIME 148104409 >>>>>>> (ns)). > [ 872.496152] FINAL CALIBRATION SUMMARY (ns): KernelLatency >>>>>>> 1698, UserLatency 3736. Figures can be differ for differing >>>>>>> machines but I do not see why anything should hang. Your listing >>>>>>> shows that the kernel part has finished, while ps aux shows the >>>>>>> user space part running, even if I do not see where >>>>>>> /usr/realtime/calibration/latencies 216320 2600 comes from. In >>>>>>> any case the user space part, with the defaul frequency and >>>>>>> calibration cycles, cannot but last 1 second What is the >>>>>>> frequency of your CPU, something about I GHz? So >>>>>>> >>>>>>> >>>>>>> >>>>>>> Paolo. >>>>>>> >>>>>>> >>>>>>> >>>>>>> ________________________________________ >>>>>>> From: Duane AW. Jeffery >>>>>>> [[email protected]<mailto:[email protected]> >>>>>>> ] >>>>>>> Sent: Thursday, April 14, 2016 7:24 PM >>>>>>> To: Paolo Mantegazza >>>>>>> Cc: '[email protected]<mailto:[email protected]>' >>>>>>> Subject: RE: [Rtai] RTAI-5 make hangs at self-calibrate. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Tried Vulcano just now, after some fiddling, I was able to get >>>>>>> it to compile, but then trying to insmod rtai_sched.ko seems to >>>>>>> hang the terminal. >>>>>>> >>>>>>> Checking with another terminal, the last few lines of dmesg are like: >>>>>>> >>>>>>> >>>>>>> >>>>>>> USERMODE CHECK: OK >>>>>>> USERMODE CHECK PROVIDED (ns): KernelLatency -1, UserLatency -1. >>>>>>> KERNEL SPACE LATENCY ENDED AT CYCLE: 1243, LATENCY = 3058, >>>>>>> VARIANCE = 33761/10004569, GAIN = 843651/1000000000, LEAST = 2600. > AFTER KERNEL >>>>>>> CALIBRATION (WITH RTAI TASK, ns): KernelLatency 1201, >>>>>>> UserLatency -1 >>>>>>> (CALIBRATION: PERIOD 10000 (ns), TIME 201353401 (ns)).>>>>> >>>>>>> >>>>>>> >>>>>>> Ps aux shows the following command running: >>>>>>> >>>>>>> >>>>>>> >>>>>>> /usr/realtime/calibration/calibrate >>>>>>> /usr/realtime/calibration/latencies 216320 2600 >>>>>>> >>>>>>> >>>>>>> >>>>>>> Any ideas? >>>>>>> >>>>>>> >>>>>>> >>>>>>> -Duane >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: Paolo Mantegazza >>>>>>> [mailto:[email protected]<mailto:paolo.mantegazza@polim >>>>>>> i.it> >>>>>>> ] > Sent: Thursday, April 14, 2016 7:03 AM >>>>>>> To: Duane AW. Jeffery >>>>>>> <[email protected]<mailto:[email protected]> >>>>>>> Subject: Re: [Rtai] RTAI-5 make hangs at self-calibrate. >>>>>>> >>>>>>> >>>>>>> >>>>>>> My suggestion is that you try VULCANO CVS. It wil be released as >>>>>>> 5.0 >>>>>>> test2 next week or so. > One of the new things that come with it is >>>>>>> exactly a new calibration procedure. I got a check, witnessed on >>>>>>> this list, by just one user but two or three more fedback to me >>>>>>> privatly it worked. So another check is welcomed. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Paolo >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 04/13/2016 10:28 PM, Duane AW. Jeffery wrote: >>>>>>> Hi all, >>>>>>> >>>>>>> >>>>>>> >>>>>>> I'm working on a new laptop (ASUS E402M) and trying to get RTAI >>>>>>> to compile on it. >>>>>>> >>>>>>> I am running kernel 3.18.22 - updated into what is otherwise a >>>>>>> Slackware 14.1 install. I have applied the hal patch and >>>>>>> successfully compiled and booted my patched linux kernel. >>>>>>> >>>>>>> When I go to my RTAI source tree, unpacked into >>>>>>> /usr/src/<folder> symlinked to /usr/src/rtai and try to compile >>>>>>> it (first make menuconfig to setup, and then make), it begins >>>>>>> ok, and then gets to the part where it calls "/bin/sh >>>>>>> ../../base/sched/selfcalibrate.sh x86", and then it just hangs there forever. >>>>>>> >>>>>>> If I switch to another terminal, I can see that lsmod reports >>>>>>> rtai_hal and rtai_tmpsched are loaded, and then that dmesg shows >>>>>>> some messages that look ok from both the rtai_hal module and the >>>>>>> rtai_tmpsched module. Checking ps aux shows that the >>>>>>> selfcalibrate.sh script is still running, and has called >>>>>>> "/usr/src/rtai/base/arch/x86/calibration/.libs/lt-calibrate >>>>>>> ../arch/x86/hal" which is also still running. Along with a "tee >>>>>>> tmp_output". >>>>>>> >>>>>>> Looking at the tmp_output file in /usr/src/rtai/base/sched/ >>>>>>> reveals an empty file. Also running is [RTAI_KTHRD_SRVR]. >>>>>>> >>>>>>> I have tried both RTAI 5.0-test1.tar.bz2 as posted on the main >>>>>>> page of www.rtai.org<http://www.rtai.org><http://www.rtai.org>, >>>>>>> and also tried ShabbyX's github master tree. Both fail the same way. >>>>>>> >>>>>>> Anybody have any idea what's going on here? I've compiled RTAI >>>>>>> many times before without this problem occurring, but never on >>>>>>> this hardware. >>>>>>> >>>>>>> -Duane >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> >>>>>>> >>>>>>> >>>>>>> Rtai mailing list >>>>>>> >>>>>>> >>>>>>> >>>>>>> [email protected]<mailto:[email protected]><mailto:[email protected]<mailto: >>>>>>> Rtai@r >>>>>>> tai.org>> >>>>>>> >>>>>>> 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]<mailto:[email protected]> >>>>> https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai >> >> >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> Rtai mailing list >> [email protected]<mailto:[email protected]> >> https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai >> >> ------------------------------ >> >> End of Rtai Digest, Vol 100, Issue 22 >> ************************************* > > _______________________________________________ > 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