From: Jan Kiszka <jan.kiszka@domain.hid>
To: andy motten <andy.motten@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] hard lock-up
Date: Mon, 13 Aug 2007 19:01:21 +0200 [thread overview]
Message-ID: <46C08E61.9060204@domain.hid> (raw)
In-Reply-To: <3535aae80708130810s603edb7fo9f7be56342ddf921@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
andy motten wrote:
>> Klaas Gadeyne wrote:
>>> On Fri, 10 Aug 2007, Jan Kiszka wrote:
>>> [..]
>>>> BTW, given that the SMI workaround is infunctional on your system: Do
>>>> you get reasonable latencies ATM? It looked to me like the NMI
>> watchdog
>>>> might have triggered due to SMI-related delays.
>>> We do get very reasonable latencies once the AGP functionality is
>>> turned off (otherwise, latencies are pathetic). Note that we haven't
>>> sorted out whether the buggy behaviour and huge latencies are due to
>>> the AGP bus in general or too the specific intel_something_els_here
>>> driver.
>> Did you try the "noaccel" option, as explained in the FAQ ?
>>
>
> Yes, but there was no change in performance.
You mean latency?
>
> We have tried several configurations of the system, and we get no hard
> lockups anymore.
> Even the configurations that used to lockup are working now without a
> problem.
>
> Maybe we forget something, but to be honest, we have no idea what triggered
> this change in behavior.
> Thanks for all the help.
> As soon as we know something more about this 'random' behavior, We will post
> it.
And the pathetic latencies might be worth a look using the latency
tracer. Just to be sure it's no software issue. Is there any known
non-broken real-time Linux installation for your board, or did you just
try it out for the first time?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-08-13 17:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 9:11 [Xenomai-help] hard lock-up andy motten
2007-08-09 9:42 ` Gilles Chanteperdrix
2007-08-09 11:24 ` Jan Kiszka
2007-08-09 16:09 ` andy motten
2007-08-09 16:22 ` Philippe Gerum
2007-08-10 7:32 ` Jan Kiszka
2007-08-10 7:54 ` Klaas Gadeyne
2007-08-10 15:05 ` andy motten
2007-08-10 15:12 ` Jan Kiszka
2007-08-13 7:06 ` Klaas Gadeyne
2007-08-13 7:19 ` Gilles Chanteperdrix
2007-08-13 15:10 ` andy motten
2007-08-13 17:01 ` Jan Kiszka [this message]
2007-08-14 15:26 ` andy motten
2007-08-27 13:27 ` andy motten
2007-08-27 16:55 ` Jan Kiszka
2007-08-28 10:06 ` andy motten
2007-08-28 11:32 ` Jan Kiszka
2007-08-29 11:36 ` andy motten
2007-08-29 6:11 ` Jan Kiszka
2007-08-29 13:40 ` andy motten
2007-08-29 14:12 ` Jan Kiszka
2007-08-29 14:23 ` Philippe Gerum
2007-08-29 14:23 ` andy motten
2007-08-09 16:26 ` Gilles Chanteperdrix
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=46C08E61.9060204@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=andy.motten@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.