From owner-freebsd-amd64@freebsd.org  Mon Apr  9 19:52:44 2018
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3020F9E28B;
 Mon,  9 Apr 2018 19:52:44 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 66A476EB7F;
 Mon,  9 Apr 2018 19:52:44 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215])
 by mail.baldwin.cx (Postfix) with ESMTPSA id 9053110AFD6;
 Mon,  9 Apr 2018 15:52:43 -0400 (EDT)
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?
Date: Mon, 09 Apr 2018 12:37:26 -0700
Message-ID: <2644434.8Ktpdmy6i5@ralph.baldwin.cx>
User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; )
In-Reply-To: <621E84E6-D42C-4778-B028-AF3E1042CE7D@yahoo.com>
References: <621E84E6-D42C-4778-B028-AF3E1042CE7D@yahoo.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3
 (mail.baldwin.cx); Mon, 09 Apr 2018 15:52:43 -0400 (EDT)
X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx
X-Virus-Status: Clean
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Apr 2018 19:52:44 -0000

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