From: "J.D. Yamokoski" <yamokosk@domain.hid>
To: rpm@xenomai.org
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Problems booting after Adeos patch
Date: Fri, 29 Sep 2006 08:59:30 -0400 [thread overview]
Message-ID: <451D18B2.3060007@domain.hid> (raw)
In-Reply-To: <1159475501.4982.49.camel@domain.hid>
Philippe Gerum wrote:
> On Thu, 2006-09-28 at 22:27 +0200, Philippe Gerum wrote:
>
>> Ok, thanks. Just for the purpose of finding some grip on this issue,
>> could you:
>> 1) apply the patch below; I suspect some unwanted IRQ migration issue,
>> but can't prove it right now.
>> 2) if this patch does not solve the boot problem with CONFIG_PCI_MSI
>> enabled, then does disabling CONFIG_SMP improve the situation?
>>
>> TIA,
>>
>
> Actually, this patch would be better for the purpose of testing.
>
> --- 2.6.17-ipipe/kernel/irq/migration.c.orig 2006-09-28 22:28:20.000000000 +0200
> +++ 2.6.17-ipipe/kernel/irq/migration.c 2006-09-28 22:30:13.000000000 +0200
> @@ -17,6 +17,10 @@
> cpumask_t tmp;
> irq_desc_t *desc = irq_descp(irq);
>
> +#ifdef CONFIG_IPIPE
> + return;
> +#endif /* CONFIG_IPIPE */
> +
> if (likely(!desc->move_irq))
> return;
>
Real quick, does it matter if I was using the Adeos I-pipe patch for
kernel 2.6.15 when I ran into my problems? That patch looks like it is
for 2.6.17 - But I can try either one.
next prev parent reply other threads:[~2006-09-29 12:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 21:36 [Adeos-main] Problems booting after Adeos patch J.D. Yamokoski
2006-09-27 23:30 ` Jan Kiszka
2006-09-28 14:06 ` J.D. Yamokoski
2006-09-28 14:23 ` Jan Kiszka
2006-09-28 14:44 ` Philippe Gerum
2006-09-28 17:08 ` J.D. Yamokoski
2006-09-28 20:27 ` Philippe Gerum
2006-09-28 20:31 ` Philippe Gerum
2006-09-29 12:59 ` J.D. Yamokoski [this message]
2006-09-29 13:44 ` Philippe Gerum
2006-10-02 16:11 ` J.D. Yamokoski
2006-10-14 21:54 ` [Xenomai-core] Adeos + CONFIG_PCI_MSI issue Philippe Gerum
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=451D18B2.3060007@domain.hid \
--to=yamokosk@domain.hid \
--cc=adeos-main@gna.org \
--cc=rpm@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.