From: Jan Kiszka <jan.kiszka@siemens.com>
To: Manuel Huber <manuel.h87@gmail.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] (Boot)-problems with (current) ipipe patch on AMD FX 61000 - 2.6.38.8 & 3.5.7
Date: Tue, 19 Feb 2013 13:12:16 +0100 [thread overview]
Message-ID: <51236C20.5020906@siemens.com> (raw)
In-Reply-To: <51236A75.5090400@siemens.com>
On 2013-02-19 13:05, Jan Kiszka wrote:
> On 2013-02-19 12:22, Manuel Huber wrote:
>> Thanks for your reply and sorry for the delay ;)
>> I have tried disabling the options and attached the logs. It still fails :(
>>
>> I hope it's okay to attach so many files... I can also add the config
>> files for
>> every build if that helps.
>
> I'll try your config later, though in a different environment. If I'm
> unable to reproduce, I'll provide further instrumentation suggestions.
>
> Gilles instrumentation confirmed that the CPU is taking a standard
> external IRQ (#23: 0x37-FIRST_EXTERNAL_VECTOR).
Wrong, it's IRQ #7: 0x37-IRQ0_VECTOR.
BTW, do you get spurious events on that IRQ line? Check your kernel log
while running a normal kernel for a while. Also have a look at
/proc/interrupts, if there are entries for #7.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-02-19 12:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 12:05 [Xenomai] (Boot)-problems with (current) ipipe patch on AMD FX 61000 - 2.6.38.8 & 3.5.7 Manuel Huber
2013-02-14 20:13 ` Gilles Chanteperdrix
2013-02-19 11:13 ` Manuel Huber
2013-02-19 12:02 ` Gilles Chanteperdrix
2013-02-15 6:55 ` Jan Kiszka
2013-02-19 11:22 ` Manuel Huber
2013-02-19 12:05 ` Jan Kiszka
2013-02-19 12:07 ` Gilles Chanteperdrix
2013-02-19 12:22 ` Jan Kiszka
2013-02-19 12:30 ` Gilles Chanteperdrix
2013-02-19 12:40 ` Jan Kiszka
2013-02-19 12:12 ` Jan Kiszka [this message]
2013-02-19 18:48 ` Jan Kiszka
2013-02-19 18:52 ` Gilles Chanteperdrix
2013-02-19 19:05 ` Jan Kiszka
2013-02-20 20:42 ` Manuel Huber
2013-02-19 20:17 ` Jan Kiszka
2013-02-22 13:54 ` Manuel Huber
2013-02-22 14:06 ` Jan Kiszka
2013-02-25 17:08 ` Jan Kiszka
2013-02-25 19:07 ` Anders Blomdell
2013-02-25 19:10 ` Jan Kiszka
2013-02-25 20:09 ` Anders Blomdell
2013-02-25 22:02 ` Jan Kiszka
2013-02-26 15:57 ` Anders Blomdell
2013-02-26 15:58 ` Jan Kiszka
[not found] ` <512F92C3.1070003@control.lth.se>
2013-02-28 17:30 ` Jan Kiszka
2013-03-11 8:34 ` Anders Blomdell
2013-03-01 11:15 ` Manuel Huber
2013-03-01 13:48 ` Jan Kiszka
2013-04-09 22:09 ` Gilles Chanteperdrix
2013-04-10 7:02 ` Jan Kiszka
2013-04-10 7:05 ` Gilles Chanteperdrix
2013-04-10 7:09 ` Jan Kiszka
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=51236C20.5020906@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=manuel.h87@gmail.com \
--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.