Date: Tue, 10 Jan 2006 16:55:14 +0100 From: Bruno Ducrot <ducrot@poupinou.org> To: guru@Sisis.de Cc: freebsd-mobile@freebsd.org Subject: Re: 6.0-REL && CPU M770 (cold) M740 (hot) Message-ID: <20060110155514.GF32102@poupinou.org> In-Reply-To: <20060110100741.GA3509@rebelion.Sisis.de> References: <20060110093536.GA2609@rebelion.Sisis.de> <20060110095746.GC32102@poupinou.org> <20060110100741.GA3509@rebelion.Sisis.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 10, 2006 at 11:07:41AM +0100, guru@Sisis.de wrote: > El día Tuesday, January 10, 2006 a las 10:57:46AM +0100, Bruno Ducrot escribió: > > > On Tue, Jan 10, 2006 at 10:35:36AM +0100, guru@Sisis.de wrote: > > > > > > Hello, > > > > > > In the past two weeks I've installed the same 6.0-REL configuration on > > > two Fujitsu-Siemens notebooks: > > > > > > Amilo Lifebook E8020 with Intel M770 CPU (2.13 GHz) > > > Amilo M 1437G with Intel M740 CPU (1.73 GHz) > > > > > > the one with the M770 runs very cold and nearly never the fan comes > > > up even when KDE is running the fan does not switch on, while the M740 > > > runs very warm with fan nearly always on, even if KDE is not launched; > > > > > > as well there are a lot of differences in the sysctl's output > > > of both systems; I'm attaching of bot the 'sysctl -a | fgrep acpi_' > > > > I don't see the 'correct' sysctl to debug your problem. > > Please send: > > sysctl hw.acpi > > and > > sysctl dev.cpu > > Thanks for your feedback; here it goes; > > M770 CPU: > > hw.acpi.supported_sleep_state: S3 S4 S5 > hw.acpi.power_button_state: S5 > hw.acpi.sleep_button_state: S3 > hw.acpi.lid_switch_state: NONE > hw.acpi.standby_state: S1 > hw.acpi.suspend_state: S3 > hw.acpi.sleep_delay: 1 > hw.acpi.s4bios: 0 > hw.acpi.verbose: 0 > hw.acpi.reset_video: 1 > hw.acpi.cpu.cx_supported: C1/0 C2/1 C3/185 > hw.acpi.cpu.cx_lowest: C1 you may want to try to set hw.acpi.cpu.cx_lowest=C4 here. > hw.acpi.cpu.cx_usage: 100.00% 0.00% 0.00% > hw.acpi.acline: 1 > hw.acpi.battery.life: 98 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 1 > hw.acpi.battery.units: 2 > hw.acpi.battery.info_expire: 5 > dev.cpu.0.%desc: ACPI CPU > dev.cpu.0.%driver: cpu > dev.cpu.0.%location: handle=\_PR_.CPU0 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%parent: acpi0 I don't see any thermal zone. How are you able to determine the current temperature for this model? It's also strange that one is not able to scale frequency and voltage from the est driver (included in the cpufreq.ko module). > > M740 CPU: > > hw.acpi.supported_sleep_state: S3 S4 S5 > hw.acpi.power_button_state: S5 > hw.acpi.sleep_button_state: S3 > hw.acpi.lid_switch_state: NONE > hw.acpi.standby_state: S1 > hw.acpi.suspend_state: S3 > hw.acpi.sleep_delay: 1 > hw.acpi.s4bios: 0 > hw.acpi.verbose: 0 > hw.acpi.reset_video: 1 > hw.acpi.cpu.cx_supported: C1/1 C2/1 C3/1 C4/1 > hw.acpi.cpu.cx_lowest: C1 ditto. Try hw.acpi.cpu.cx_lowest=C4 For both of your laptops, you can set this sysctl via your /etc/rc.conf Do a man rc.conf and look for 'performance_cx_lowest' and 'economy_cx_lowest'. > hw.acpi.cpu.cx_usage: 100.00% 0.00% 0.00% 0.00% > hw.acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.tz0.temperature: 51.0C It's not that high, especially if frequency and idle power saving (this is the C? stuff) are not turned on. > hw.acpi.thermal.tz0.active: -1 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: -1 > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 100.0C > hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > hw.acpi.battery.life: 100 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 0 > hw.acpi.battery.units: 1 > hw.acpi.battery.info_expire: 5 > hw.acpi.acline: 1 > dev.cpu.0.%desc: ACPI CPU > dev.cpu.0.%driver: cpu > dev.cpu.0.%location: handle=\_PR_.CPU1 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%parent: acpi0 > dev.cpu.0.freq: 1735 > dev.cpu.0.freq_levels: 1735/-1 1518/-1 1301/-1 1084/-1 867/-1 650/-1 433/-1 216/-1 Sound like only acpi_throttle (or p4tcc) is used, but no est. > dev.cpufreq.0.%driver: cpufreq > dev.cpufreq.0.%parent: cpu0 Could you please try to include the following to your loader.conf: cpufreq_load="YES" Note that it's not possible ATM to 'kldload cpufreq' for the enhanced speedstep support. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060110155514.GF32102>