On Sunday 08 March 2009 02:06:33 am Maciej Piechotka wrote: > On Sat, 2009-03-07 at 15:00 +0000, Matthew Garrett wrote: > > On Sat, Mar 07, 2009 at 12:09:29PM +0100, Maciej Piechotka wrote: > > > # cat /proc/acpi/thermal_zone/THM0/trip_points > > > critical (S5): 99 C > > > passive: 95 C: tc1=5 tc2=4 tsp=600 devices= CPU > > > > > > The problem is that it seems that the system halts at about 95 C - in > > > moment when cooling should be applied. This might be an ACPI/ibm_acpi > > > bug. > > > > Halts as in shuts down, or halts as in stops running? The R51e seems to > > have the 32/64-bit ACPI address issue - can you try booting with > > acpi=rsdt as a kernel argument and see whether it behaves any better? > > Somehow. It keeps system at 70-80 C but on 2.6.29 it freezes the > computer when I log into Gnome (it seems that gdm is not enought and it > occures after few minutes) - i.e. I cannot move pointer, change VT nor > even ping the system (I use in-kernel radeon driver and Radeon Xpress > 200M card RC410). Hmm, I expect no PowerPlay things are implemented in the in-kernel radeon implementation yet? fglrx and aticonfig --list-powerstates and aticonfig --set-powerstate X could help a lot. This could at least explain the high temperature rates. Like that you could find out how much could be saved by graphics power savings. > i.e. I cannot move pointer, change VT nor > even ping the system (I use in-kernel radeon driver and Radeon Xpress > 200M card RC410). Sounds like the in-kernel radeon driver is not that stable yet? Yang Zhao once implemented PowerPlay support in radeonhd userspace: http://yangman.ca/git/xf86-video-radeonhd.git diffing it with the official radeonhd driver and implementing the same in the kernel's radeon driver might be necessary at some time? I once played a bit with it and I could imagine as both should be atombios based, it shouldn't be that hard to port and it got already some testing on specific HW. Matthew: Is it planned to add PowerPlay support to the radeon in-kernel driver at some time? If yes, I can help a bit. Hm, but all this has nothing to do with cpufreq which a Celeron is not capable of. Thomas -- 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
