Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Nov 2013 18:02:00 -0800
From:      Sean Bruno <sean_bruno@yahoo.com>
To:        Jung-uk Kim <jkim@FreeBSD.org>
Cc:        freebsd-acpi <freebsd-acpi@freebsd.org>
Subject:   Re: Problems with amd FX 8 core and freq scaling
Message-ID:  <1384221720.1748.53.camel@powernoodle.corp.yahoo.com>
In-Reply-To: <52815060.9050406@FreeBSD.org>
References:  <5281358D.1010406@FreeBSD.org>	<5281374F.7080802@FreeBSD.org> <CAJ-VmomgCyjX_tR7bLzw6s8jSJJvfB=5fXFCj6UgdKFz6rW-FQ@mail.gmail.com> <52814CB2.6050204@FreeBSD.org>  <52815060.9050406@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
On Mon, 2013-11-11 at 16:47 -0500, Jung-uk Kim wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 2013-11-11 16:31:30 -0500, Jung-uk Kim wrote:
> > On 2013-11-11 15:26:58 -0500, Adrian Chadd wrote:
> >> On 11 November 2013 12:00, Jung-uk Kim <jkim@freebsd.org> wrote:
> >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> >>> 
> >>> On 2013-11-11 13:16:47 -0500, Nicholas McKenzie wrote:
> >>>> But wouldn't this just disable frequency scaling and the
> >>>> whole point of powerd?
> >>> 
> >>> No.  acpi_throttle (and p4tcc) controls T-state.  "Frequency 
> >>> scaling" should be done by changing P-state.
> > 
> >> Right.
> > 
> >> IIRC, T-state is just for emergency temperature throttling. It 
> >> shouldn't be used outside of that.
> > 
> > 
> >>>>> There have been a number of reports of throttling causing 
> >>>>> crashes. This setting does not prevent powerd from
> >>>>> adjusting your CPU's clock, it just disables some arcane
> >>>>> feature which pre-dates the modern power management
> >>>>> methods.
> > 
> >> .. did anyone ever figure out why crashes would be caused by 
> >> T-state adjustment?
> > 
> > My memory is vague but I think it was not able to reject a broken
> > FADT or _PTC table, or something like that.
> 
> Just in case, here I attached the uncommitted (and untested) patch.
> 
> Jung-uk Kim
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (FreeBSD)
> 
> iQEcBAEBAgAGBQJSgVBgAAoJEHyflib82/FGACsIAJGDQGOYYO8dxvtQMw4BBnzl
> BNbFkvalvHOzaSezJz+A4R0zeIMvkfJtu0Gb8qiTkxJF+REREFo6a7lmzC7hOMwa
> 7PzRRRG34rtmnnHJro3Wc5qQwc1zBbmyFgYEJ45AkmIc62mpp9f0sZyNA1+aSpau
> 2sY6H0dXktapc2pLR1uNyxfUlr1tRhoabceGSlGLYiB583FrMsvASkaTnuWQ2IfI
> gytrJBKjMihu60KlwKauzUOVDrEuN3J/B1y7V/TrTXmcFmWgL9Wdw/gC7ToRdloT
> JdF812Duj/xYvyoNEwkz1Rm0NT5r1ZTYqwMvkOPuMfK7IWX0O9UFO8VG+QnJXhU=
> =/d/E
> -----END PGP SIGNATURE-----
> _______________________________________________
> freebsd-acpi@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org"


Let me test this on my fx-8150 tonight.  What should I look for as a
test failure/success?

sean

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (FreeBSD)

iQEcBAABAgAGBQJSgYwYAAoJEBkJRdwI6BaHG/QH/1u5cNNcy/CrM8Y1JNWG8guS
76NEW2XQjI0tF4THSqr7FlY6cGPjAZ3jY9hIUcXVmacZLrqYn8zhvwiz7UVCGiMK
CMDVne8c3Dqr2FVjCFjrpHLhQIZsVuuYCeb4IgR9SrKPt4KMu1YK1zBYILEWZd+n
Itqq/n9o9AQlFSHQgrrHBoOsm1+HsoWqlknn9nYiXIijYxxsqU4xzSORt/vW1UCF
m9oJQMCcuTde5U4+0BzLgsEmht2X3z5re2YQXkfEggBYLowvXJPSAEmfveNF1YAd
pIiKe73CYl46UBKUMN5uh2A++fXu5BYAhZrWCT0mFOU9IRQrfZHYawS/r9psUq4=
=vWd2
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1384221720.1748.53.camel>