[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20061004011544.d49308de.akpm@osdl.org>
Date: Wed, 4 Oct 2006 01:15:44 -0700
From: Andrew Morton <akpm@...l.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>, Jim Gettys <jg@...top.org>,
John Stultz <johnstul@...ibm.com>,
David Woodhouse <dwmw2@...radead.org>,
Arjan van de Ven <arjan@...radead.org>,
Dave Jones <davej@...hat.com>
Subject: Re: [patch] clockevents: drivers for i386, fix #2
On Wed, 4 Oct 2006 09:55:40 +0200
Ingo Molnar <mingo@...e.hu> wrote:
>
> * Andrew Morton <akpm@...l.org> wrote:
>
> > None of the interrupts are doing anything wrong. oprofile shows
> > nothing alarming.
> >
> > Disabling cpufreq in config doesn't fix it.
> >
> > Userspace can count to a billion in 3.9 seconds when this problem is
> > present, which is the same time as it takes on a non-slow kernel.
> >
> > `sleep 5' takes 5 seconds.
> >
> > Yet initscripts take a long time (especially applying the ipfilter
> > firewall rues for some reason), and `startx' takes a long time, etc.
> > This kernel takes 112 seconds to boot to a login prompt - other
> > kernels take 56 seconds (interesting ratio..)
>
> hm, do you have the NMI watchdog enabled by any chance? [in particular,
> do you have nmi_watchdog=2?] Although your bootlog does not show it.
>
There's no nmi_watchdog setting in the kernel boot command line and the
NMI counter isn't incrementing.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists