Re: 2.6.17-rc1-mm3: time-i386-clocksource-drivers*.patch brokeuserspace apps

[john stultz]

On Sun, 2006-04-30 at 14:59 +0200, Laurent Riffard wrote:
> Since 2.6.17-rc1-mm3, some applications behave strangely here:
> - video players (mplayer, vlc) are randomly frozen after less than 1
> minute playing . They are killable by ^C.
> - some network java application (freenet-0.7) quit after a few
> minutes running.
> 
> A bissection point out time-i386-clocksource-drivers.patch as the
> sucker.

Thanks for narrowing this down!


> I noticed that, since 2.6.17-rc1-mm3, pit clocksource is installed
> instead of acpi_pm clocksource. Booting with "clocksource=acpi_pm"
> does not help.
> 
> [root@antares ~]# grep clocksource dmesg-2.6.17-rc*
> dmesg-2.6.17-rc1-mm1:Time: tsc clocksource has been installed.
> dmesg-2.6.17-rc1-mm1:Time: acpi_pm clocksource has been installed.
> dmesg-2.6.17-rc1-mm2:Time: tsc clocksource has been installed.
> dmesg-2.6.17-rc1-mm2:Time: acpi_pm clocksource has been installed.
> dmesg-2.6.17-rc1-mm3:Time: tsc clocksource has been installed.
> dmesg-2.6.17-rc1-mm3:Time: pit clocksource has been installed.
> dmesg-2.6.17-rc2-mm1:Time: tsc clocksource has been installed.
> dmesg-2.6.17-rc2-mm1:Time: pit clocksource has been installed.

Hmmm. I'm not sure why the ACPI PM timer isn't showing up. Your .config
looks good, but I don't see the ACPI PM timer io-port being detected as
I expect.

Len, has there been any changes to that ACPI code?

> Is pit clocksource broken ? If so, how can I get back acpi_pm
> clocksource ?

I just got another report about the pit clocksource having trouble,
although that was on an SMP system. So its likely there is an issue
there so I'll have to hunt that down.

> Feel free to ask for more information or to send me test patches.

I need to dig on the ACPI issue, but I should be able to have a test
patch for you on the PIT issue early this week.

thanks
-john

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/