On Thu, Dec 24, 2009 at 08:24:12AM -0800, Kevin Oberman wrote: > > Date: Thu, 24 Dec 2009 11:46:26 +0100 > > From: Bernd Walter <ticso_at_cicely7.cicely.de> > > Sender: owner-freebsd-current_at_freebsd.org > > > > On Wed, Dec 23, 2009 at 04:44:35PM +0200, Gleb Kurtsou wrote: > > > On (21/12/2009 19:18), Doug Barton wrote: > > > > b. f. wrote: > > > > > On 12/21/09, Doug Barton <dougb_at_freebsd.org> wrote: > > > > >> b. f. wrote: > > > > >>>> no X! So I think to myself, what else did I change last night.... oh > > > > > > > > > >>> acpi_perf? acpi_throttle? acpi_thermal? acpi_video? > > > > >> I haven't done anything special with the acpi stuff. The only thing > > > > >> that looks relevant from dmesg is: acpi_tz0: <Thermal Zone> on acpi0 > > > > >> > > > > > > > > > > Yes, but which components show up in 'sysctl -a | grep -ie acpi' ? > > > > > > > > It's a long list, but here you go: > > > > http://people.freebsd.org/~dougb/acpi-grep.txt > > > > > > > > >>> Which nvidia driver? > > > > >> The latest. > > > > > > > > > > Which video card? > > > > > > > > nvidia0: <GeForce Go 7300> > > > I had similar problems with GeForce 8400M. GPU temperature could get up > > > to 100C in X, which increased CPU temperature in its turn. I use > > > powerd, and had lockups with *_cx_lowest settings. I run amd64, i386 was > > > just fine on the same notebook. > > > > It is not just nvidia. > > I'm using two plain old PCI Matrox G400 and whenever I start X with > > powerd enabled I have a full freeze within 24 hours. > > It doesn't seem to be a problem to start powerd once X is runnning. > > Maybe it is something like tuning some delay loop with reduced clock > > rate, which then isn't long enough with increased speed. > > Quick question...are you using throttling/TCC? If so, either turn it off > or limit how low it can run the CPU. When I was running throttling on > systems with old Matrox and Radeon cards, they would freeze if the > throttling went too low. I asume yes - not sure about all those modern fancy names. In other words dev.cpu.?.freq changes. > As mav pointed out at http://wiki.freebsd.org/TuningPowerConsumption, > TCC does little to conserve power and was not designed for that. TCC is > Thermal Control Circuit and is designed to keep the CPU form > over-temping. It works for this, but not power management. I'd love to > see it off (for power management) by default. > hint.p4tcc.0.disabled=1 > hint.acpi_throttle.0.disabled=1 What is the difference between the hints and disabling powerd? My system is a C2 quad on an Intel board running i386/PAE. Only C1 is supported, which - to my knowledge - doesn't require powerd and should be active by default. [20]cicely7# sysctl dev.cpu 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 dev.cpu.0.temperature: 60 dev.cpu.0.freq: 2394 dev.cpu.0.freq_levels: 2394/89000 2094/77875 1795/66750 1496/55625 1197/44500 897/33375 598/22250 299/11125 dev.cpu.0.cx_supported: C1/1 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.temperature: 59 dev.cpu.1.cx_supported: C1/1 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% dev.cpu.2.%desc: ACPI CPU dev.cpu.2.%driver: cpu dev.cpu.2.%location: handle=\_PR_.CPU2 dev.cpu.2.%pnpinfo: _HID=none _UID=0 dev.cpu.2.%parent: acpi0 dev.cpu.2.temperature: 54 dev.cpu.2.cx_supported: C1/1 dev.cpu.2.cx_lowest: C1 dev.cpu.2.cx_usage: 100.00% dev.cpu.3.%desc: ACPI CPU dev.cpu.3.%driver: cpu dev.cpu.3.%location: handle=\_PR_.CPU3 dev.cpu.3.%pnpinfo: _HID=none _UID=0 dev.cpu.3.%parent: acpi0 dev.cpu.3.temperature: 52 dev.cpu.3.cx_supported: C1/1 dev.cpu.3.cx_lowest: C1 dev.cpu.3.cx_usage: 100.00% -- B.Walter <bernd_at_bwct.de> http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.Received on Thu Dec 24 2009 - 16:48:42 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:59 UTC