From owner-freebsd-amd64@freebsd.org Sun Apr 8 16:39:41 2018 Return-Path: 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 E3AC3F8EF1B for ; Sun, 8 Apr 2018 16:39:40 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic316-8.consmr.mail.gq1.yahoo.com (sonic316-8.consmr.mail.gq1.yahoo.com [98.137.69.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6A09E70C1C for ; Sun, 8 Apr 2018 16:39:40 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: u_Ux55QVM1k4XIc7bIAbet2wS8WhBYeQq1NlNCkjUfQ9dWprhhpwLbH4cuFJozg 7kV9AMEjQC7LniK8U2KIPs5gaI1Dafmdl.SbI8bbjj5n8ZR82tFqvcIHG1lt2dONdwNjpFUkHFgP SF7QgiUpk2JjT4Jh8C1SU1MMz.wrenDoIMTh5ke8PBrFfrzHxx8rQ.R1EQU1btpqeKMc05vRbGax O3tRirwCdJlOgsU8ng.4WooHwNNqVjZZascZug1Tx_Ra0jlaAZk5Z95SRjWtb36SVxV4doz7PBVv zCMnDFUNfmOi34O2KOJQGvqeObKw0tGaloxviCDil9uWFBuStt92zxGUboGzvTC1EzCX1aAJCRv4 Z1hkY76p9Cln5iNNoW0RY4NZtT_n_ZopGTggcNgkGEzCuLtgBmV8pAFyjM5Qipp.o5shTAnrlIbA LPM.y8uv9hekIvw1dnUMqG0keoU.fuy0fn7XK2GOkNoi8w2bPGkldqak0dDILKaqF45CUEAhNQla sUO8BLwY7gqIW7a6tAVSdvGeQrfAKmXml5N36 Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.gq1.yahoo.com with HTTP; Sun, 8 Apr 2018 16:39:38 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp431.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID d9f02034e3b178c021c97b2e13312602; Sun, 08 Apr 2018 16:29:26 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Ryzen Threadripper, Hyper-V, and NUMA vs. DIMMs: 3 DIMMs on each side seems to always be in "Local" mode, not "Distributed" Message-Id: Date: Sun, 8 Apr 2018 09:29:25 -0700 To: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org, FreeBSD Current X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2018 16:39:41 -0000 Context: Ryzen Threadripper 1950X under Windows 10 Pro with Hyper-V (used to run FreeBSD). In experimenting with switching a Threadripper 1950X to have ECC RAM I discovered: A) The maximum ECC memory it would put to use was 96 GiBytes (3 DIMMs on each side, a 4th on each side was recognized but was ignored/disabled if present). B) AMD Ryzen Master classified the 96 GiByte configurations (with or without the ignored DIMMs) as "Local" without an ability switch to "Distributed". C) The downloaded Windows CoreInfo.exe utility agreed on there being 2 NUMA nodes. D) As did the result of the User Hardware Topology button in the Hyper-V Processor > NUMA settings: On a single virtual non-uniform memory architecture node: Maximum number of processors : 16 Maximum amount of memory (MB) : 48070 Maximum NUMA nodes allowed on a socket: 2 Only 1 socket. E) The CoreInfo.exe quick "Approximate Cross-NUMA Node Access Cost (relative to fastest)" tends to show the 4 numbers varying from 1.0 to 1.7 when retried repeatedly. An oddity is that sometimes the 1.0's are between 00 and 01, in fact this seems usual, and normally at most one 1.0 exists. The 00 row seems to always have the smaller numbers. An example: 00 01 00: 1.2 1.0 01: 1.3 1.5 I had no original intent of playing with NUMA but I figured that the Threadripper could be configured for such, and even has configurations that apparently require such as far as AMD Ryzen Master is concerned, could be of interest and possible use for folks testing FreeBSD NUMA support. Since I'd done nothing to build a kernel with NUMA enabled, FreeBSD 12.0 under Hyper-V did not see the NUMA structure from (D). One thing that did show during booting was getting 4 lines of: "SRAT: Ignoring memory at addr" instead of 2. === Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-amd64@freebsd.org Mon Apr 9 12:52:02 2018 Return-Path: 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 6A842FA1E59 for ; Mon, 9 Apr 2018 12:52:02 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F34EC861D3 for ; Mon, 9 Apr 2018 12:52:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AFDC5FA1E53; Mon, 9 Apr 2018 12:52:01 +0000 (UTC) Delivered-To: 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 9C129FA1E52; Mon, 9 Apr 2018 12:52:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 11A4E861AF; Mon, 9 Apr 2018 12:52:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w39Cpnmt097720 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 9 Apr 2018 15:51:53 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w39Cpnmt097720 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w39CpnRg097719; Mon, 9 Apr 2018 15:51:49 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 9 Apr 2018 15:51:49 +0300 From: Konstantin Belousov To: Yoshihiro Ota Cc: Bruce Evans , Dimitry Andric , current@FreeBSD.org, amd64@FreeBSD.org Subject: Re: i386 4/4 change Message-ID: <20180409125149.GA1774@kib.kiev.ua> References: <20180331102901.GN1774@kib.kiev.ua> <20180401004833.L3296@besplex.bde.org> <3FAD36FD-FA90-49F6-9141-B9CCCCA2BF00@FreeBSD.org> <20180401151124.G893@besplex.bde.org> <20180409082213.1ca1fc0cd589bafa98a4fead@j.email.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180409082213.1ca1fc0cd589bafa98a4fead@j.email.ne.jp> User-Agent: Mutt/1.9.4 (2018-02-28) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2018 12:52:02 -0000 On Mon, Apr 09, 2018 at 08:22:13AM -0400, Yoshihiro Ota wrote: > What is the current status of this? > > Based on SVN history, it doesn't look https://reviews.freebsd.org/D14633 has been merged/commited yet. I fixed bugs reported by Bruce. Right now the patch is waiting for some other testing to finish, before the final retest. > > I can try after I recover from disk crahes. > I expect I need few more days to restore. > > Will this retire PAE option? The patch is ortogonal to PAE. From owner-freebsd-amd64@freebsd.org Mon Apr 9 12:32:30 2018 Return-Path: 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 14700FA0B4A for ; Mon, 9 Apr 2018 12:32:30 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A7FFA7B71D for ; Mon, 9 Apr 2018 12:32:29 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: by mailman.ysv.freebsd.org (Postfix) id 667BDFA0B48; Mon, 9 Apr 2018 12:32:29 +0000 (UTC) Delivered-To: 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 2BEA9FA0B46; Mon, 9 Apr 2018 12:32:29 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from mail01.asahi-net.or.jp (mail01.asahi-net.or.jp [202.224.55.13]) by mx1.freebsd.org (Postfix) with ESMTP id B10E67B6F3; Mon, 9 Apr 2018 12:32:27 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from localhost (pool-108-53-56-94.nwrknj.fios.verizon.net [108.53.56.94]) (Authenticated sender: NR2Y-OOT) by mail01.asahi-net.or.jp (Postfix) with ESMTPSA id 1056C57F70; Mon, 9 Apr 2018 21:22:40 +0900 (JST) Date: Mon, 9 Apr 2018 08:22:13 -0400 From: Yoshihiro Ota To: Bruce Evans Cc: Dimitry Andric , Konstantin Belousov , current@FreeBSD.org, amd64@FreeBSD.org Subject: Re: i386 4/4 change Message-Id: <20180409082213.1ca1fc0cd589bafa98a4fead@j.email.ne.jp> In-Reply-To: <20180401151124.G893@besplex.bde.org> References: <20180331102901.GN1774@kib.kiev.ua> <20180401004833.L3296@besplex.bde.org> <3FAD36FD-FA90-49F6-9141-B9CCCCA2BF00@FreeBSD.org> <20180401151124.G893@besplex.bde.org> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; i386-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 09 Apr 2018 13:52:40 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2018 12:32:30 -0000 What is the current status of this? Based on SVN history, it doesn't look https://reviews.freebsd.org/D14633 has been merged/commited yet. I can try after I recover from disk crahes. I expect I need few more days to restore. Will this retire PAE option? Thanks, Hiro On Sun, 1 Apr 2018 17:05:03 +1000 (EST) Bruce Evans wrote: > > On Sun, 1 Apr 2018, Dimitry Andric wrote: > > > On 31 Mar 2018, at 17:57, Bruce Evans wrote: > >> > >> On Sat, 31 Mar 2018, Konstantin Belousov wrote: > >> > >>> the change to provide full 4G of address space for both kernel and > >>> user on i386 is ready to land. The motivation for the work was to both > >>> mitigate Meltdown on i386, and to give more breazing space for still > >>> used 32bit architecture. The patch was tested by Peter Holm, and I am > >>> satisfied with the code. > >>> > >>> If you use i386 with HEAD, I recommend you to apply the patch from > >>> https://reviews.freebsd.org/D14633 > >>> and report any regressions before the commit, not after. Unless > >>> a significant issue is reported, I plan to commit the change somewhere > >>> at Wed/Thu next week. > >>> > >>> Also I welcome patch comments and reviews. > >> > >> It crashes at boot time in getmemsize() unless booted with loader which > >> I don't want to use. > > > For me, it at least compiles and boots OK, but I'm one of those crazy > > people who use the default boot loader. ;) > > I found a quick fix and sent it to kib. (2 crashes in vm86 code for memory > sizing. This is not called if loader is used && the system has smap. Old > systems don't have smap, so they crash even if loader is used.) > > > I haven't yet run any performance tests, I'll try building world and a > > few large ports tomorrow. General operation from the command line does > > not feel "sluggish" in any way, however. > > Further performance tests: > - reading /dev/zero using tinygrams is 6 times slower > - read/write of a pipe using tinygrams is 25 times slower. It also gives > unexpected values in wait statuses on exit, hopefully just because the > bug is in the test program is exposed by the changed timing (but later > it also gave SIGBUS errors). This does a context switch or 2 for every > read/write. It now runs 7 times slower using 2 4.GHz CPUs than in > FreeBSD-5 using 1 2.0 GHz CPU. The faster CPUs and 2 of them used to > make it run 4 times faster. It shows another slowdown since FreeBSD-5, > and much larger slowdowns since FreeBSD-1: > > 1996 FreeBSD on P1 133MHz: 72k/s > 1997 FreeBSD on P1 133MHz: 44k/s (after dyson's opts for large sizes) > 1997 Linux on P1 133MHz: 93k/s (simpler is faster for small sizes) > 1999 FreeBSD on K6 266MHz: 129k/s > 2018 FBSD-~5 on AthXP 2GHz: 696k/s > 2018 FreeBSD on i7 2x4GHz: 2900k/s > 2018 FBSD4+4 on i7 2x4GHz: 113k/s (faster than Linux on a P1 133MHz!!) > > Netblast to localhost has much the same 6 times slowness as reading > /dev/zero using tinygrams. This is the slowdown for syscalls. > Tinygrams are hard to avoid for UDP. Even 1500 bytes is a tinygram > for /dev/zero. Without 4+4, localhost is very slow because it does > a context switch or 2 for every packet (even with 2 CPUs when there is > no need to switch). Without 4+4 this used to cost much the same as the > context switches for the pipe benchmark. Now it costs relatively much > less since (for netblast to localhost) all of the context switches are > between kernel threads. > > The pipe benchmark uses select() to avoid busy-waiting. That was good > for UP. But for SMP with just 2 CPUs, it is better to busy-wait and > poll in the reader and writer. > > netblast already uses busy-waiting. It used to be a bug that select() > doesn't work on sockets, at least for UDP, so blasting using busy-waiting > is the only possible method (timeouts are usually too coarse-grained to > go as fast as blasting, and if they are fine-grained enough to go fast > then they are not much better than busy-waiting with time wasted for > setting up timeouts). SMP makes this a feature. It forces use of busy- > waiting, which is best if you have a CPU free to run it and this method > doesn't take to much power. > > Context switches to task queues give similar slowness. This won't be > affected by 4+4 since task queues are in the kernel. I don't like > networking in userland since it has large syscall and context switch > costs. Increasing these by factors of 6 and 25 doesn't help. It > can only be better by combining i/o in a way that the kernel neglects > to do or which is imposed by per-packet APIs. Slowdown factors of 6 > or 25 require the combined i/o to be 6 or 25 larger to amortise the costs. > > Bruce > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-amd64@freebsd.org Mon Apr 9 19:52:44 2018 Return-Path: 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 To: freebsd-current@freebsd.org Cc: Mark Millard , FreeBSD Hackers , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: at device 7.3 (no driver attached) > . . . > intsmb0: 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 From owner-freebsd-amd64@freebsd.org Tue Apr 10 05:32:24 2018 Return-Path: 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 0E2E3FA2001; Tue, 10 Apr 2018 05:32:24 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f65.google.com (mail-lf0-f65.google.com [209.85.215.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C8EC7ED3F; Tue, 10 Apr 2018 05:32:23 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f65.google.com with SMTP id v207-v6so9811927lfa.10; Mon, 09 Apr 2018 22:32:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=6KRrdrSy1hA/sVZKmDI4gfDh7/MsBVWBc20gVbAOczM=; b=nyk2/O+3Biv6OMA2C9A8I7Ea9r2uSZbwn4mulBOb6aZS84DhHw8s+RATfYNMj/Q5Bb CPNHCi9zdfkIbmORcwK09clCl2DruhTIPGDyvnXV/4W/SPKEUcMFvH/NY55NgKF5eNHH L/0Xa0rlk4kPIOXE6DiWvtBIXQbyM7DJVQM8Cnf6R+is7mq7ZxGb44fIOckiyKcemo1T 9cDWLGBr+ebyhC3Wvf71XROrAjo/v6Xgdj3X7q0B0P4YoGF1eNnQWm+l/YBaVhLl18ob 4tBsp4pL++jmJG/guU3irtCKa2F9tUpDWFV2UAyRyZz+X7dcvkEEy1rxtP6/g8sqyzJO bkuA== X-Gm-Message-State: ALQs6tCABQ0Vtjvh6otFb6OyNcy9R3J2+vh3oKVKyLtXB1obCeSuoXle naz8AEkKxN9rWhqx1qBFq6fqC4oq X-Google-Smtp-Source: AIpwx49LJkG5AU+7I3pvO6tMLkBC4D8Ooh0oS49+1/MUPGtE47WIRHFwv5EkxRjHyzHQKi/H7Cuo8w== X-Received: by 2002:a19:d9d4:: with SMTP id s81-v6mr1011002lfi.49.1523338336228; Mon, 09 Apr 2018 22:32:16 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id r25sm335527ljc.8.2018.04.09.22.32.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Apr 2018 22:32:15 -0700 (PDT) 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? To: John Baldwin , freebsd-current@freebsd.org Cc: FreeBSD Hackers , freebsd-amd64@freebsd.org References: <621E84E6-D42C-4778-B028-AF3E1042CE7D@yahoo.com> <2644434.8Ktpdmy6i5@ralph.baldwin.cx> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <2a03f32b-34f9-7fcb-8d4d-94bd7a8d4290@FreeBSD.org> Date: Tue, 10 Apr 2018 08:32:13 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <2644434.8Ktpdmy6i5@ralph.baldwin.cx> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 10 Apr 2018 10:39:14 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2018 05:32:24 -0000 On 09/04/2018 22:37, John Baldwin wrote: > 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: at device 7.3 (no driver attached) >> . . . >> intsmb0: 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). Note the above. >> Is this expected? Did I misconfigure something in Hyper-V? > > That seems like an odd device to have for an AMD machine. Except that this is not an AMD machine but a Hyper-V? (And even if that were a physical AMD machine the driver would not be odd for it as the driver supports AMD chipsets that provide SMBus controllers compatible with PIIX4). Mark provided the following information in his post: >> # pciconf -l -v 0:0:7:3 >> none0@pci0:0:7:3: class=0x068000 card=0x00000000 chip=0x71138086 rev=0x02 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82371AB/EB/MB PIIX4 ACPI' >> class = bridge My guess is that Hyper-V's emulation of PIIX4 is not complete or correct with respect to the SMBus controller. And, as I am sure that Hyper-V does not emulate any SMBus slaves anyway, it would be completely useless. > I suspect that this has never > worked and the module started auto-loading due to devmatch. This must be true. -- Andriy Gapon From owner-freebsd-amd64@freebsd.org Thu Apr 12 07:44:18 2018 Return-Path: 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 8A966F9E21C for ; Thu, 12 Apr 2018 07:44:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1D28C6FBE2 for ; Thu, 12 Apr 2018 07:44:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C885EF9E1FF; Thu, 12 Apr 2018 07:44:17 +0000 (UTC) Delivered-To: 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 B48FBF9E1FB for ; Thu, 12 Apr 2018 07:44:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D5236FBDF for ; Thu, 12 Apr 2018 07:44:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 79D3A26DF8 for ; Thu, 12 Apr 2018 07:44:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3C7iGPr073486 for ; Thu, 12 Apr 2018 07:44:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3C7iGle073485 for amd64@FreeBSD.org; Thu, 12 Apr 2018 07:44:16 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: amd64@FreeBSD.org Subject: [Bug 209421] Processes hangs in D state, suspfs or vofflock wchan under FreeBSD 10.X-11.X Date: Thu, 12 Apr 2018 07:44:15 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: work+freebsd@vvv.kiev.ua X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 07:44:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209421 --- Comment #12 from vvv --- vfs.lookup_shared=3D0 didn't help. Trying to disable journaling and leave p= lain SU. --=20 You are receiving this mail because: You are on the CC list for the bug.=