Bug 180562 - [amdtemp] amdtemp and ACPI not working with motherboard ASUS M5A97 PRO
Summary: [amdtemp] amdtemp and ACPI not working with motherboard ASUS M5A97 PRO
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: amd64 (show other bugs)
Version: 9.1-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: Andriy Gapon
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-15 00:10 UTC by Vladislav V. Prodan
Modified: 2018-05-25 00:53 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladislav V. Prodan 2013-07-15 00:10:00 UTC
amdtemp and ACPI not working with motherboard ASUS M5A97 PRO

Base Board Information
        Manufacturer: ASUSTeK COMPUTER INC.
        Product Name: M5A97 PRO
        Version: Rev 1.xx


dmesg output:

CPU: AMD FX(tm)-8120 Eight-Core Processor            (3110.48-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x600f12  Family = 0x15  Model = 0x1  Stepping = 2
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x1e98220b<SSE3,PCLMULQDQ,MON,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AESNI,XSAVE,OSXSAVE,AVX>
  AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
  AMD Features2=0x1c9bfff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,XOP,SKINIT,WDT,LWP,FMA4,NodeId,Topology,<b23>,<b24>>
  TSC: P-state invariant, performance statistics
real memory  = 34359738368 (32768 MB)
avail memory = 33190621184 (31653 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <ALASKA A M I>
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
FreeBSD/SMP: 1 package(s) x 8 core(s)
 cpu0 (BSP): APIC ID: 16
 cpu1 (AP): APIC ID: 17
 cpu2 (AP): APIC ID: 18
 cpu3 (AP): APIC ID: 19
 cpu4 (AP): APIC ID: 20
 cpu5 (AP): APIC ID: 21
 cpu6 (AP): APIC ID: 22
 cpu7 (AP): APIC ID: 23
ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20110527/tbfadt-586)
ioapic0 <Version 2.1> irqs 0-23 on motherboard
ioapic1 <Version 2.1> irqs 24-55 on motherboard
kbd1 at kbdmux0
netmap: loaded module
smbios0: <System Management BIOS> at iomem 0xf0480-0xf049e on motherboard
smbios0: Version: 2.7, BCD Revision: 2.7
acpi0: <ALASKA A M I> on motherboard
ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND (20110527/psargs-392)
ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20110527/nsinit-380)
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
cpu4: <ACPI CPU> on acpi0
cpu5: <ACPI CPU> on acpi0
cpu6: <ACPI CPU> on acpi0
cpu7: <ACPI CPU> on acpi0
attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 450
Event timer "HPET1" frequency 14318180 Hz quality 450
Event timer "HPET2" frequency 14318180 Hz quality 450
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_ec0: <Embedded Controller: GPE 0xa> port 0x62,0x66 on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 52 at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xe000-0xe07f mem 0xfd000000-0xfdffffff,0xf0000000-0xf7ffffff,0xf8000000-0xf9ffffff irq 24 at device 0.0 on pci1
pci1: <multimedia, HDA> at device 0.1 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> irq 52 at device 4.0 on pci0
pci2: <ACPI PCI bus> on pcib2
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet> port 0xd000-0xd0ff mem 0xfa104000-0xfa104fff,0xfa100000-0xfa103fff irq 44 at device 0.0 on pci2
re0: Using 1 MSI-X message
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00000000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
re0: Ethernet address: 14:da:e9:52:1a:3b
001.000007 netmap_attach [1679] success for re0
pcib3: <ACPI PCI-PCI bridge> irq 53 at device 6.0 on pci0
pci3: <ACPI PCI bus> on pcib3
atapci0: <JMicron JMB362 SATA300 controller> port 0xc040-0xc047,0xc030-0xc033,0xc020-0xc027,0xc010-0xc013,0xc000-0xc00f mem 0xfe210000-0xfe2101ff irq 51 at device 0.0 on pci3
atapci1: <AHCI SATA controller> at channel -1 on atapci0
atapci1: AHCI v1.10 controller with 2 3Gbps ports, PM supported
ata2: <ATA channel> on atapci1
ata3: <ATA channel> on atapci1
pcib4: <ACPI PCI-PCI bridge> irq 53 at device 7.0 on pci0
pci4: <ACPI PCI bus> on pcib4
xhci0: <XHCI (generic) USB 3.0 controller> mem 0xfe100000-0xfe107fff irq 50 at device 0.0 on pci4
xhci0: 32 byte context size.
usbus0 on xhci0
atapci2: <ATI IXP700/800 SATA300 controller> port 0xf040-0xf047,0xf030-0xf033,0xf020-0xf027,0xf010-0xf013,0xf000-0xf00f mem 0xfe307000-0xfe3073ff irq 19 at device 17.0 on pci0
atapci2: AHCI v1.20 controller with 6 6Gbps ports, PM supported
ata4: <ATA channel> at channel 0 on atapci2
ata5: <ATA channel> at channel 1 on atapci2
ata6: <ATA channel> at channel 2 on atapci2
ata7: <ATA channel> at channel 3 on atapci2
ata8: <ATA channel> at channel 4 on atapci2
ata9: <ATA channel> at channel 5 on atapci2
ohci0: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe306000-0xfe306fff irq 18 at device 18.0 on pci0
usbus1 on ohci0
ehci0: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe305000-0xfe3050ff irq 17 at device 18.2 on pci0
usbus2: EHCI version 1.0
usbus2 on ehci0
ohci1: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe304000-0xfe304fff irq 20 at device 19.0 on pci0
usbus3 on ohci1
ehci1: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe303000-0xfe3030ff irq 21 at device 19.2 on pci0
usbus4: EHCI version 1.0
usbus4 on ehci1
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib5: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pci5: <ACPI PCI bus> on pcib5
ohci2: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe302000-0xfe302fff irq 18 at device 20.5 on pci0
usbus5 on ohci2
ohci3: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe301000-0xfe301fff irq 22 at device 22.0 on pci0
usbus6 on ohci3
ehci2: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe300000-0xfe3000ff irq 23 at device 22.2 on pci0
usbus7: EHCI version 1.0
usbus7 on ehci2
acpi_button0: <Power Button> on acpi0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcdfff,0xce000-0xcefff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
ppc0: cannot reserve I/O port range
acpi_throttle0: <ACPI CPU Throttling> on cpu0
hwpstate0: <Cool`n'Quiet 2.0> on cpu0
acpi_throttle1: <ACPI CPU Throttling> on cpu1
acpi_throttle1: failed to attach P_CNT
device_attach: acpi_throttle1 attach returned 6
acpi_throttle2: <ACPI CPU Throttling> on cpu2
acpi_throttle2: failed to attach P_CNT
device_attach: acpi_throttle2 attach returned 6
acpi_throttle3: <ACPI CPU Throttling> on cpu3
acpi_throttle3: failed to attach P_CNT
device_attach: acpi_throttle3 attach returned 6
acpi_throttle4: <ACPI CPU Throttling> on cpu4
acpi_throttle4: failed to attach P_CNT
device_attach: acpi_throttle4 attach returned 6
acpi_throttle5: <ACPI CPU Throttling> on cpu5
acpi_throttle5: failed to attach P_CNT
device_attach: acpi_throttle5 attach returned 6
acpi_throttle6: <ACPI CPU Throttling> on cpu6
acpi_throttle6: failed to attach P_CNT
device_attach: acpi_throttle6 attach returned 6
acpi_throttle7: <ACPI CPU Throttling> on cpu7
acpi_throttle7: failed to attach P_CNT
device_attach: acpi_throttle7 attach returned 6
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
DUMMYNET 0 with IPv6 initialized (100409)
load_dn_sched dn_sched PRIO loaded
load_dn_sched dn_sched QFQ loaded
load_dn_sched dn_sched RR loaded
load_dn_sched dn_sched WF2Q+ loaded
load_dn_sched dn_sched FIFO loaded
usbus0: 5.0Gbps Super Speed USB v3.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 480Mbps High Speed USB v2.0
usbus3: 12Mbps Full Speed USB v1.0
usbus4: 480Mbps High Speed USB v2.0
usbus5: 12Mbps Full Speed USB v1.0
usbus6: 12Mbps Full Speed USB v1.0
usbus7: 480Mbps High Speed USB v2.0
ugen0.1: <0x1b21> at usbus0
uhub0: <0x1b21 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ugen1.1: <ATI> at usbus1
uhub1: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen2.1: <ATI> at usbus2
uhub2: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
ugen3.1: <ATI> at usbus3
uhub3: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
ugen4.1: <ATI> at usbus4
uhub4: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus4
ugen5.1: <ATI> at usbus5
uhub5: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
ugen6.1: <ATI> at usbus6
uhub6: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus6
ugen7.1: <ATI> at usbus7
uhub7: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus7
uhub5: 2 ports with 2 removable, self powered
uhub6: 4 ports with 4 removable, self powered
uhub1: 5 ports with 5 removable, self powered
uhub3: 5 ports with 5 removable, self powered
uhub0: 4 ports with 4 removable, self powered
uhub7: 4 ports with 4 removable, self powered
uhub2: 5 ports with 5 removable, self powered
uhub4: 5 ports with 5 removable, self powered
ada0 at ata4 bus 0 scbus2 target 0 lun 0
ada0: <ST3000DM001-9YN166 CC4C> ATA-8 SATA 3.x device
ada0: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
ada0: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad8
ada1 at ata5 bus 0 scbus3 target 0 lun 0
ada1: <ST3000DM001-9YN166 CC4C> ATA-8 SATA 3.x device
ada1: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
ada1: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada1: Previously was known as ad10
ada2 at ata6 bus 0 scbus4 target 0 lun 0
ada2: <ST3000DM001-9YN166 CC4C> ATA-8 SATA 3.x device
ada2: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
ada2: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada2: Previously was known as ad12
ada3 at ata7 bus 0 scbus5 target 0 lun 0
ada3: <ST3000DM001-9YN166 CC4C> ATA-8 SATA 3.x device
ada3: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
ada3: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada3: Previously was known as ad14
SMP: AP CPU #1 Launched!
SMP: AP CPU #7 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #6 Launched!
SMP: AP CPU #5 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #4 Launched!
Timecounter "TSC-low" frequency 12150329 Hz quality 1000
Trying to mount root from zfs:tank []...
re0: link state changed to UP
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2013-07-15 16:52:40 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-amd64

reclassify.
Comment 2 Mark Linimon 2013-07-15 17:05:36 UTC
----- Forwarded message from Jan Bramkamp <crest@rlwinm.de> -----

Date: Mon, 15 Jul 2013 18:00:19 +0200
From: Jan Bramkamp <crest@rlwinm.de>
To: freebsd-amd64@freebsd.org
Subject: Re: amd64/180562: amdtemp and ACPI not working with motherboard ASUS M5A97 PRO
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130707 Thunderbird/17.0.7

On 15.07.2013 17:53, linimon@FreeBSD.org wrote:
> Synopsis: amdtemp and ACPI not working with motherboard ASUS M5A97 PRO

The amdtemp driver in FreeBSD 9.1 doesn't support Bulldozer and
Piledriver temperature sensors. Support is available 10-CURRENT.
Copy sys/dev/amdtemp/amdtemp.c from 10-CURRENT and rebuild your kernel
if you want support for the CPU internal temperature sensor. This worked
for me with a FX-8350 CPU.
_______________________________________________
freebsd-amd64@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org"

----- End forwarded message -----
Comment 3 Jung-uk Kim freebsd_committer 2013-07-16 00:15:22 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As I mentioned in the commit log, its temperature reading is NOT
absolute.  Therefore, it is not very useful.

http://svnweb.freebsd.org/changeset/base/232090

Please try aibs(4) if you have an ASUS motherboard.

Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (FreeBSD)

iQEcBAEBAgAGBQJR5IKKAAoJECXpabHZMqHOAXMIAMwrQyKzTDcC+KzBh99WaRK8
AjJtf0rjuq5JHPEv7B7p7AfLo7CgELrXzj+0Te7Z2up0yduH2FL9f3yJMlqIItkb
x76kfYLJ3syyR3ZE2v8kdE6wSprg+peUsTGJWX9gmlxOrmwahbsvgof/NjuUynG/
1rqt641NrwcjtZH8vOeMGZysmosANXEb1YLlrBE3DQkIG2FZHQ/gbm3tsh9sjUEE
6hL37BsOfbVYzSZlRwFyNbb3pmWBtTZEeYpTmQQjDbzR6VTd6YiQVHdi8dtLXBv4
WwY2uZflWpWmB53bPpMdE/ij4uLCKPla7fKmaGn116G5sDCz9x6b1MpmqCoD3Bw=
=3Q+J
-----END PGP SIGNATURE-----
Comment 4 Mark Linimon 2013-08-09 02:33:41 UTC
----- Forwarded message from John-Mark Gurney <jmg@funkthat.com> -----

Date: Sat, 20 Jul 2013 22:32:37 -0700
From: John-Mark Gurney <jmg@funkthat.com>
To: Jan Bramkamp <crest@rlwinm.de>
Subject: Re: amd64/180562: amdtemp and ACPI not working with motherboard ASUS M5A97 PRO

Jan Bramkamp wrote this message on Mon, Jul 15, 2013 at 18:00 +0200:
> The amdtemp driver in FreeBSD 9.1 doesn't support Bulldozer and
> Piledriver temperature sensors. Support is available 10-CURRENT.
> Copy sys/dev/amdtemp/amdtemp.c from 10-CURRENT and rebuild your kernel
> if you want support for the CPU internal temperature sensor. This worked
> for me with a FX-8350 CPU.

Hmm... Doesn't work for me on my AMD A10-5700 processor which, according
to wikipedia, is a piledriver...

I did add my chip to the driver:
Index: amdtemp.c
===================================================================
--- amdtemp.c   (revision 252129)
+++ amdtemp.c   (working copy)
@@ -76,6 +76,7 @@
 #define        DEVICEID_AMD_MISC0F     0x1103
 #define        DEVICEID_AMD_MISC10     0x1203
 #define        DEVICEID_AMD_MISC11     0x1303
+#define        DEVICEID_AMD_MISC12     0x1403
 #define        DEVICEID_AMD_MISC14     0x1703
 #define        DEVICEID_AMD_MISC15     0x1603
 
@@ -86,6 +87,7 @@
        { VENDORID_AMD, DEVICEID_AMD_MISC0F },
        { VENDORID_AMD, DEVICEID_AMD_MISC10 },
        { VENDORID_AMD, DEVICEID_AMD_MISC11 },
+       { VENDORID_AMD, DEVICEID_AMD_MISC12 },
        { VENDORID_AMD, DEVICEID_AMD_MISC14 },
        { VENDORID_AMD, DEVICEID_AMD_MISC15 },
        { 0, 0 }

But the results don't look correct:
# sysctl -a | grep amdtemp
amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb4
dev.amdtemp.0.%desc: AMD CPU On-Die Thermal Sensors
dev.amdtemp.0.%driver: amdtemp
dev.amdtemp.0.%parent: hostb4
dev.amdtemp.0.sensor_offset: 0
dev.amdtemp.0.core0.sensor0: 8.5C

Probably that weird quirk, though the docs don't describe the issue in
enough detail:
     Instead, it specifies the processor temperature relative to the point at
     which the system must supply the maximum cooling for the processor's
     specified maximum case temperature and maximum thermal power
     dissipation'' according to BIOS and Kernel Developer's Guide (BKDG) for
     AMD Processors,

Which is what temp?  The url provided is just a list of docs..  Is it
at 50C that the max cooling needs to be supplied? 100C? 1000C?

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."
_______________________________________________
freebsd-amd64@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org"

----- End forwarded message -----
Comment 5 sasamotikomi 2015-02-19 19:28:29 UTC
Can this patch help?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194792
Comment 6 Johannes Lundberg 2018-05-24 12:06:14 UTC
amdtemp won't recognize my ryzen on ASRock A320M-HDV mobo.

CPU: AMD Ryzen 3 2200G with Radeon Vega Graphics     (3493.52-MHz K8-class CPU)
  Origin="AuthenticAMD"  Id=0x810f10  Family=0x17  Model=0x11  Stepping=0
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x7ed8320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
  AMD Features2=0x35c233ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX>
  Structured Extended Features=0x209c01a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  AMD Extended Feature Extensions ID EBX=0x1007<CLZERO,IRPerf,XSaveErPtr>
  SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
  TSC: P-state invariant, performance statistics

Where can I find the device id that should be added to the list?
Comment 7 Andriy Gapon freebsd_committer 2018-05-24 14:25:55 UTC
Is this bug now a catch all for all amdtemp issues?
Despite a very specific title?

Johannes, maybe it's worth to ask on mailing lists or forums first?
If no help there, then please open a new bug report.
Comment 8 Johannes Lundberg 2018-05-24 14:52:27 UTC
(In reply to Andriy Gapon from comment #7)
I skimmed through and it looked like it was about adding device id to support new hardware - which is much related to my case. In an attempt to reduce the number of open and forgotten bug reports, I reused this one. 

At a closer look, maybe it's a bit of mismatch.
Comment 9 Andriy Gapon freebsd_committer 2018-05-24 20:45:04 UTC
(In reply to Johannes Lundberg from comment #8)
I see.  OTOH, new IDs are going to keep appearing. I don't think that we should an eternal bug because of that.  I think that it's better to have actionable reports with small, well-defined scope.
So, I would like to close this bug report now.