From: "Yogi A. Patel" <yapatel@gatech.edu>
To: Jan Kiszka <jan.kiszka@web.de>, xenomai@xenomai.org
Subject: Re: [Xenomai] 3.14.17 patch initial ram disk hangup
Date: Mon, 25 May 2015 09:47:55 -0400 [thread overview]
Message-ID: <5563280B.2040301@gatech.edu> (raw)
In-Reply-To: <55617756.4080307@web.de>
On 05/24/2015 03:01 AM, Jan Kiszka wrote:
> On 2015-05-22 22:47, Yogi A. Patel wrote:
>> Hi -
>>
>> I have a Dell OptiPlex 9020 running 3.14.17. I am trying to get this system to run 3.14.17 with xenomai (using the 3.14.17 patch in the xenomai 2.6.4 source).
>>
>> The computer hangs when I select the kernel at “Loading initial ram disk”. I tried booting into recovery mode and go the following output:
>>
>> Kernel panic - not syncing: timer doesn’t work through Interrupt-remapped IO-APIC.
> Please turn off CONFIG_IRQ_REMAP or boot the kernel with intremap=off.
> This feature is not yet compatible with I-pipe. I guess we should encode
> this into the x86 patch.
>
> Jan
>
>> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.17-xenomai-2.6.4.
>>
>> I’m having a hard time finding the source of the error. I’ve attached my config file. Any suggestions appreciated!
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: config
>> Type: application/octet-stream
>> Size: 163773 bytes
>> Desc: not available
>> URL: <http://xenomai.org/pipermail/xenomai/attachments/20150522/c24951de/attachment.obj>
>> -------------- next part --------------
>>
>> Yogi
>>
>> _______________________________________________
>> Xenomai mailing list
>> Xenomai@xenomai.org
>> http://xenomai.org/mailman/listinfo/xenomai
>>
>
I tried Jan's suggestion and it works with the 3.14.17-x84-6 ipipe patch
- I can boot in get to a desktop/etc. However, the latencies are all
over the place. I am seeing worst-case latencies anywhere between 2us-50us.
I tried Gilles' suggestion, too - and compiled with 3.14.17-x86-9 ipipe
patch. Same thing as above.
I read around online about interrupt remapping - and I can't seem to
find anything that hints at why this turning it off would cause the
latencies to be all over the place.
Any thoughts/guidance appreciated!
Yogi
next prev parent reply other threads:[~2015-05-25 13:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 20:47 [Xenomai] 3.14.17 patch initial ram disk hangup Yogi A. Patel
2015-05-22 21:05 ` Gilles Chanteperdrix
2015-05-22 21:22 ` Yogi A. Patel
2015-05-22 21:37 ` Yogi A. Patel
2015-05-22 21:52 ` Gilles Chanteperdrix
2015-05-22 22:00 ` Yogi A. Patel
2015-05-22 22:26 ` Gilles Chanteperdrix
2015-05-23 18:14 ` Yogi A. Patel
2015-05-23 18:26 ` Gilles Chanteperdrix
2015-05-23 20:32 ` Yogi A. Patel
2015-05-24 6:51 ` Gilles Chanteperdrix
2015-05-24 7:01 ` Jan Kiszka
2015-05-25 13:47 ` Yogi A. Patel [this message]
2015-05-25 14:23 ` Jeroen Van den Keybus
2015-05-25 15:06 ` Yogi A. Patel
2015-05-25 15:22 ` Gilles Chanteperdrix
2015-05-25 16:01 ` Jeroen Van den Keybus
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=5563280B.2040301@gatech.edu \
--to=yapatel@gatech.edu \
--cc=jan.kiszka@web.de \
--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.