https://bugzilla.kernel.org/show_bug.cgi?id=19702 --- Comment #30 from Thomas Renninger <trenn@xxxxxxx> 2010-10-29 12:14:38 --- Thanks. I still think not considering core dependencies in HW_ALL case is wrong, but this needs further/separate discussing/evaluation. Peter, as you said with exactly same HW and kernel version/.config: This one is broken: Intel Core2 Duo T7300 2.0 GHz processor and this one is not: Intel Core2 Quad Q9550 Could you show us: cat /sys/devices/system/clocksource/clocksource0/available_clocksource and cat /sys/devices/system/clocksource/clocksource0/current_clocksource does it make a difference switching, e.g. to hpet? echo xy >/sys/devices/system/clocksource/clocksource0/current_clocksource Ok, I checked Heinz's and Peter's dmesg: Heinz explicitly enables hpet via boot param (what is this for?) clocksource=hpet acpi_skip_timer_override And Peter has: Marking TSC unstable due to TSC halts in idle Switching to clocksource hpet It's always only CPU0 not switching up, right? Looks like something with hpet is wrong. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
