Date: Sun, 06 Jan 2019 09:37:06 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 234657] AMD Opteron X3000 series CPU temperature sensor support Message-ID: <bug-234657-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234657 Bug ID: 234657 Summary: AMD Opteron X3000 series CPU temperature sensor support Product: Base System Version: 11.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: tjoard@gmail.com I am using FreeNAS 11.2 and as it turns out, I cannot read out the CPU temperature for my AMD Opteron X3216 CPU in my HPE Microserver Gen10. I fil= ed this at the FreeNAS Redmine: https://redmine.ixsystems.com/issues/64077 I have the following tunables: amdtemp_load=3D"YES" # for reading AMD CPU temperatures hint.acpi_throttle.0.disabled=3D"YES" # cool'n'quiet hw.pci.realloc_bars=3D"1" # needed for screen output on Microserver gen10 Trying sysctl -a | grep -i temp does not yield any temperatures. I also tri= ed other things to grep for like cpu, none of which would give me the CPU temperatures. I submitted FreeNAS debug output to the FreeNAS developers. They replied the following: "As I can see, there are several variations of that CPU generati= on, and while FreeBSD supports temperature reporting for one of them, two others are different. As I understand, amdtemp driver would have to attach to devi= ce "hostb7 pnpinfo vendor=3D0x1022 device=3D0x1573", but that ID is not in the= code.", along with the suggestion to contact Conrad Meyer about this. I contacted Conrad, he asked me what the family/model numbers for my CPU ar= e. The relevant dmesg output: CPU: AMD Opteron(tm) X3216 APU (1597.04-MHz K8-class = CPU) Origin=3D"AuthenticAMD" Id=3D0x660f01 Family=3D0x15 Model=3D0x60 Step= ping=3D1 =20 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> =20 Features2=3D0x7ed8320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,MOVB= E,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND> AMD Features=3D0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM> AMD Features2=3D0x2febbfff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW= ,IBS,XOP,SKINIT,WDT,LWP,FMA4,TCE,NodeId,TBM,Topology,PCXC,PNXC,<b25>,DBE,PT= SC,MWAITX> Structured Extended Features=3D0x1a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2> XSAVE Features=3D0x1<XSAVEOPT> SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=3D32768 TSC: P-state invariant, performance statistics Conrad also asked me how the FreeNAS dev arrived at this device information. That I do not know, but I think they could (and are also better qualified t= o) explain this? Also, I won't mind (re)generating any diagnostic information = if need be. I am willing to test patches for this issue on my hardware. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234657-227>