All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Gowtham Garimella <ggarime1@jhu.edu>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] xenomai latency test hangs due to kernel paging request
Date: Tue, 14 Jul 2015 05:54:33 +0200	[thread overview]
Message-ID: <20150714035433.GC1971@hermes.click-hack.org> (raw)
In-Reply-To: <CO1PR01MB256AC4CE16186B5C49AEABD949B0@CO1PR01MB256.prod.exchangelabs.com>

On Tue, Jul 14, 2015 at 12:57:10AM +0000, Gowtham Garimella wrote:
>   
> Hi Everyone,
> 
> I have installed xenomai 2.6.4 on ubuntu 14.04 with the latest
> kernel  3.14.17.

3.14.17 is not the latest kernel. As explained in the documentation,
you can use later patches in the I-pipe download area for the same
kernel version number. So, the "latest kernel" would be
https://xenomai.org//downloads/ipipe/v3.x/x86/ipipe-core-3.14.44-x86-9.patch

Unfortunately that patch has an issue on x86, so I would recommend
using that one instead:
https://xenomai.org//downloads/ipipe/v3.x/x86/older/ipipe-core-3.14.39-x86-9.patch


>  My hardware is a NUC i5 computer (NUC5i5MYHE
> model) with x86 architecture 64 bit computer. I am able  to
> successfully install xenomai and am able to reboot the system 
> normally. I checked that Xenomai is enabled correctly  as seen in
> /var/log/syslog
> 
> The issue I am facing is that, when I run xeno latency it hangs
> and does  not print any latencies. I have seen some posts before
> on similar  issues but they did not help much.

Well, I doubt someone with similar issues did not get an answer.
Could you point us to the posts you are talking about?


>  I enabled ipipe
> tracing and am  attaching the trace. The main part of the log
> files  that  I think is the issue is these lines:
> 
> 
> [  643.881016] BUG: unable to handle kernel paging request at 00007fff0d573ea0
> [  643.881049] IP: [<ffffffff8163c181>] rthal_strncpy_from_user+0x11/0x30
> [  643.881077] PGD 3f78f8067 PUD 3e5e37067 PMD 3ff7b5067 PTE 80000003cf16c067
> [  643.881108] Oops: 0001 [#1] SMP
> [  643.881124] Modules linked in: x86_pkg_temp_thermal i915
> drm_kms_helper

Actually, you do not really need the I-pipe tracer. The kernel logs
would be sufficient. And please, post the full logs, from the boot,
up to the bug itself.

-- 
					    Gilles.
https://click-hack.org


  reply	other threads:[~2015-07-14  3:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14  0:57 [Xenomai] xenomai latency test hangs due to kernel paging request Gowtham Garimella
2015-07-14  3:54 ` Gilles Chanteperdrix [this message]
2015-07-14  3:58 ` Gilles Chanteperdrix
2015-07-14  4:33   ` Gilles Chanteperdrix
2015-07-14  7:28 ` Jan Kiszka
2015-07-14  7:36   ` Gilles Chanteperdrix
2015-07-14  8:05     ` Jan Kiszka
2015-07-14 17:08       ` Gowtham Garimella

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=20150714035433.GC1971@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=ggarime1@jhu.edu \
    --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.