Date: Tue, 20 Apr 2021 13:59:22 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 255263] amdsmn and amdtemp not loaded by devmatch on AMD Epyc Message-ID: <bug-255263-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255263 Bug ID: 255263 Summary: amdsmn and amdtemp not loaded by devmatch on AMD Epyc Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: olivier@freebsd.org 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" -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255263-227>