Re: NOHZ: local_softirq_pending

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Iratxo,

please do not top post.

On Sun, 14 Jun 2009, Iratxo Pichel Ortiz wrote:

> > I am using 2.6.30-rt16 RT Kernel on a IXP425 system. The system is running

  2.6.29-rt16, right ?

> > an experimental comm stack that has been working quite well with 2.6.26-rt2
> > for a very long time (> 100days).
> >
> > When the system boots, every 180s aprox, I see this traces in the dmesg:
> > 42949422.930000] NOHZ: local_softirq_pending 02

Hmm, so something is marking the timer softirq pending, but does not
wake the timer softirq.

> > [42949422.940000] NOHZ: local_softirq_pending 02
> > [42949422.950000] NOHZ: local_softirq_pending 02
> > [42949422.960000] ISR HIHG LATENCY 30073
> > [42949596.920000] NOHZ: local_softirq_pending 02
> > [42949596.930000] NOHZ: local_softirq_pending 02
> > [42949596.940000] NOHZ: local_softirq_pending 02
> > [42949596.950000] NOHZ: local_softirq_pending 02

So this repeats itself roughly every 3min and stays that way for a
couple of jiffies. Does your code fiddle with timers ?

> > [42949596.960000] ISR HIHG LATENCY 40066

The latency is exaclty the number of NOHZ messages * 10ms. I assume
you have HZ=100. Looks like your code is waiting for a timer, which
does not fire due to the local_softirq_pending 02 problem.

Does it work when you disable CONFIG_NOHZ ?

Thanks,

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

[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux