On Wed, 2011-06-22 at 19:16 +0200, Gilles Chanteperdrix wrote:
> On 05/19/2011 10:29 PM, Philippe Gerum wrote:
> > On Thu, 2011-05-19 at 20:36 +0200, Jan Kiszka wrote:
> >> On 2011-05-19 20:15, Gilles Chanteperdrix wrote:
> >>> On 05/19/2011 03:58 PM, Philippe Gerum wrote:
> For this reason, I
On 05/19/2011 10:29 PM, Philippe Gerum wrote:
> On Thu, 2011-05-19 at 20:36 +0200, Jan Kiszka wrote:
>> On 2011-05-19 20:15, Gilles Chanteperdrix wrote:
>>> On 05/19/2011 03:58 PM, Philippe Gerum wrote:
For this reason, I'm considering issuing a patch for a complete removal
of the NMI lat
On Thu, 2011-05-19 at 20:36 +0200, Jan Kiszka wrote:
> On 2011-05-19 20:15, Gilles Chanteperdrix wrote:
> > On 05/19/2011 03:58 PM, Philippe Gerum wrote:
> >> For this reason, I'm considering issuing a patch for a complete removal
> >> of the NMI latency watchdog code in Xenomai 2.6.x, disabling th
On 2011-05-19 20:15, Gilles Chanteperdrix wrote:
> On 05/19/2011 03:58 PM, Philippe Gerum wrote:
>> For this reason, I'm considering issuing a patch for a complete removal
>> of the NMI latency watchdog code in Xenomai 2.6.x, disabling the feature
>> for 2.6.38 kernels and above in 2.5.x.
>>
>> Com
On 05/19/2011 03:58 PM, Philippe Gerum wrote:
> For this reason, I'm considering issuing a patch for a complete removal
> of the NMI latency watchdog code in Xenomai 2.6.x, disabling the feature
> for 2.6.38 kernels and above in 2.5.x.
>
> Comments welcome.
I am in the same case as you: I no long
The NMI latency watchdog is a feature Xenomai supports when proper
hardware is available, which triggers a stack backtrace dump, then
panics when a real-time timer tick is late by a given amount of time. We
used it in the early times to chase pathological latencies, particularly
when debugging the
