Re: [patch 00/22] high resolution timers / dynamic ticks - V3

[Andrew Morton <akpm@osdl.org>]

On Thu, 5 Oct 2006 10:23:48 +0200
Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Andrew Morton <akpm@osdl.org> wrote:
> 
> > It just did something:
> > 
> > [   12.112000] kjournald starting.  Commit interval 5 seconds
> > [   12.160000] EXT3-fs: recovery complete.
> > [   12.164000] EXT3-fs: mounted filesystem with ordered data mode.
> > [   12.980000] audit(1160010604.980:2): enforcing=1 old_enforcing=0 auid=4294967295
> > [   18.808000] security:  3 users, 6 roles, 1417 types, 151 bools, 1 sens, 256 cats
> > [   18.812000] security:  57 classes, 41080 rules
> > [   18.816000] SELinux:  Completing initialization.
> > [   18.816000] SELinux:  Setting up existing superblocks.
> > [   18.824000] SELinux: initialized (dev sda6, type ext3), uses xattr
> > [   18.860000] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
> > 
> > 
> > Those "six seconds" took at least three minutes.  With luck I'll have 
> > a login prompt tomorrow morning.
> 
> as per your previous stats, the ratio between expected and real local 
> APIC timer IRQs is 3:250. So if your normal bootup takes 1 minute, you 
> should be up and running in an hour or so :-/
> 
> you should be seeing similar symptoms when booting the x86 SMP kernel on 
> that box. Or is the anomalously slow LOC count only an artifact of the 
> hres tree?
> 

The stock kernel shows a local-apic interrupt rate of 18Hz (HZ=250).  Other
times I've seen 13Hz.

With this patch series applied, disabling the local apic in config fixes
things up (using the PIT).

With the stock kernel and SMP, the system is slow, but not _as_ slow. 
Bootup takes maybe twice as long, but not all week.  This time the local
APIC interrupt rate is 8Hz, so something peculiar is happening here -
nothing is proportional.

It'd be nice to fix the local apic rather than working around it.  Any idea
why it's doing this?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/