[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070325101548.GI24225@mellanox.co.il>
Date: Sun, 25 Mar 2007 12:15:48 +0200
From: "Michael S. Tsirkin" <mst@....mellanox.co.il>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: "Michael S. Tsirkin" <mst@....mellanox.co.il>,
Adrian Bunk <bunk@...sta.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Soeren Sonnenburg <kernel@....de>, Ingo Molnar <mingo@...e.hu>,
Tejun Heo <htejun@...il.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
John Stultz <johnstul@...ibm.com>
Subject: Re: [4/5] 2.6.21-rc4: known regressions (v2)
> Quoting Thomas Gleixner <tglx@...utronix.de>:
> Subject: Re: [4/5] 2.6.21-rc4: known regressions (v2)
>
> On Sun, 2007-03-25 at 10:57 +0200, Michael S. Tsirkin wrote:
> > > Can you please test the following:
> > >
> > > Add "clocksource=acpi_pm" to the kernel commandline.
> > >
> > > If this does not change anything, then disable CONFIG_HPET and retry.
> >
> > I have:
> > $ grep CONFIG_HPET .config
> > CONFIG_HPET_TIMER=y
> > CONFIG_HPET_EMULATE_RTC=y
> > # CONFIG_HPET is not set
> >
> > so I think all these tests were done with CONFIG_HPET=n.
>
> Gack. Please turn off CONFIG_HPET_TIMER and CONFIG_HPET_EMULATE_RTC
Okay ... although they are in defconfig for i386, and they did not create
problems in 2.6.20.
> > Given this, does it still make sense to test clocksource=acpi_pm?
>
> Yes.
With or without CONFIG_HPET_TIMER?
--
MST
-
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