From: Jan Kiszka <jan.kiszka@domain.hid>
To: Stelian Pop <stelian@domain.hid>,
rpm@xenomai.org, Xenomai-core@domain.hid
Subject: Re: [Xenomai-core] [PATCH] fix hw-timer setup/cleanup for i386
Date: Sat, 13 Oct 2007 18:38:30 +0200 [thread overview]
Message-ID: <4710F486.40403@domain.hid> (raw)
In-Reply-To: <20071013161211.GB24909@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
Stelian Pop wrote:
> On Sat, Oct 13, 2007 at 04:42:27PM +0200, Jan Kiszka wrote:
>
>> Where do you get ENODEV? On nucleus startup? Please provide
>> /proc/timer_list output of the working and non-working setups.
>
> It turns out that I had the Linux NMI watchdog enabled (nmi_watchdog=1
> on the command line) and this was causing the -ENODEV problems. Once
> removed, I'm able to boot and successfully run all configurations: UP,
> UP + APIC, UP + APIC + IO_APIC, SMP. And the latencies are back to normal.
>
> Maybe we should detect that the NMI watchdog is enabled and issue a
> warning message, this would save others a few hours and many kernel
> builds...
NMI is still broken for >= 2.6.22, known issue :-/. The problem is that
Linux falls back to the PIT, leaving our beloved APIC in disabled state
which makes Xenomai fail when asking for it. $Someone has to look into
the reason why we cannot take over the APIC in that scenario...
>
> This is with your timer cleanup patch, of course.
>
>> PS: For unknown reasons your mails don't make it to my web.de address,
>> only to the list. Do you get any error messages?
>
> I did get one saying:
> <jan.kiszka@domain.hid>: host mx-ha02.web.de[217.72.192.188] refused to talk to me:
> 554 Transaction failed. For explanation visit
> http://freemail.web.de/reject/?ip=88.191.70.230
>
> I didn't investigate yet what's happenning.
>
Your IP is probably associated to some DSL access, and a lot of
providers block such senders categorically due to all the spam robots
running on hijacked user PCs.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-10-13 16:38 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
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 [this message]
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=4710F486.40403@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Xenomai-core@domain.hid \
--cc=rpm@xenomai.org \
--cc=stelian@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.