Re: [Xenomai-core] errors to console when running xeno-test (latency -t 1)

2006-03-30 Thread Jim Cromie 

Gilles Chanteperdrix wrote:

Jim Cromie wrote:
 > Gilles Chanteperdrix wrote:
 > > 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.
 > >
 > >   
 > 807 didnt fix it here.  Its also still present in 815


Reverting 807 produces a bug on my test box identical to the one you are
reporting. Merging 807 again make the bug disappear. Could you double
check ? If the bug persists, could you send me privately your .config
file ?

  
yes, now works. 
My err was not recompiling the kernel too.

sorry for the noise.

___
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)

2006-03-29 Thread Gilles Chanteperdrix 
Jim Cromie wrote:
 > Gilles Chanteperdrix wrote:
 > > 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.
 > >
 > >   
 > 807 didnt fix it here.  Its also still present in 815

Reverting 807 produces a bug on my test box identical to the one you are
reporting. Merging 807 again make the bug disappear. Could you double
check ? If the bug persists, could you send me privately your .config
file ?

-- 


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)

2006-03-28 Thread Jim Cromie 

Gilles Chanteperdrix wrote:

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.

  

807 didnt fix it here.  Its also still present in 815

___
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)

2006-03-27 Thread Gilles Chanteperdrix 
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)

2006-03-27 Thread Gilles Chanteperdrix 
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)

2006-03-27 Thread Gilles Chanteperdrix 
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)

2006-03-27 Thread Jim Cromie 

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: