Date: Tue, 04 Aug 2015 13:18:21 -0700 From: John Baldwin <jhb@freebsd.org> To: freebsd-hackers@freebsd.org Cc: Mario Lobo <lobo@bsd.com.br>, "Herbert J. Skuhra" <herbert@oslo.ath.cx> Subject: Re: Gigabyte 970A-UD3P and hwpstate problem Message-ID: <1678045.UlXctAKXAD@ralph.baldwin.cx> In-Reply-To: <20150712152321.51b8407c@Papi> References: <20150710213752.473cb831@Papi> <20150711135006.GB41680@oslo.ath.cx> <20150712152321.51b8407c@Papi>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, July 12, 2015 03:23:21 PM Mario Lobo wrote: > On Sat, 11 Jul 2015 15:50:06 +0200 > "Herbert J. Skuhra" <herbert@oslo.ath.cx> wrote: >=20 > > On Fri, Jul 10, 2015 at 09:37:52PM -0300, Mario Lobo wrote: > > > Hi; > > >=20 > > > I just installed a Gigabyte 970A-UD3P mobo and updated BIOS to th= e > > > latest version but the problem also showed with the previous > > > version. > > >=20 > > > Here is my amd64 10-STABLE setup: > > >=20 > > > FreeBSD 10.2-PRERELEASE #0 r285207M: Tue Jul 7 00:11:01 BRT 2015= > > > amd64 > > >=20 > > > CPU: AMD FX-8320E Eight-Core Processor (3214.93-MHz K8-class CPU)= > > > Origin=3D"AuthenticAMD" Id=3D0x600f20 Family=3D0x15 Model=3D= 0x2 > > > Stepping=3D0 > > > Features=3D0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP= ,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> > > > Features2=3D0x3e98320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,S= SE4.2,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C> > > > AMD Features=3D0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM= > AMD > > > Features2=3D0x1ebbfff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Pref= etch,OSVW,IBS,XOP,SKINIT,WDT,LWP,FMA4,TCE,NodeId,TBM,Topology,PCXC,PNXC= > > > > Structured Extended Features=3D0x8<BMI1> > > > SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=3D65536 > > > TSC: P-state invariant, performance statistics > > > real memory =3D 17179869184 (16384 MB) > > > [snip] > > > ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has > > > zero address or length: 0x0000000000000000/0x1 (20150515/tbfadt-6= 73) > > > [snip] > > > hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff o= n > > > acpi0 > > >=20 > > > The problem: > > >=20 > > > powerd: no cpufreq(4) support -- aborting: No such file or direct= ory > > > /etc/rc: WARNING: failed to start powerd > >=20 > > Could this be your problem: > >=20 > > r276986 | nwhitehorn | 2015-01-11 18:10:07 +0100 (s=F8n, 11 jan 201= 5) | > > 8 lines > >=20 > > MFC r265329: > > Disable ACPI and P4TCC throttling by default, following discussion = on > > freebsd-current. These CPU speed control techniques are usually > > unhelpful at best. For now, continue building the relevant code int= o > > GENERIC so that it can trivially be re-enabled at runtime if anyone= > > wants it. > >=20 > > Relnotes: yes > >=20 > > % svnlite diff -c 276986 sys/amd64/conf/GENERIC.hints=20 > > Index: sys/amd64/conf/GENERIC.hints > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > --- sys/amd64/conf/GENERIC.hints (revision 276985) > > +++ sys/amd64/conf/GENERIC.hints (revision 276986) > > @@ -31,3 +31,5 @@ > > hint.attimer.0.port=3D"0x40" > > hint.attimer.0.irq=3D"0" > > hint.wbwd.0.at=3D"isa" > > +hint.acpi_throttle.0.disabled=3D"1" > > +hint.p4tcc.0.disabled=3D"1" > >=20 > > Does it work if your unset or remove those lines > > from /boot/device.hints? > >=20 >=20 > YEEESSS ! Thanks for pointing that out! >=20 > I have these commented on my loader.conf but I didn't know they were > active somewhere else. >=20 > As far as cpufreq/powerd goes, it's working now and frequencies are > being throttled but still no cool'n'quiet/hwpstate0 showing on dmesg.= > acpi_throttle attaches to cpu0 but not to the others. The acpi_throttle isn't really that helpful though. You probably want to try to add support for your CPU to the hwpstate driver instead and leave acpi_throttle disabled. Can you run 'kgdb' as root and get the output of 'p amd_pminfo'? Hmm, do you have an acpi_perf0 device? If not, then your CPU isn't supported without BIOS help. First check to see if there are any BIOS options to control CPU throttling that are currently disabled. --=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1678045.UlXctAKXAD>