From nobody@FreeBSD.org  Fri May  2 21:59:04 2014
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by hub.freebsd.org (Postfix) with ESMTPS id A052F64A
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  2 May 2014 21:59:04 +0000 (UTC)
Received: from cgiserv.freebsd.org (cgiserv.freebsd.org [IPv6:2001:1900:2254:206a::50:4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 8E34710DC
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  2 May 2014 21:59:04 +0000 (UTC)
Received: from cgiserv.freebsd.org ([127.0.1.6])
	by cgiserv.freebsd.org (8.14.8/8.14.8) with ESMTP id s42Lx4Z9077177
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 2 May 2014 21:59:04 GMT
	(envelope-from nobody@cgiserv.freebsd.org)
Received: (from nobody@localhost)
	by cgiserv.freebsd.org (8.14.8/8.14.8/Submit) id s42Lx4I5077176;
	Fri, 2 May 2014 21:59:04 GMT
	(envelope-from nobody)
Message-Id: <201405022159.s42Lx4I5077176@cgiserv.freebsd.org>
Date: Fri, 2 May 2014 21:59:04 GMT
From: Brodey Dover <doverosx@gmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: AMD Kabini (AM1/FM1Sb) Frequency Switching Causes Crash
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         189267
>Category:       amd64
>Synopsis:       [cpufreq] AMD Kabini (AM1/FM1Sb) Frequency Switching Causes Crash
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 02 22:00:00 UTC 2014
>Closed-Date:    
>Last-Modified:  Sun May  4 15:10:01 UTC 2014
>Originator:     Brodey Dover
>Release:        9.2-RELEASE-p4
>Organization:
>Environment:
FreeBSD freenas.brodeydover.ca 9.2-RELEASE-p4 FreeBSD 9.2-RELEASE-p4 #0 r262572+
17a4d3d: Wed Apr 23 10:09:38 PDT 2014     root@build3.ixsystems.com:/tank/home/j
kh/build/9.2.1/freenas/os-base/amd64/fusion/jkh/9.2.1/freenas/FreeBSD/src/sys/FR
EENAS.amd64  amd64
>Description:
Running powerd on FreeNAS system with C6 state enabled in BIOS causes
the system to crash shortly after start-up. Disabling the C6 state in
the BIOS resolves the system crashing but then one does not receive the
low power modes afforded by the platform. 

Disabling powerd, however, enabling CnQ and C6 state in the BIOS also
resolves the system crashing with the same effect; no low power modes.
I also note significant power usage from a system that should otherwise
be consuming less power than my Skt 939 90W TDP X2 3800+ with 4x DDR 1GB
modules. I noted that the GPU was also never down-clocked and would never
enter any low power modes.

I feel that this is a serious compatibility issue for hardware (that I
think was released when 9.2 was production). 
>How-To-Repeat:
Run hardware on FreeBSD 9.2. (I haven't tried FreeBSD 10).
>Fix:
N/A

>Release-Note:
>Audit-Trail:

From: Jeremias Blendin <jeremias@blendin.org>
To: doverosx@gmail.com, bug-followup@FreeBSD.org
Cc:  
Subject: Re: amd64/189267: AMD Kabini (AM1/FM1Sb) Frequency Switching Causes Crash
Date: Sat, 3 May 2014 11:17:03 +0200

 --001a1134056682a4e204f87b5c8a
 Content-Type: text/plain; charset=UTF-8
 
 I have the same problem with an AMD Athlon 5350 on Asrock AM1H-ITX. I did
 not verify the powerd solution yet. However, the experience is similar,
 shortly after booting the system would reset. I tried FreeBSD 10 release
 and stable, in both cases I activated powerd in the installation process
 and had the described reboot issue.
 I suspected a driver issue and switched to a FreeBSD 11 snapshot which
 works perfectly. I guess the reason is that powerd is not enabled on these
 snapshots.
 
 --001a1134056682a4e204f87b5c8a--

From: Brodey Dover <doverosx@gmail.com>
To: Jeremias Blendin <jeremias@blendin.org>
Cc: bug-followup@freebsd.org
Subject: Re: amd64/189267: AMD Kabini (AM1/FM1Sb) Frequency Switching Causes Crash
Date: Sun, 4 May 2014 11:03:07 -0400

 --089e01493df60178f704f89450e9
 Content-Type: text/plain; charset=UTF-8
 
 I also noticed that HPET isn't an eventtimer option in spite of it being
 enabled in the BIOS.
 
 [brodey@freenas] /# sysctl -a | grep eventtimer
 kern.eventtimer.choice: LAPIC(400) i8254(100) RTC(0)
 kern.eventtimer.et.LAPIC.flags: 15
 kern.eventtimer.et.LAPIC.frequency: 50000961
 kern.eventtimer.et.LAPIC.quality: 400
 kern.eventtimer.et.i8254.flags: 1
 kern.eventtimer.et.i8254.frequency: 1193182
 kern.eventtimer.et.i8254.quality: 100
 kern.eventtimer.et.RTC.flags: 17
 kern.eventtimer.et.RTC.frequency: 32768
 kern.eventtimer.et.RTC.quality: 0
 kern.eventtimer.periodic: 0
 kern.eventtimer.timer: LAPIC
 kern.eventtimer.activetick: 1
 kern.eventtimer.idletick: 0
 kern.eventtimer.singlemul: 2
 
 I also note that one core has a different supported state (maybe this is an
 AMD implementation):
 
 hw.acpi.cpu.cx_lowest: C1
 dev.cpu.0.cx_supported: C1/1/0 C2/2/400
 dev.cpu.0.cx_lowest: C1
 dev.cpu.0.cx_usage: 100.00% 0.00% last 98us
 dev.cpu.1.cx_supported: C1/1/0
 dev.cpu.1.cx_lowest: C1
 dev.cpu.1.cx_usage: 100.00% last 235us
 dev.cpu.2.cx_supported: C1/1/0
 dev.cpu.2.cx_lowest: C1
 dev.cpu.2.cx_usage: 100.00% last 17us
 dev.cpu.3.cx_supported: C1/1/0
 dev.cpu.3.cx_lowest: C1
 dev.cpu.3.cx_usage: 100.00% last 16us
 
 Seeing C1 state supported and it's usage makes me wonder where my other
 wattage is being used. I think the GPU isn't being switched down.
 
 
 On Sat, May 3, 2014 at 5:17 AM, Jeremias Blendin <jeremias@blendin.org>wrote:
 
 > I have the same problem with an AMD Athlon 5350 on Asrock AM1H-ITX. I did
 > not verify the powerd solution yet. However, the experience is similar,
 > shortly after booting the system would reset. I tried FreeBSD 10 release
 > and stable, in both cases I activated powerd in the installation process
 > and had the described reboot issue.
 > I suspected a driver issue and switched to a FreeBSD 11 snapshot which
 > works perfectly. I guess the reason is that powerd is not enabled on these
 > snapshots.
 >
 
 --089e01493df60178f704f89450e9
 Content-Type: text/html; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 <div dir=3D"ltr"><div><div>I also noticed that HPET isn&#39;t an eventtimer=
  option in spite of it being enabled in the BIOS. <br><br>[brodey@freenas] =
 /# sysctl -a | grep eventtimer<br>kern.eventtimer.choice: LAPIC(400) i8254(=
 100) RTC(0)<br>
 kern.eventtimer.et.LAPIC.flags: 15<br>kern.eventtimer.et.LAPIC.frequency: 5=
 0000961<br>kern.eventtimer.et.LAPIC.quality: 400<br>kern.eventtimer.et.i825=
 4.flags: 1<br>kern.eventtimer.et.i8254.frequency: 1193182<br>kern.eventtime=
 r.et.i8254.quality: 100<br>
 kern.eventtimer.et.RTC.flags: 17<br>kern.eventtimer.et.RTC.frequency: 32768=
 <br>kern.eventtimer.et.RTC.quality: 0<br>kern.eventtimer.periodic: 0<br>ker=
 n.eventtimer.timer: LAPIC<br>kern.eventtimer.activetick: 1<br>kern.eventtim=
 er.idletick: 0<br>
 kern.eventtimer.singlemul: 2<br><br></div>I also note that one core has a d=
 ifferent supported state (maybe this is an AMD implementation):<br><br>hw.a=
 cpi.cpu.cx_lowest: C1<br>dev.cpu.0.cx_supported: C1/1/0 C2/2/400<br>dev.cpu=
 .0.cx_lowest: C1<br>
 dev.cpu.0.cx_usage: 100.00% 0.00% last 98us<br>dev.cpu.1.cx_supported: C1/1=
 /0<br>dev.cpu.1.cx_lowest: C1<br>dev.cpu.1.cx_usage: 100.00% last 235us<br>=
 dev.cpu.2.cx_supported: C1/1/0<br>dev.cpu.2.cx_lowest: C1<br>dev.cpu.2.cx_u=
 sage: 100.00% last 17us<br>
 dev.cpu.3.cx_supported: C1/1/0<br>dev.cpu.3.cx_lowest: C1<br>dev.cpu.3.cx_u=
 sage: 100.00% last 16us<br><br></div>Seeing C1 state supported and it&#39;s=
  usage makes me wonder where my other wattage is being used. I think the GP=
 U isn&#39;t being switched down.<br>
 </div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat,=
  May 3, 2014 at 5:17 AM, Jeremias Blendin <span dir=3D"ltr">&lt;<a href=3D"=
 mailto:jeremias@blendin.org" target=3D"_blank">jeremias@blendin.org</a>&gt;=
 </span> wrote:<br>
 <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
 x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>I have the same proble=
 m with an AMD Athlon 5350 on Asrock AM1H-ITX. I did not verify the powerd s=
 olution yet. However, the experience is similar, shortly after booting the =
 system would reset. I tried FreeBSD 10 release and stable, in both cases I =
 activated powerd in the installation process and had the described reboot i=
 ssue.<br>
 
 </div><div>I suspected a driver issue and switched to a FreeBSD 11 snapshot=
  which works perfectly. I guess the reason is that powerd is not enabled on=
  these snapshots.</div></div>
 </blockquote></div><br></div>
 
 --089e01493df60178f704f89450e9--
>Unformatted:
