Subject: Re: Failure of PowerNow! on amd64 -current
To: Juan RP <email@example.com>
From: Scott Ellis <firstname.lastname@example.org>
Date: 04/03/2007 20:18:51
Sure enough. Guess I just missed the update to 1.18 when I cvs updated!
Sorry for the noise, it works great now. Thanks Juan!
Juan RP wrote:
> Can you please try with powernow_k8.c 1.18? looks like that msr_read
> needs to be
> initialized, this was reported by FUKUMOTO Atsushi and it should avoid
> the hang.
> ----- Original Message ----- From: "Scott Ellis" <email@example.com>
> To: <firstname.lastname@example.org>
> Sent: Tuesday, April 03, 2007 4:52 AM
> Subject: Failure of PowerNow! on amd64 -current
>> I upgraded my amd64 system from -current Feb 22 to -current Apr 2, and
>> found that PowerNow! seems to cause an immediate hang (not even
>> dropping to DDB...just a solid lockup).
>> Here's what I get in single-user, changing the frequency manually:
>> # sysctl -a | grep power
>> sysctl: warning: /var/run/dev.db: No such file or directory
>> machdep.powernow.frequency.target = 2200
>> machdep.powernow.frequency.current = 2200
>> machdep.powernow.frequency.available = 1000 1800 2000 2200
>> # sysctl -w machdep.powernow.frequency.target=1000
>> (yes, that "k" is all that's printed before the hang...it may be the
>> last gasp of the serial port before the crash!)
>> The above (and more importantly, estd) works fine on the Feb 22 kernel.
>> What info can I collect to help debug?