From: Jan Kiszka <jan.kiszka@domain.hid>
To: Steve Kreyer <steve.kreyer@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Timer problems?
Date: Sun, 27 Aug 2006 12:38:14 +0200 [thread overview]
Message-ID: <44F17616.9080701@domain.hid> (raw)
In-Reply-To: <44F0B06B.6050102@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2758 bytes --]
Steve Kreyer wrote:
> 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
Any particular reason to use 2.6.15? Though this should not be the
problem here, it's generally better to use a patch that comes with the
particular Xenomai version - it gained a better test coverage.
>
>> hardware description (e.g. the architecture),
> It is a x86 system, Pentium 4 (~ 3 years old)
...but you have configured your processor to be from the pre-Pentium era
(CONFIG_M586). Suboptimal because TSC support is disabled, TSC emulation
is enabled.
Moreover, and that's likely another reason for troubles here, you have
CONFIG_VT on. This normally unproblematic features collides with the TSC
emulation of Xenomai. SVN head warns you about this conflict, 2.2 not
yet. Solution: pick a more appropriate processor type.
> 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
There are a two more suboptimal (but unproblematic settings):
o CONFIG_SMP: unless your system can be enhanced with more CPUs, switch
it off
o CONFIG_XENO_OPT_TIMING_PERIODIC: this is only required, if you
actually need periodic timer mode (instead of one-shot mode)
And, again, I would take the chance when recompiling anyway to upgrade
the kernel version.
HTH,
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-08-27 10:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 14:42 [Xenomai-help] Problems with rt_task_wait_period Steve Kreyer
2006-08-07 15:27 ` Jan Kiszka
2006-08-07 15:32 ` Philippe Gerum
2006-08-25 15:31 ` [Xenomai-help] Timer problems? Steve Kreyer
2006-08-25 17:47 ` Jan Kiszka
2006-08-26 20:34 ` Steve Kreyer
2006-08-27 10:38 ` Jan Kiszka [this message]
2006-08-27 12:08 ` Philippe Gerum
2006-08-27 12:24 ` Bernhard Walle
2006-08-28 14:46 ` Philippe Gerum
2006-08-27 12:34 ` Gilles Chanteperdrix
2006-08-27 13:02 ` Philippe Gerum
2006-08-27 13:56 ` Jan Kiszka
2006-08-27 13:47 ` Steve Kreyer
2006-08-27 14:22 ` Philippe Gerum
2006-08-27 14:25 ` Philippe Gerum
2006-08-27 14:45 ` Steve Kreyer
[not found] ` <44F196A0.2030006@domain.hid>
2006-08-27 13:00 ` Steve Kreyer
2006-08-25 17:57 ` [Xenomai-help] " Bernhard Walle
2006-08-26 21:23 ` Steve Kreyer
2006-08-26 21:38 ` Bernhard Walle
2006-08-26 22:12 ` Philippe Gerum
2006-08-27 9:21 ` Steve Kreyer
2006-08-27 9:34 ` Philippe Gerum
2006-08-27 10:31 ` Gilles Chanteperdrix
2006-08-27 9:27 ` Steve Kreyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44F17616.9080701@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=steve.kreyer@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.