Hi Jan,

first of all thanks for your answer.
Jan Kiszka wrote:
Your example (with slight modifications) works fine, and the other
effect you listed here clearly indicates some fundamental problem of
your box. Does the kernel log contain any suspicious messages,
specifically after that input lock-up?
No the kernel log says nothing on this lock...
If not, please provide a precise
setup description: Xenomai version,
cat /proc/xenomai/version
2.2
I have also attached the config.log of the xenomai configuration to this email, if this
could be meaningful to figure out the problem...
 kernel version + ipipe revision,
cat /proc/ipipe/version
1.3-07

uname -a
Linux euklid 2.6.152.6.15 #6 SMP PREEMPT Sun Aug 6 17:02:34 CEST 2006 i686 GNU/Linux

hardware description (e.g. the architecture),
It is a x86 system, Pentium 4 (~ 3 years old)
cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 1
model name      : Intel(R) Pentium(R) 4 CPU 1.60GHz
stepping        : 2
cpu MHz         : 1600.244
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips        : 3207.69

and the .config of your
system (zipped please).
Ok, it is attached...
Jan


Regards,
Steve

Attachment: kernel-config.gz
Description: application/gzip

Attachment: xenomai-config.log.gz
Description: application/gzip

_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help

Reply via email to