Re: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)

On Fri, 2005-12-30 at 08:44 +0100, Ingo Molnar wrote:
> 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.

ARM does disable preemption in cpu_idle() . 

Daniel

-
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/

---

• References:
  • Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
    • From: "kus Kusche Klaus" <[email protected]>
  • Re: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
    • From: Lee Revell <[email protected]>
  • Re: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
    • From: Ingo Molnar <[email protected]>

• Prev by Date: Re: PROBLEM: cannot boot 2.6.15-rc6 on Opteron machine
• Next by Date: Re: USB Key Kingston DataTraveler
• Previous by thread: Re: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
• Next by thread: RE: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
• Index(es):
  • Date
  • Thread

[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]