ºÜ¶àÏñÎÒÒ»Ñùϲ»¶»»OSµÄͬѧ¿Ï¶¨¶ÔÕâ¸ö²»Ä°ÉúÁË£¬ÌرðÊÇamd+ati×éºÏµÄÈ˾³£Åöµ½¡£archlinux,ubuntu,fedora,debianµÈ£¬Ò»Ð©°æ±¾ÔÚ°²×°µÄʱºò¾Í¿¨ÔÚÕâ¸öµØ·½²»¶¯ÁË¡£ÓÐЩ¡°¸ßÊÖ¡±»áÖ¸µ¼ÄãÔÚkernelÕâÒ»ÐмÓÉÏ¡°acpi=off" ¾Í¿ÉÒÔ¼ÌÐøÁË¡£µ«ÊÇ£¬²»¾ÃÄã»á·¢ÏÖ¡£×Ô¼ºµÄµçÄÔ²»ÄÜÏñwinÄÇÑù¹Ø»úÁË¡£Ó²Å̲»¶¯ÁË£¬¿ÉµçÔ´»¹ÔÚÏì×ÅÄØ¡£
ºÇºÇ£¬ÎªÊ²Ã´ÄØ£¿Ï±߸øÄã¶ÎEÎÄ£ºThe tsc clock source keeps getting marked unstable and falls back to using acpi_pm on kernel 2.6.21.3. This is directly linked to using cpu frequencing scaling. If I leave default governer as performace is fine, second I set to ondemand or anything the changes the current frequency the unstable msg appears.
¿´¶®ÁËû£¿ÆäʵÎÒҲûÍêÈ«¶®.
ºÃÀ²£¬»¹ÊÇ¿´¿´Ôõô°ì°É£¡
ÏÈ¿´¿´Ä㻹ÓбðµÄ¿ÉÌæ´úƷû£¿
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
ÎÒµÄOS¾ÍÏÔʾÁ˼¸¸ö£º hpet acpi_pm jiffies tsc
È»ºóÔÚgrubµÄkernel ÐÐÖ¸¶¨¸Ã¹ÜÀíÆ÷£ºÒ»°ãÊÇÑ¡Õâ¸ö£º clocksource=acpi_pm
ÊÔÊÔ£¬ÏÖÔÚ²»ÊÇ¿ÉÒÔÀ²£¿