"Could not allocate I/O space" and "intsmb0 attach returned 6" in a under-Hyper-V context on Ryzen Threadripper: Is this expected?
jhb at freebsd.org
Mon Apr 9 19:52:44 UTC 2018
On Sunday, April 01, 2018 02:23:36 PM Mark Millard wrote:
> # uname -apKU
> FreeBSD FBSDHUGE 12.0-CURRENT FreeBSD 12.0-CURRENT r331831M amd64 amd64 1200060 1200060
> I get:
> . . .
> pci0: <bridge> at device 7.3 (no driver attached)
> . . .
> intsmb0: <Intel PIIX4 SMBUS Interface> at device 7.3 on pci0
> intsmb0: Could not allocate I/O space
> device_attach: intsmb0 attach returned 6
> on a Ryzen Threadripper 1950X where FreeBSD is being run under
> Hyper-V (on a Windows 10 Pro machine).
> Is this expected? Did I misconfigure something in Hyper-V?
That seems like an odd device to have for an AMD machine. I suspect that this has never
worked and the module started auto-loading due to devmatch.
More information about the freebsd-amd64