All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Manuel Huber <manuel.h87@gmail.com>,
	"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:40:34 +0100	[thread overview]
Message-ID: <512372C2.9000203@siemens.com> (raw)
In-Reply-To: <51237077.4040800@xenomai.org>

On 2013-02-19 13:30, Gilles Chanteperdrix wrote:
> On 02/19/2013 01:22 PM, Jan Kiszka wrote:
> 
>> On 2013-02-19 13:07, Gilles Chanteperdrix wrote:
>>> On 02/19/2013 01:05 PM, 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). I suspect we are
>>>> enabling hardware IRQs too early during the boot of secondary CPUs,
>>>> causing this BUG as not all data structures are initialized yet. What
>>>> enables then can be some code that we do not run normally, on x86-64 or
>>>> maybe also x86-32 unless using your .config and/or your hardware.
>>>
>>>
>>> Remember that we have had such problems with grub2, so, the error could
>>> depend on the bootloader, for instance a network-aware bootloader could
>>> keep the network interface configured and we would take an interrupt
>>> when re-enabling interrupts.
>>
>> Possibly, but I don't see yet how Linux (3.5.7) would behave better in
>> this case. It should rather access the irq_desc array with a negative
>> index. And that suggests there is still an I-pipe factor involved that
>> makes this bug possible (the BUG_ON just catches it).
> 
> 
> Maybe because Linux only unmask the interrupt after request_irq has
> installed a handler?

Does I-pipe do this, specifically that early during boot?

Well, I can try injecting a spurious IRQ7 through QEMU to see what happens.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2013-02-19 12:40 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 [this message]
2013-02-19 12:12       ` Jan Kiszka
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=512372C2.9000203@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.