> From: Ingo Molnar
> there seem to be leaked preempt counts:
>
> <idle>-0 0.n.1 8974us : touch_critical_timing (cpu_idle)
>
> we should never have preemption disabled in cpu_idle(). To
> debug leaked
> preemption counts, enable CONFIG_DEBUG_PREEMPT.
I enabled CONFIG_DEBUG_PREEMPT.
I still have that latency trace in <idle>-0 with that line at the end.
In fact, it is the most common trace on this system:
I always get that trace immediately after resetting the latency
tracer, always close to 9 ms (until an even longer latency happens).
Moreover, I looked up the address shown in asm_do_IRQ in the second
line of all those traces.
<idle>-0 0D..1 1us!: touch_critical_timing (default_idle)
<idle>-0 0D..2 8841us+: asm_do_IRQ (c021da44 1a 0)
It is always the same address, and it is in "cpu_idle".
However, CONFIG_DEBUG_PREEMPT remains silent: No bugs, no warns,
just plain nothing in the syslog.
--
Klaus Kusche (Software Development - Control Systems)
KEBA AG Gewerbepark Urfahr, A-4041 Linz, Austria (Europe)
Tel: +43 / 732 / 7090-3120 Fax: +43 / 732 / 7090-6301
E-Mail: [email protected] WWW: www.keba.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
