Hi Sebastian,
> > > > The kernel version 4.1.37-rt43 is working fine, the kernel
> > > > versions
> > > > 4.4.39-rt50 and
> > > 4.8.11-rt7 show the same strange behavior as 4.9.0-rt1.
> > > > Something on the way between 4.1.37-rt43 and 4.4.39-rt50 seems to
> > > > cause the
> > > trouble.
> > >
> > > can you check if one of the earlier v4.4-RT releases (maybe start
> > > with
> > > -rt2 or -rt1) also shows this behaviour?
> > > If not, would you have a testcase?
> > I tested with 4.4.0-rt2.
> > Here this issue occurs very rarely. I ran the gdb for about 30 times,
> > and here I got one hit.
> > With the other kernel versions I got the issue in 20-40% of the cases.
> >
> > I will try out the other 4.4.0 releases...
>
> I ran more tests. The kernel 4.4.1-rt4 is working fairly fine (only about one hit every
> 30 runs) but the kernel 4.4.1-rt5 is causing the issue very often.
>
Update:
I removed the patch "kernel-perf-mark-perf_cpu_context-s-timer-as-irqsafe.patch" from the 4.4.1-rt5 series.
This improved the situation. No I got the issue about in 5-10% of the runs.
With 4.9.4-rt2 I tried to remove the same assignment (as part of this very patch) in kernel/events/core.c:
timer->irqsafe = 1;
However this did not show any major improvement...
It looks as this not the issue alone. However it might be an indication where the issue is caused from.
Regards
Mathias
��.n��������+%������w��{.n�����{�����ǫ���ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
