Date: Mon, 09 Apr 2018 12:37:26 -0700 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Mark Millard <marklmi26-fbsd@yahoo.com>, FreeBSD Hackers <freebsd-hackers@freebsd.org>, freebsd-amd64@freebsd.org Subject: Re: "Could not allocate I/O space" and "intsmb0 attach returned 6" in a under-Hyper-V context on Ryzen Threadripper: Is this expected? Message-ID: <2644434.8Ktpdmy6i5@ralph.baldwin.cx> In-Reply-To: <621E84E6-D42C-4778-B028-AF3E1042CE7D@yahoo.com> References: <621E84E6-D42C-4778-B028-AF3E1042CE7D@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, April 01, 2018 02:23:36 PM Mark Millard wrote: > For: > > # 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. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2644434.8Ktpdmy6i5>