Re: [Xenomai-core] errors to console when running xeno-test (latency -t 1)
Jim Cromie wrote: > hello xenophiles, > > Im getting errors to the console when running latency -t 1. > they also appear in dmesg output This should be fixed in revision 807. -- Gilles Chanteperdrix. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] errors to console when running xeno-test (latency -t 1)
Jim Cromie wrote:
> hello xenophiles,
>
> Im getting errors to the console when running latency -t 1.
> they also appear in dmesg output
The attached patch seems to solve the issue here, but I am not sure it
should...
--
Gilles Chanteperdrix.
Index: include/asm-i386/system.h
===
--- include/asm-i386/system.h (revision 806)
+++ include/asm-i386/system.h (working copy)
@@ -422,7 +422,7 @@
{
struct task_struct *task = tcb->user_task;
-if (task && !wrap_test_fpu_used(task))
+if (task && !xnarch_fpu_init_p(task))
return;
clts();
___
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] errors to console when running xeno-test (latency -t 1)
Jim Cromie wrote: > hello xenophiles, > > Im getting errors to the console when running latency -t 1. Fully reproducible here, with a simple ping flood... Both with and without fxsr. -- Gilles Chanteperdrix. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] errors to console when running xeno-test (latency -t 1)
hello xenophiles, Im getting errors to the console when running latency -t 1. they also appear in dmesg output RTD| 16.615| 32.201| 44.845| 0| 14.054| 45.621 [ 917.477135] invalid use of FPU in Xenomai context at 0xb7e488bc RTD| 15.832| 32.166| 44.756| 0| 14.054| 45.621 [ 918.476991] invalid use of FPU in Xenomai context at 0xb7e488bc RTD| 14.542| 32.206| 44.098| 0| 14.054| 45.621 [ 919.476834] invalid use of FPU in Xenomai context at 0xb7e488bc RTD| 14.669| 32.172| 44.248| 0| 14.054| 45.621 [ 920.476706] invalid use of FPU in Xenomai context at 0xb7e488bc RTD| 15.326| 32.175| 43.045| 0| 14.054| 45.621 [ 921.476535] invalid use of FPU in Xenomai context at 0xb7e488bc RTD| 15.048| 32.216| 44.695| 0| 14.054| 45.621 [ 922.476384] invalid use of FPU in Xenomai context at 0xb7e488bc RTD| 15.344| 32.220| 52.680| 0| 14.054| 52.680 [ 923.476234] invalid use of FPU in Xenomai context at 0xb7e488bc RTD| 16.360| 32.206| 43.913| 0| 14.054| 52.680 [ 924.476085] invalid use of FPU in Xenomai context at 0xb7e488bc RTD| 14.384| 32.211| 44.275| 0| 14.054| 52.680 [ 925.475933] invalid use of FPU in Xenomai context at 0xb7e488bc RTD| 14.883| 32.181| 43.601| 0| 14.054| 52.680 [ 926.475783] invalid use of FPU in Xenomai context at 0xb7e488bc RTD| 14.684| 32.199| 44.587| 0| 14.054| 52.680 Ive attached a logfile, written by xeno-test. Hopefully it has enough detail for you to diagnose my problem ;-) (actually, there are probably trivial additions to xeno-test that would enhance the info it provides for debugging purposes forex: it currently greps XENO out of /proc/config.gz, if you identify other CONFIG_* items that are worth collecting, I'll add them. ( PREEMPT, MUTEX, ...). Or it can just cat /proc/config.gz to the log, and get everything. Also, my brand new 2.6.16-ipipe-121 kernel took quite a long time to boot. Ive seen this intermittently thru 2.6.1[45]-* series, mostly in -mm*, -rc* too (I think) but have never isolated any cause. So its probably my setup somehow... At some risk of running on too long, Ive noticed an oddity in dmesg output: do these large timestamps b4 zeroing matter ? soekris:/usr/xenomai/bin# dmesg |more [17179569.184000] Linux version 2.6.16-ipipe-121-sk ([EMAIL PROTECTED]) (gcc version 4.0.2 20051125 (Red Hat 4.0.2-8)) #4 Sun Mar 26 20:07:17 EST 2006 [17179569.184000] BIOS-provided physical RAM map: [17179569.184000] BIOS-e820: - 0009fc00 (usable) [17179569.184000] BIOS-e820: 0009fc00 - 000a (reserved) [17179569.184000] BIOS-e820: 000f - 0010 (reserved) [17179569.184000] BIOS-e820: 0010 - 0800 (usable) [17179569.184000] BIOS-e820: fff0 - 0001 (reserved) [17179569.184000] 128MB LOWMEM available. [17179569.184000] On node 0 totalpages: 32768 [17179569.184000] DMA zone: 4096 pages, LIFO batch:0 [17179569.184000] DMA32 zone: 0 pages, LIFO batch:0 [17179569.184000] Normal zone: 28672 pages, LIFO batch:7 [17179569.184000] HighMem zone: 0 pages, LIFO batch:0 [17179569.184000] DMI not present or invalid. [17179569.184000] Allocating PCI resources starting at 1000 (gap: 0800:f7f0) [17179569.184000] Built 1 zonelists [17179569.184000] Kernel command line: console=ttyS0,115200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/truck nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 panic=5 initrd=initrd-2.6.16-ipipe-121-sk.img BOOT_IMAGE=vmlinuz-2.6.16-ipipe-121-sk [17179569.184000] Initializing CPU#0 [17179569.184000] PID hash table entries: 1024 (order: 10, 16384 bytes) [0.00] Detected 266.696 MHz processor. [ 20.833323] Using tsc for high-res timesource [ 20.833436] I-pipe 1.2-01: pipeline enabled. [ 20.833781] Console: colour dummy device 80x25 [ 20.956810] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [ 20.966149] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [ 21.009759] Memory: 126112k/131072k available (1602k kernel code, 4540k reserved, 741k data, 120k init, 0k highmem) Script started on Sun Mar 26 17:40:00 2006 running ./xeno-test -T 60 -h -s -l 0 Sun Mar 26 17:40:01 PST 2006 running: cat /proc/cpuinfo processor : 0 vendor_id : Geode by NSC cpu family : 5 model : 9 model name : Unknown stepping: 1 cpu MHz : 266.696 fpu : yes fpu_exception : yes cpuid level : 2 flags : fpu tsc msr cx8 cmov mmx cxmmx bogomips: 536.58 Sun Mar 26 17:40:01 PST 2006 running: cat /proc/meminfo MemTotal: 126264 kB MemFree:
Re: [Xenomai-core] rt-video interface
Em Domingo 26 Março 2006 06:49, Jan Kiszka escreveu: >... >Maybe derived a subset from the full V4L2 API is the way to go. But >let's wait if you discover other interface designs. Actually, my priorities changed again... I'll need to finish (start actually) an application using the camera in a hard real-time context for writing another article for RTSS (http://www.rtss.org) that will happen in Brazil this year. Hope to see some of you here if my article is approved. Then I will come back to my interface designs research... >... >> This method also requires poll and select to be implemented in V4L2. We >> should discuss how to deal with it if we stick with the V4L2 variant idea. > >Hmm, what file descriptors have to be monitored in parallel so that >poll/select is required? I didn't really understand why should poll/select be required, but the author says it is too important to be optional... We should ask him why ;) Anyway, there are more efficient ways for monitoring a buffer state and wait for events in RTDM. I don't think we should use poll/select anyway... >... >> Which vision applications do you have in mind? > >So far "only" a subset of your scenario: One of my colleagues needs to >synchronise frame timestamps with timestamps of other input, from range >sensors e.g. The actually processing is not (yet?) hard RT, but the >input synchronisation is essential. I think that the timestamp provided by the interface is enough, don't you think? Best Regards, Rodrigo. ___ Yahoo! doce lar. Faça do Yahoo! sua homepage. http://br.yahoo.com/homepageset.html ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] CONFIG_XENO_OPT_DEBUG_LEVEL
Jan Kiszka wrote: Here is an attempt to base the activation of XENO_ASSERT on a subsystem debug switch at compile time, applied on RTDM. The procedure of adding a new system for XENO_ASSERT usage would be to define the required kbuild switch according to the naming scheme CONFIG_XENO_OPT_DEBUG_subsystem, include nucleus/assert.h, and add "#define CONFIG_XENO_OPT_DEBUG_subsystem 0" for the unset case. XENO_ASSERT is new called with (subsystem, condition, action). If we invent further debugging macros, they could be controlled in a similar way. What do you think? I like the flexibity this approach brings (even if I think that the context checking in drvlib.c should be done unconditionally, regardless of the debug mode -- but that's probably a matter of personal taste). I've merged this patch, so that we can further use this debug infrastructure in other sub-systems. Thanks. -- Philippe. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] xeno-config.man update patch
Romain Lenglet wrote: Hi, Here is a patch that updates the manpage for xeno-config: many options have been removed. Applied. I have checked the other manpages: they seem up-to-date. Thanks (twice). --- xenomai/ChangeLog 2006-03-27 16:29:36.497437408 +0900 +++ xenomai-newman/ChangeLog2006-03-27 18:06:37.297541288 +0900 @@ -1,3 +1,8 @@ +2006-03-27 Romain Lenglet <[EMAIL PROTECTED]> + + * doc/man/xeno-config.man.in: Updated to match the latest revision of + the xeno-config script. + 2006-03-26 Philippe Gerum <[EMAIL PROTECTED]> * ksrc/arch/i386/patches: Upgrade to 2.6.16-1.2-01. @@ -148,7 +153,7 @@ * ksrc/skins/posix/registry.c (pse51_node_lookup): Use different namespaces for different objects types. -2006-02-27 Romain Lenglet <[EMAIL PROTECTED]> +2006-03-08 Romain Lenglet <[EMAIL PROTECTED]> * scripts/prepare-kernel.sh: Added options to select changes to ignore and to not include in the output patch file when the --outpatch option --- xenomai/doc/man/xeno-config.man.in 2006-02-27 09:51:54.785445304 +0900 +++ xenomai-newman/doc/man/xeno-config.man.in 2006-03-27 18:06:51.743345192 +0900 @@ -9,7 +9,7 @@ .\" Xenomai distribution. .\" .pc -.TH XENO-CONFIG 1 "2005-10-18" "@PACKAGE_VERSION@" "Xenomai" +.TH XENO-CONFIG 1 "2006-03-27" "@PACKAGE_VERSION@" "Xenomai" .SH NAME xeno-config \- Display Xenomai libraries configuration .SH SYNOPSIS @@ -20,20 +20,18 @@ .br .B xeno-config \-\-help .br -\fBxeno-config\fP [\fB\-\-version\fP] [\fB\-\-cc\fP] [\fB\-\-cross\-compile\fP] [\fB\-\-arch\fP] [\fB\-\-subarch\fP] [\fB\-\-prefix\fP] [\fB\-\-config\fP] [\fB\-\-mod*\-cflags\fP|\fB\-\-module\-cflags\fP|\fB\-\-kernel\-cflags\fP] [\fB\-\-xeno\-cflags\fP|\fB\-\-fusion\-cflags\fP] [\fB\-\-xeno\-ldflags\fP|\fB\-\-fusion\-ldflags\fP] [\fB\-\-posix\-cflags\fP] [\fB\-\-posix\-ldflags\fP] [\fB\-\-uvm\-cflags\fP] [\fB\-\-uvm\-ldflags\fP] [\fB\-\-linux\-dir\fP|\fB\-\-linux\fP] [\fB\-\-linux\-ver*\fP|\fB\-\-linux\-version\fP] [\fB\-\-mod*\-dir\fP|\fB\-\-module\-dir\fP] [\fB\-\-sym*\-dir\fP|\fB\-\-symbol\-dir\fP] [\fB\-\-lib*\-dir\fP|\fB\-\-library\-dir\fP|\fB\-\-libdir\fP|\fB\-\-user\-libdir\fP] +\fBxeno-config\fP [\fB\-\-version\fP] [\fB\-\-cc\fP] [\fB\-\-arch\fP] [\fB\-\-prefix\fP] [\fB\-\-xeno\-cflags\fP] [\fB\-\-xeno\-ldflags\fP] [\fB\-\-posix\-cflags\fP] [\fB\-\-posix\-ldflags\fP] [\fB\-\-uvm\-cflags\fP] [\fB\-\-uvm\-ldflags\fP] [\fB\-\-lib*\-dir\fP|\fB\-\-library\-dir\fP|\fB\-\-libdir\fP|\fB\-\-user\-libdir\fP] .SH DESCRIPTION \fBxeno-config\fP is a script that is used to to display the compiler and linker flags that are required for building applications that use Xenomai. Any combination of options can be chosen (except \fB\-\-verbose\fP and \fB\-\-help\fP) to display configuration information, and options can be given in any order. The command output one line for each option, in the same order as the options. -When \fBxeno-config \-\-verbose\fP is executed, all configuration information is displayed in a different, human-readable format. +When \fBxeno-config \-\-verbose\fP is executed, all configuration information is displayed in a different, more human-readable format. When \fBxeno-config\fP is executed without any options, the output is equivalent to than when executing \fBxeno-config \-\-verbose\fP then \fBxeno-config \-\-help\fP. .\" .SH OPTIONS -In an option's description, a \fB*\fP in the option name is meant as a wildcard. For instance, \fB\-\-mod\-cflags\fP, \fB\-\-modu\-cflags\fP and \fB\-\-modanything\-cflags\fP are all valid and synonymous options. -.TP .B \-\-v, \-\-verbose Outputs all configuration information, in a human-readable format. .TP @@ -44,35 +42,20 @@ Outputs one line with the installed Xenomai version. .TP .B \-\-cc -Outputs one line with the path to the C compiler command used to compiled Xenomai. -.TP -.B \-\-cross\-compile -Outputs one line with the prefix that was prepended to the command names used to compile Xenomai, e.g. if it was cross-compiled. -The ouput line is empty if no prefix was prepended to command names. +Outputs one line with the path to the C compiler command that was used to compiled Xenomai. .TP .B \-\-arch Outputs one line with the architecture to compile to, e.g. i386. -.TP -.B \-\-subarch -Outputs one line with the sub-architecture to compile to. -The ouput line is empty if not compiling to a specific sub-architecture. +May be different from the architecture of the currently running system, if cross-compiling. .TP .B \-\-prefix Outputs one line with the absolute path to the base Xenomai installation directory. .TP -.B \-\-config -Outputs one line with the absolute path to the configuration file used to compile Xenomai. -.TP -.B \-\-mod*\-cflags, \-\-module\-cflags, \-\-kernel\-cflags -Outputs one
[Xenomai-core] Re: [Xenomai-help] document on running Xenomai on Blackfin 533
Hi Adam, I'm currently revamping the documentation framework. The core stuff is already there but it still needs some customization to generate acceptable and publishable documents. Should be ready within a week I hope as far as html output is concerned. I will then migrate all available documents to xml docbook to finally obtain a real documentation base for the project. I will start with a "Getting Started" document and also technical article already published by Philippe. The first one has the priority and all my attention at the moment though. I think your document could be part of it as architecture dependent section (if you agree of course ;). All documents will finally be accessible from the website. Regards, Bruno Rouchouse On 3/27/06, adam li <[EMAIL PROTECTED]> wrote: Hi,I have played with Xenomai on Blackfin 533. Here is a step by stepdocument on how to enable Xenomai on Blackfin 533 with uClinux for yourinterest: http://docs.blackfin.uclinux.org/doku.php?id=adeosThanks,-Adam___Xenomai-help mailing listXenomai-help@gna.org https://mail.gna.org/listinfo/xenomai-help ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] xeno-config.man update patch
Hi, Here is a patch that updates the manpage for xeno-config: many options have been removed. I have checked the other manpages: they seem up-to-date. -- Romain LENGLET --- xenomai/ChangeLog 2006-03-27 16:29:36.497437408 +0900 +++ xenomai-newman/ChangeLog 2006-03-27 18:06:37.297541288 +0900 @@ -1,3 +1,8 @@ +2006-03-27 Romain Lenglet <[EMAIL PROTECTED]> + + * doc/man/xeno-config.man.in: Updated to match the latest revision of + the xeno-config script. + 2006-03-26 Philippe Gerum <[EMAIL PROTECTED]> * ksrc/arch/i386/patches: Upgrade to 2.6.16-1.2-01. @@ -148,7 +153,7 @@ * ksrc/skins/posix/registry.c (pse51_node_lookup): Use different namespaces for different objects types. -2006-02-27 Romain Lenglet <[EMAIL PROTECTED]> +2006-03-08 Romain Lenglet <[EMAIL PROTECTED]> * scripts/prepare-kernel.sh: Added options to select changes to ignore and to not include in the output patch file when the --outpatch option --- xenomai/doc/man/xeno-config.man.in 2006-02-27 09:51:54.785445304 +0900 +++ xenomai-newman/doc/man/xeno-config.man.in 2006-03-27 18:06:51.743345192 +0900 @@ -9,7 +9,7 @@ .\" Xenomai distribution. .\" .pc -.TH XENO-CONFIG 1 "2005-10-18" "@PACKAGE_VERSION@" "Xenomai" +.TH XENO-CONFIG 1 "2006-03-27" "@PACKAGE_VERSION@" "Xenomai" .SH NAME xeno-config \- Display Xenomai libraries configuration .SH SYNOPSIS @@ -20,20 +20,18 @@ .br .B xeno-config \-\-help .br -\fBxeno-config\fP [\fB\-\-version\fP] [\fB\-\-cc\fP] [\fB\-\-cross\-compile\fP] [\fB\-\-arch\fP] [\fB\-\-subarch\fP] [\fB\-\-prefix\fP] [\fB\-\-config\fP] [\fB\-\-mod*\-cflags\fP|\fB\-\-module\-cflags\fP|\fB\-\-kernel\-cflags\fP] [\fB\-\-xeno\-cflags\fP|\fB\-\-fusion\-cflags\fP] [\fB\-\-xeno\-ldflags\fP|\fB\-\-fusion\-ldflags\fP] [\fB\-\-posix\-cflags\fP] [\fB\-\-posix\-ldflags\fP] [\fB\-\-uvm\-cflags\fP] [\fB\-\-uvm\-ldflags\fP] [\fB\-\-linux\-dir\fP|\fB\-\-linux\fP] [\fB\-\-linux\-ver*\fP|\fB\-\-linux\-version\fP] [\fB\-\-mod*\-dir\fP|\fB\-\-module\-dir\fP] [\fB\-\-sym*\-dir\fP|\fB\-\-symbol\-dir\fP] [\fB\-\-lib*\-dir\fP|\fB\-\-library\-dir\fP|\fB\-\-libdir\fP|\fB\-\-user\-libdir\fP] +\fBxeno-config\fP [\fB\-\-version\fP] [\fB\-\-cc\fP] [\fB\-\-arch\fP] [\fB\-\-prefix\fP] [\fB\-\-xeno\-cflags\fP] [\fB\-\-xeno\-ldflags\fP] [\fB\-\-posix\-cflags\fP] [\fB\-\-posix\-ldflags\fP] [\fB\-\-uvm\-cflags\fP] [\fB\-\-uvm\-ldflags\fP] [\fB\-\-lib*\-dir\fP|\fB\-\-library\-dir\fP|\fB\-\-libdir\fP|\fB\-\-user\-libdir\fP] .SH DESCRIPTION \fBxeno-config\fP is a script that is used to to display the compiler and linker flags that are required for building applications that use Xenomai. Any combination of options can be chosen (except \fB\-\-verbose\fP and \fB\-\-help\fP) to display configuration information, and options can be given in any order. The command output one line for each option, in the same order as the options. -When \fBxeno-config \-\-verbose\fP is executed, all configuration information is displayed in a different, human-readable format. +When \fBxeno-config \-\-verbose\fP is executed, all configuration information is displayed in a different, more human-readable format. When \fBxeno-config\fP is executed without any options, the output is equivalent to than when executing \fBxeno-config \-\-verbose\fP then \fBxeno-config \-\-help\fP. .\" .SH OPTIONS -In an option's description, a \fB*\fP in the option name is meant as a wildcard. For instance, \fB\-\-mod\-cflags\fP, \fB\-\-modu\-cflags\fP and \fB\-\-modanything\-cflags\fP are all valid and synonymous options. -.TP .B \-\-v, \-\-verbose Outputs all configuration information, in a human-readable format. .TP @@ -44,35 +42,20 @@ Outputs one line with the installed Xenomai version. .TP .B \-\-cc -Outputs one line with the path to the C compiler command used to compiled Xenomai. -.TP -.B \-\-cross\-compile -Outputs one line with the prefix that was prepended to the command names used to compile Xenomai, e.g. if it was cross-compiled. -The ouput line is empty if no prefix was prepended to command names. +Outputs one line with the path to the C compiler command that was used to compiled Xenomai. .TP .B \-\-arch Outputs one line with the architecture to compile to, e.g. i386. -.TP -.B \-\-subarch -Outputs one line with the sub-architecture to compile to. -The ouput line is empty if not compiling to a specific sub-architecture. +May be different from the architecture of the currently running system, if cross-compiling. .TP .B \-\-prefix Outputs one line with the absolute path to the base Xenomai installation directory. .TP -.B \-\-config -Outputs one line with the absolute path to the configuration file used to compile Xenomai. -.TP -.B \-\-mod*\-cflags, \-\-module\-cflags, \-\-kernel\-cflags -Outputs one line with the C compiler command-line options that are necessary to compile Linux kernel modules that use the Xenomai Linux kernel modules. -.TP -.B \-\-xeno\-cflags, \-\-fusion\-cflags
