From: Stelian Pop <stelian@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: Xenomai-core@domain.hid
Subject: Re: [Xenomai-core] [PATCH] fix hw-timer setup/cleanup for i386
Date: Fri, 12 Oct 2007 10:58:44 +0200 [thread overview]
Message-ID: <1192179524.5149.23.camel@domain.hid> (raw)
In-Reply-To: <470E8BFE.4070804@domain.hid>
Hi Jan,
[taking this on the list after several mails with Philippe...]
Le jeudi 11 octobre 2007 à 22:47 +0200, Jan Kiszka a écrit :
> This patch for SVN trunk fixes most of the current bugs around hardware
> timer takeover and release from/to Linux.
[...]
I have a problem with the timer on my MacBook Pro (Core2Duo, used in
_32_ bit mode)(*): when Xenomai takes over the timer (at 'modprobe
xeno_native' time), the Linux timer stops.
Looking into /proc/xenomai/irq shows that Xenomai does receive the
hardware interrupts, and /proc/interrupts shows that they are no longer
forwarded to Linux. Before loading xeno_native, everything is ok.
Linux userspace continues to somewhat work: I can issue commands, and
depending on the syscalls they made I suppose (no, strace doesn't work),
sometimes they end correctly sometimes they hang (and I cannot interrupt
them by ^C or other signals.).
I tried several .config variations, without any change in behaviour: my
current test config has SMP, NO_HZ, APIC, PREEMPT, HIRES all disabled).
This happens with a 2.6.22.9 kernel, adeos-ipipe-2.6.22-i386-1.10-07,
xenomai svn HEAD (rev 3050), with or without your current patch. It is
quite possible that this is not a new problem, since I have this laptop
since a few weeks only and I never ran Xenomai on it.
I'll happily provide any further information or test results if you
need.
Thanks,
Stelian.
(*) yeah, I know I could install a x86_64 distribution but I had some
terrible experiences in the past - mainly due to the usage of some
proprietary bricks like flash, java etc. I know some of those have been
resolved today, and one of these days I should try once more, but now it
is not a good time for this.
--
Stelian Pop <stelian@domain.hid>
next prev parent reply other threads:[~2007-10-12 8:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 20:47 [Xenomai-core] [PATCH] fix hw-timer setup/cleanup for i386 Jan Kiszka
2007-10-12 8:58 ` Stelian Pop [this message]
2007-10-12 9:14 ` Jan Kiszka
2007-10-12 11:00 ` Stelian Pop
2007-10-12 11:15 ` Jan Kiszka
2007-10-12 13:19 ` Stelian Pop
2007-10-12 13:39 ` Jan Kiszka
2007-10-12 13:41 ` Philippe Gerum
2007-10-12 14:26 ` Stelian Pop
2007-10-12 19:53 ` Jan Kiszka
2007-10-12 20:22 ` Stelian Pop
2007-10-12 21:51 ` Stelian Pop
2007-10-12 21:58 ` Philippe Gerum
2007-10-13 14:28 ` Stelian Pop
2007-10-13 14:42 ` Jan Kiszka
2007-10-13 16:12 ` Stelian Pop
2007-10-13 16:35 ` Philippe Gerum
2007-10-13 16:38 ` Jan Kiszka
2007-10-13 20:55 ` Stelian Pop
2007-10-13 14:32 ` Stelian Pop
2007-10-12 9:00 ` Jan Kiszka
2007-10-12 9:16 ` Philippe Gerum
2007-10-12 9:47 ` Jan Kiszka
2007-10-12 12:48 ` Philippe Gerum
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=1192179524.5149.23.camel@domain.hid \
--to=stelian@domain.hid \
--cc=Xenomai-core@domain.hid \
--cc=jan.kiszka@domain.hid \
/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.