As Andriy Gapon wrote: > on 23/04/2010 12:17 Joerg Wunsch said the following: > > dev.cpu.0.freq_levels: 2000/25000 1875/23437 1800/20900 1687/19593 > > 1600/17500 > > 1500/16406 1400/15312 1300/14218 1200/13125 1100/12031 1000/10937 900/9843 > > 800/7900 750/7406 700/6912 650/6418 600/5925 550/5431 500/4937 450/4443 > > 400/3950 350/3456 300/2962 250/2468 200/1975 150/1481 100/987 50/493
> You seem to have far too many levels here. > I think that you need to check for cpufreq drivers you have attached > to your cpu and disable the one(s) that cause problem. Well, it seems real that Turion-based machines can offer that many CPU frequency levels. Another dualcore Turion machine offers these: dev.cpu.0.freq_levels: 1990/100000 1791/81822 1592/65808 1393/57582 1194/49356 995/41130 796/22152 696/19383 597/16614 497/13845 398/11076 298/8307 199/5538 99/2769 Not quite that many as the machine above, but still an impressive list. It seems I managed it to finally fix the machine above, thanks to anyone for suggestions. I updated the BIOS to the latest version (1.07) where the reports I found in the Internet suggested that Windows 7 failed to set the CPU frequency away from the default 800 MHz one with any prior version. This by itself didn't really solve the issue at hand, so I continued to upgrade the machine's kernel from FreeBSD 8.0-RELEASE to RELENG_8. Also, I modularized the kernel, and recompiled the cpufreq module with *just* the powernow driver in it. I cannot tell for sure which of the three things did fix it, but I can now run it with "powerd -a hadp -b adp", and it ran for 12 h that way (including the nightly cron jobs). -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"
