Date: Tue, 04 Dec 2018 18:20:49 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 233764] [amdtemp] does not recognize AMD A8-7600 temperature sensors Message-ID: <bug-233764-227-d16mS5ReBd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233764-227@https.bugs.freebsd.org/bugzilla/> References: <bug-233764-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233764 Conrad Meyer <cem@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cem@freebsd.org --- Comment #1 from Conrad Meyer <cem@freebsd.org> --- That's a family 15h, model 30h (I think). Relevant BKDG is here: https://www.amd.com/system/files/TechDocs/49125_15h_Models_30h-3Fh_BKDG.pdf Should be D18F3xA4 ("Reported Temperature Control"), CurTmp[21:31] like oth= er models. 0xA4 matches our AMDTEMP_REPTMP_CTRL. Maybe this model uses CurTmpTjSel and adjusted range like the Family 17h 29= 90WX models. Support for that was added in 12.x, for family 17h only. That wou= ld make sense if the real temperature was *exactly* 49.0=C2=B0C. But 0.0 seems suspicious =E2=80=94 it seems unlikely the true temperature is exactly 49.0. Interestingly, the D18F3x00 deviceid is documented as 141D, which we define= as MISC17. So as far as I can tell, we should be doing the right thing on that CPU. What hostbridge device did amdtemp attach to on your system? Well, "dev.amdtemp.0.%parent: hostb7". What's that? Can you please provide "dev= info -v |grep hostb7"? And maybe "devinfo -v | grep device=3D0x141d" as well. Thanks. --=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-233764-227-d16mS5ReBd>