On Tue, Jul 5, 2011 at 10:45 AM, Ronny Meeus <[email protected]> wrote:
> On Mon, Jul 4, 2011 at 10:13 PM, Philippe Gerum <[email protected]> wrote:
>> On Mon, 2011-07-04 at 22:09 +0200, Philippe Gerum wrote:
>>> On Mon, 2011-07-04 at 22:04 +0200, Ronny Meeus wrote:
>>> > On Mon, Jul 4, 2011 at 1:42 PM, Gilles Chanteperdrix
>>> > <[email protected]> wrote:
>>> > > On 07/04/2011 10:20 AM, Philippe Gerum wrote:
>>> > >> Could you try 2.6.36-ipipe as well in case 2.6.35.7 without pipeline
>>> > >> does not exhibit the issue? A number of changes went in the IRQ replay
>>> > >> code during this time frame, and 2.6.35 was in a state of flux 
>>> > >> regarding
>>> > >> this.
>>> > >
>>> > > And please try Xenomai 2.5.6.
>>> > >
>>> > > --
>>> > >                                            Gilles.
>>> > >
>>> >
>>> > Hello
>>> >
>>> > today we tested tested: "Running the same test on 2.6.35.7 without IPIPE".
>>> > The result is also not OK. The problem can be reproduced on this
>>> > kernel, so it looks like the issue has nothing to do with the I-PIPE.
>>> > We are currently porting the FreeScale patches to the 2.6.36 kernel
>>> > but it looks like this is going to take some effort (Thomas already
>>> > spent half a day on it today).
>>> >
>>> > Maybe a bit of history: we started with the 2.6.34 kernel with no SMP.
>>> > Here we observed issue in some scenarios. By playing with the
>>> > configuration we found that these issues were resolved by switching to
>>> > SMP (even on one core).
>>> > After the activation of SMP we started to see BADNESS issues once we
>>> > started to run our Xenomai based applications.
>>> > Thomas found a patch on the Xenomai mailing list to solve the badness
>>> > issue but this was based on 2.6.35.7. We ported the FreeScale patches
>>> > to that releases and we observed the blocking application issue
>>> > described above.
>>> >
>>> > We will try to port the FreeScale patches to 2.6.36 and see how the
>>> > system behaves. More information on this later.
>>> > Can you guys give us any hint of what would be the most stable version
>>> > of Linux + Xenomai to base our application on?
>>>
>>> SMP-wise for powerpc, 2.6.36 + upcoming 2.5.6
>>
>> s,upcoming,,
>>
>> I mean 2.5.6 stock.
>>
>>>
>>> >
>>> > Thanks
>>> > Ronny
>>> >
>>> > _______________________________________________
>>> > Adeos-main mailing list
>>> > [email protected]
>>> > https://mail.gna.org/listinfo/adeos-main
>>>
>>
>> --
>> Philippe.
>>
>>
>>
>
> Hello
>
> we have done the test on both 2.6.36 and 2.6.36.4 without I-PIPE.
> In both cases the issue is seen.
>
> Any hints to helps us debugging this issue would be appreciated.
>
> Best regards
> Ronny
>

Hello

Today we have identified the issue.
In the net/packet/af_packet.c file a spin_lock is used where a
spin_lock_bh should be used. We observed that the spin_lock was
entered recursively: by the application and also from the context of a
softIRQ. Result was a deadlock.

I will post a patch soon on the netdev mailing list.
We will upgrade most probably to 2.6.36.4 and Xenomai 2.5.6 like you
guys suggested.

Thanks for your support.

Best regards,
Ronny

_______________________________________________
Adeos-main mailing list
[email protected]
https://mail.gna.org/listinfo/adeos-main

Reply via email to