[stable 9] broken hwpstate calls

[Sean Bruno]

On Fri, 2012-05-18 at 09:18 -0700, Jung-uk Kim wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 2012-05-18 01:32:09 -0400, Sean Bruno wrote:
> > Looks like my AMD box isn't quite working correctly with regards
> > to P-states.    I noted this repeating periodically: hwpstate0: set
> > freq failed, err 6
> > 
> > 
> > I noted these errors when setting the hwpstate verbose systctl on:
> > 
> > May 17 22:28:32 Alice kernel: hwpstate0: set freq failed, err 6 May
> > 17 22:28:32 Alice kernel: hwpstate0: setting P1-state on cpu0 May
> > 17 22:28:32 Alice kernel: hwpstate0: result  P1-state on cpu0 May
> > 17 22:28:32 Alice kernel: hwpstate0: setting P1-state on cpu1 May
> > 17 22:28:32 Alice kernel: hwpstate0: result  P1-state on cpu1 May
> > 17 22:28:32 Alice kernel: hwpstate0: setting P1-state on cpu2 May
> > 17 22:28:32 Alice kernel: hwpstate0: result  P1-state on cpu2 May
> > 17 22:28:32 Alice kernel: hwpstate0: setting P1-state on cpu3 May
> > 17 22:28:32 Alice kernel: hwpstate0: result  P1-state on cpu3 May
> > 17 22:28:32 Alice kernel: hwpstate0: setting P1-state on cpu4 May
> > 17 22:28:32 Alice kernel: hwpstate0: result  P1-state on cpu4 May
> > 17 22:28:32 Alice kernel: hwpstate0: setting P1-state on cpu5 May
> > 17 22:28:32 Alice kernel: hwpstate0: result  P1-state on cpu5 May
> > 17 22:28:32 Alice kernel: hwpstate0: setting P1-state on cpu6 May
> > 17 22:28:32 Alice kernel: hwpstate0: result  P1-state on cpu6 May
> > 17 22:28:32 Alice kernel: hwpstate0: setting P1-state on cpu7 May
> > 17 22:28:32 Alice kernel: hwpstate0: result  P1-state on cpu7
> > 
> > 
> > Sean
> > 
> > ref this machine:  http://forums.pcbsd.org/showthread.php?t=16733
> 
> I briefly looked at the dmesg.  You have a Family 15h processor
> (Bulldozer with Turbo Core) and I believe it isn't supported (yet).
> It won't be too hard to implement, though.
> 
> Jung-uk Kim


I'm assuming, something like this to start?

http://people.freebsd.org/~sbruno/bulldozer.txt

I'm reading the AMD spec, and that *seems* to be right?  But, chances
are I have no idea what I'm doing.  :-)

Sean