-- > > [...] > > > > > CONFIG_INTERRUPT_OFF_HIST=y > > > CONFIG_CRITICAL_LATENCY_HIST=y > > > CONFIG_LATENCY_HIST=y > > > > Turn off all histograms. They will kill any measurements you are taking. > > And yes, you will not get the output from latency_trace that you are > > after. > > Steven and Daniel, I tried your suggestion with the following resulsts: > CRITICAL_IRQSOFF_TIMING: preempt_max_latency remains 0 even under load, > cyclictest -b is able to store a trace in /proc/latency_trace > CRITICAL_PREEMPT_TIMING: kernel won´t start at all (vmlinuz is read from tftp server but nothing afterwards) > WAKEUP_TIMING: is working as expected. > > So switching off the histograms is an improvement. For the moment, I can live with this situation > (especially the cyclictest -b option is very useful), > but I wonder if anyone else has the same problems? critcal irqs off timings wont start with wakeup timing on. You need to disable that. But that you can do from the command line. echo 0 > /proc/sys/kernel/wakeup_timing -- Steve - To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
