Bug 255263 - amdsmn and amdtemp not loaded by devmatch on AMD Epyc
Summary: amdsmn and amdtemp not loaded by devmatch on AMD Epyc
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Some People
Assignee: Warner Losh
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-20 13:59 UTC by Olivier Cochard
Modified: 2021-04-20 14:00 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Cochard freebsd_committer 2021-04-20 13:59:22 UTC
My AMD Epyc has an amdsmn and amdtemp:

$ pciconf -l | grep 0x1480
hostb0@pci0:192:0:0:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1480 subvendor=0x1022 subdevice=0x1450
hostb8@pci0:128:0:0:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1480 subvendor=0x1022 subdevice=0x1450
hostb16@pci0:64:0:0:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1480 subvendor=0x1022 subdevice=0x1450
hostb24@pci0:0:0:0:     class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1480 subvendor=0x1022 subdevice=0x1450

But devmatch isn't able to load them

"because there is a mis-match between hostb and pci."

and

"So this driver attaches to the various host bridges. These bridges have drivers. So, devmatch won’t consider even loading this driver. If we fix the pci -> hostb message, it highlights a mismatch between pci vs hostb in the module_pnp_info tables. This driver is a bit unique and only adds itself as a child to an otherwise passive hostb0 device"