[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1197056910.32023.25.camel@cmn3.stanford.edu>
Date: Fri, 07 Dec 2007 11:48:30 -0800
From: Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU>
To: Ingo Molnar <mingo@...e.hu>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>, Len Brown <lenb@...nel.org>,
Venki Pallipadi <venkatesh.pallipadi@...el.com>
Subject: Re: [git pull] x86/hrtimer/acpi fixes
On Fri, 2007-12-07 at 11:29 -0800, Fernando Lopez-Lezcano wrote:
> On Fri, 2007-12-07 at 19:59 +0100, Ingo Molnar wrote:
> > * Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU> wrote:
> >
> > > Ingo, I was about to post about timer problems in 2.6.23.9+rt12 when I
> > > saw this. Would this be related / should I test / will this solve
> > > everything? :-)
> > >
> > > What I'm seeing is jack "delays" that go away if I boot with
> > > "idle=poll", just like it was happening a long time ago. Smells like
> > > 'time of day' glitches when the process switches cpus (this is on a
> > > dual core intel laptop).
> >
> > does it go away with hpet=disable as well? If yes then there could be a
> > relation. If not then it's something else and we need to debug it.
>
> Nope, it doesn't still getting "delay" and "xrun" messages galore.
Attached: configuration and dmesg output booting with idle=poll,
reconfirmed that that makes the delay and xrun messages go away.
-- Fernando
View attachment "dmesg.2" of type "text/plain" (27146 bytes)
View attachment "config-2.6.23.9-1.rt12.2.fc7.ccrmart" of type "text/plain" (80369 bytes)
Powered by blists - more mailing lists