On 3/17/22 4:44 PM, Jan Kiszka wrote:
On 17.03.22 16:24, Scott Reed wrote:
On 3/16/22 11:35 AM, Jan Kiszka wrote:
On 16.03.22 10:58, Scott Reed wrote:
On 3/15/22 9:42 AM, Scott Reed via Xenomai wrote:
On 3/15/22 7:32 AM, Jan Kiszka wrote:
On 14.03.22 18:45, Scott Reed wrote:
On
en to working and non-working 4.14
kernels.
>
I have been able to get my test running on 4.14.110+ipipe without the
system hanging on the first PCIe MSI interrupt. I have attached my
patch (hopefully the attachment shows up correctly, but if not
please let me know).
The f
On 17.03.22 16:24, Scott Reed wrote:
>
>
> On 3/16/22 11:35 AM, Jan Kiszka wrote:
>> On 16.03.22 10:58, Scott Reed wrote:
>>>
>>>
>>> On 3/15/22 9:42 AM, Scott Reed via Xenomai wrote:
On 3/15/22 7:32 AM, Jan Kiszka wrote:
> On 14.03.22 18:45, Scott Reed wrote:
>>
>>
on the first PCIe MSI interrupt.
> >>
> >> As mentioned before, I first observed this behavior when moving from
> >> 4.14.62+ipipe and 4.14.110+ipipe so I think my best bet is to dive
> >> into what changed in this time frame. My goal is still to move to
>
n-text attachment was scrubbed...
Name: 0001-ipipe-arm-Fix-handling-of-PCIe-MSI-interrupts.patch
Type: text/x-patch
Size: 993 bytes
Desc: not available
URL:
<http://xenomai.org/pipermail/xenomai/attachments/20220317/c81fcb0f/attachment.bin>
Thank you Jan, Philippe. Your responses have given us a lot to look into
and a lot to learn. We'll come back with a more detailed response once
we've gained a little more understanding on our end.
Matt
On Wed, Mar 16, 2022 at 5:09 AM Philippe Gerum wrote:
>
> Matt Klass via Xenomai writes:
>
