From owner-freebsd-hackers@freebsd.org Mon Feb 6 10:22:01 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 500B1CD32CD for ; Mon, 6 Feb 2017 10:22:01 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 15B489BA for ; Mon, 6 Feb 2017 10:22:01 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cagQp-000AHp-4Q for freebsd-hackers@freebsd.org; Mon, 06 Feb 2017 13:21:59 +0300 Date: Mon, 6 Feb 2017 13:21:59 +0300 From: Slawa Olhovchenkov To: freebsd-hackers@freebsd.org Subject: Inactive memory Message-ID: <20170206102159.GD5366@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2017 10:22:01 -0000 What is 'Inactive' memory? Can I let is definitly availably for allocation (after some time)? Under some load I am got about 30GB of Inactive memory and I am prefer migrate this memory to ARC cache. Can I have assurance about freeing this memory under pressure? From owner-freebsd-hackers@freebsd.org Mon Feb 6 12:19:09 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7E03CD2C82 for ; Mon, 6 Feb 2017 12:19:09 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.18.14]) (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 90365F44 for ; Mon, 6 Feb 2017 12:19:09 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from [78.35.162.27] (helo=fabiankeil.de) by smtprelay02.ispgateway.de with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.84) (envelope-from ) id 1caiG8-0005U9-CO for freebsd-hackers@freebsd.org; Mon, 06 Feb 2017 13:19:04 +0100 Date: Mon, 6 Feb 2017 13:17:11 +0100 From: Fabian Keil To: freebsd-hackers@freebsd.org Subject: Re: Inactive memory Message-ID: <20170206131711.76fe19ed@fabiankeil.de> In-Reply-To: <20170206102159.GD5366@zxy.spb.ru> References: <20170206102159.GD5366@zxy.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/S/KiEkDC3mB4xT5c9GJfKTx"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2017 12:19:09 -0000 --Sig_/S/KiEkDC3mB4xT5c9GJfKTx Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Slawa Olhovchenkov wrote: > What is 'Inactive' memory? =46rom sys/vm/vm_page.h: /* * Each pageable resident page falls into one of four lists: * * free * Available for allocation now. * * cache * Almost available for allocation. Still associated with * an object, but clean and immediately freeable. * * The following lists are LRU sorted: * * inactive * Low activity, candidates for reclamation. * This is the list of pages that should be * paged out next. * * active * Pages that are "active" i.e. they have been * recently referenced. * */ A case-insensitive grep for "inactive" in the directory will result in a couple of additional relevant comments and implementation details. > Can I let is definitly availably for allocation (after some time)? > Under some load I am got about 30GB of Inactive memory and I am > prefer migrate this memory to ARC cache. >=20 > Can I have assurance about freeing this memory under pressure? While inactive memory is supposed to be freed under memory pressure, in vanilla FreeBSD the ARC may shrink to relieve memory pressure first. In extreme case the ARC may shrink to its limit while the inactive memory continues to grow. In ElectroBSD, this patch is supposed to address this: https://www.fabiankeil.de/sourcecode/electrobsd/ElectroBSD-r312620-6cfa243f= 1516/0239-sys-vm-Limit-the-inactive-pages-more-aggressively.diff You could give it a try to see if it helps for your workload. If you haven't already, you also may want to look at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D187594 Among other things, it contains a bunch of (conflicting) theories about how the system behaves under memory pressure. Fabian --Sig_/S/KiEkDC3mB4xT5c9GJfKTx Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTKUNd6H/m3+ByGULIFiohV/3dUnQUCWJhpRwAKCRAFiohV/3dU nf4cAJ4/eaiIiQqTvAAFTswZtzNPfo8IiQCgitYZJOCF5SUa+nzRpu3/LMoRgZ8= =fyaM -----END PGP SIGNATURE----- --Sig_/S/KiEkDC3mB4xT5c9GJfKTx-- From owner-freebsd-hackers@freebsd.org Mon Feb 6 13:05:25 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4342CCFA9F for ; Mon, 6 Feb 2017 13:05:25 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 A720BC5A for ; Mon, 6 Feb 2017 13:05:25 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1caiyv-000FGn-Et; Mon, 06 Feb 2017 16:05:21 +0300 Date: Mon, 6 Feb 2017 16:05:21 +0300 From: Slawa Olhovchenkov To: Fabian Keil Cc: freebsd-hackers@freebsd.org Subject: Re: Inactive memory Message-ID: <20170206130521.GE5366@zxy.spb.ru> References: <20170206102159.GD5366@zxy.spb.ru> <20170206131711.76fe19ed@fabiankeil.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170206131711.76fe19ed@fabiankeil.de> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2017 13:05:26 -0000 On Mon, Feb 06, 2017 at 01:17:11PM +0100, Fabian Keil wrote: > Slawa Olhovchenkov wrote: > > > What is 'Inactive' memory? > > From sys/vm/vm_page.h: > /* > * Each pageable resident page falls into one of four lists: > * > * free > * Available for allocation now. > * > * cache > * Almost available for allocation. Still associated with > * an object, but clean and immediately freeable. > * > * The following lists are LRU sorted: > * > * inactive > * Low activity, candidates for reclamation. > * This is the list of pages that should be > * paged out next. > * > * active > * Pages that are "active" i.e. they have been > * recently referenced. > * > */ > > A case-insensitive grep for "inactive" in the directory > will result in a couple of additional relevant comments > and implementation details. > > > Can I let is definitly availably for allocation (after some time)? > > Under some load I am got about 30GB of Inactive memory and I am > > prefer migrate this memory to ARC cache. > > > > Can I have assurance about freeing this memory under pressure? > > While inactive memory is supposed to be freed under memory > pressure, in vanilla FreeBSD the ARC may shrink to relieve > memory pressure first. In extreme case the ARC may shrink > to its limit while the inactive memory continues to grow. > > In ElectroBSD, this patch is supposed to address this: > https://www.fabiankeil.de/sourcecode/electrobsd/ElectroBSD-r312620-6cfa243f1516/0239-sys-vm-Limit-the-inactive-pages-more-aggressively.diff > You could give it a try to see if it helps for your workload. I am afraid this patch. > If you haven't already, you also may want to look at: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187594 > Among other things, it contains a bunch of (conflicting) > theories about how the system behaves under memory pressure. I am see some reports (in wild internet) about count as 'inactive' used memory in tmpfs. I am not sure about conversion this pages to free and ack this question. Thanks for URLs, I am try different patch for ARC. From owner-freebsd-hackers@freebsd.org Mon Feb 6 18:53:57 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45C29CD39CB; Mon, 6 Feb 2017 18:53:57 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mx1.etoilesoft.fr (mx1.etoilesoft.fr [52.57.51.18]) by mx1.freebsd.org (Postfix) with ESMTP id 10A8B1566; Mon, 6 Feb 2017 18:53:56 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mx1.etoilesoft.fr (localhost [127.0.0.1]) by mx1.etoilesoft.fr (Postfix) with ESMTP id 95E039D19F; Mon, 6 Feb 2017 18:54:08 +0000 (UTC) Received: from [172.20.15.189] (localhost [127.0.0.1]) (Authenticated sender: auryn@zirakzigil.org) by mx1.etoilesoft.fr (Postfix) with ESMTPA id 262019D19D; Mon, 6 Feb 2017 18:54:08 +0000 (UTC) To: "freebsd-net@freebsd.org" , freebsd-hackers@freebsd.org From: Giulio Ferro Subject: Duplicate MAC addresses in VNET epair interaces Message-ID: <472069af-0f9d-d830-064b-2d984a5774ae@zirakzigil.org> Date: Mon, 6 Feb 2017 19:53:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2017 18:53:57 -0000 Hi all, Setup: 11.0-STABLE FreeBSD 11.0-STABLE #0 r312338: Tue Jan 17 12:29:38 UTC 2017 I've set up two freebsd hosts, each of which has a single VNET jail. On each host I've created 2 epair interfaces. Host A - epair0a, epair1a on the host - epair0b, epair1b on the jail Host B - epair0a, epair10a on the host - epair0b, epair10b on the jail What I noticed is that on both hosts, each epair interface has the same MAC address: Host A: root@xxx:~ # ifconfig epair0a epair0a: flags=8843 metric 0 mtu 1500 options=8 ether 02:ff:e0:00:03:0a inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 nd6 options=29 media: Ethernet 10Gbase-T (10Gbase-T ) status: active groups: epair root@xxx:~ # ifconfig epair1a epair1a: flags=8943 metric 0 mtu 1500 options=8 ether 02:ff:e0:00:05:0a nd6 options=29 media: Ethernet 10Gbase-T (10Gbase-T ) status: active groups: epair Host B: root@yyy:~ # ifconfig epair0a epair0a: flags=8843 metric 0 mtu 1500 options=8 ether 02:ff:e0:00:03:0a inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 nd6 options=29 media: Ethernet 10Gbase-T (10Gbase-T ) status: active groups: epair root@yyy:~ # ifconfig epair10a epair10a: flags=28943 metric 0 mtu 1500 options=8 ether 02:ff:e0:00:05:0a nd6 options=29 media: Ethernet 10Gbase-T (10Gbase-T ) status: active groups: epair (same behavior on the epair interfaces on the jail side) As you can see, the mac addresses seems to depend on the order of the creation of the epair, not on the name or address This is a potentially bad behavior, because if I want to bridge say epair1a on A with epair10a on B with a VPN or a physical connection giving 192.168.1.1 to epair1b and 192.168.1.2 to epair10b, I won't be able to make them talk to each other since they have the same MAC address. My question is: is this a bug or something I'm doing wrong? If there any workaround I can use? Thanks Giulio From owner-freebsd-hackers@freebsd.org Mon Feb 6 19:53:33 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9D06CD3ED0; Mon, 6 Feb 2017 19:53:33 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3EBDF1DA3; Mon, 6 Feb 2017 19:53:33 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 93F2525D38A4; Mon, 6 Feb 2017 19:53:19 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id A8B4BD1F855; Mon, 6 Feb 2017 19:53:18 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id 1fU8_GgIFP65; Mon, 6 Feb 2017 19:53:16 +0000 (UTC) Received: from [10.111.64.116] (unknown [IPv6:fde9:577b:c1a9:4410:9b2:9b63:1d3b:690d]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id F325BD1F828; Mon, 6 Feb 2017 19:53:14 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Giulio Ferro" Cc: "freebsd-net@freebsd.org" , freebsd-hackers@freebsd.org Subject: Re: Duplicate MAC addresses in VNET epair interaces Date: Mon, 06 Feb 2017 19:53:12 +0000 Message-ID: <8B1A6A6C-4280-4B96-9D60-FC9E7EEE2222@lists.zabbadoz.net> In-Reply-To: <472069af-0f9d-d830-064b-2d984a5774ae@zirakzigil.org> References: <472069af-0f9d-d830-064b-2d984a5774ae@zirakzigil.org> MIME-Version: 1.0 X-Mailer: MailMate (2.0BETAr6076) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2017 19:53:33 -0000 On 6 Feb 2017, at 18:53, Giulio Ferro wrote: > Hi all, > > > Setup: > > 11.0-STABLE FreeBSD 11.0-STABLE #0 r312338: Tue Jan 17 12:29:38 UTC > 2017 > > > I've set up two freebsd hosts, each of which has a single VNET jail. > > On each host I've created 2 epair interfaces. > > Host A > > - epair0a, epair1a on the host > > - epair0b, epair1b on the jail > > > Host B > > - epair0a, epair10a on the host > > - epair0b, epair10b on the jail > > > What I noticed is that on both hosts, each epair interface has the > same MAC address: > …> > > (same behavior on the epair interfaces on the jail side) > > > As you can see, the mac addresses seems to depend on the order of the > creation of the epair, not on the name or address > > > This is a potentially bad behavior, because if I want to bridge say > epair1a on A with epair10a on B with a VPN or > > a physical connection giving 192.168.1.1 to epair1b and 192.168.1.2 to > epair10b, I won't be able to make them > > talk to each other since they have the same MAC address. > > > My question is: is this a bug or something I'm doing wrong? If there > any workaround I can use? From the man page: Like any other Ethernet interface, an epair needs to have a network address. Each epair will be assigned a locally administered address by default, that is only guaranteed to be unique within one network stack. To change the default addresses one may use the SIOCSIFADDR ioctl(2) or ifconfig(8) utility. I thought someone patched it a few years ago to have a pseudo-random part to make collisions less likely and use the FreeBSD vendor space, but it seems that never happened for epair (or didn’t make it into the tree). ifconfig epair[ab] ether 02:xx:xx:xx:xx is your friend for now. /bz From owner-freebsd-hackers@freebsd.org Tue Feb 7 20:01:27 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81CCFCD580A for ; Tue, 7 Feb 2017 20:01:27 +0000 (UTC) (envelope-from trafdev@mail.ru) Received: from fallback2.mail.ru (fallback2.mail.ru [94.100.179.22]) by mx1.freebsd.org (Postfix) with ESMTP id 15BEDBC0 for ; Tue, 7 Feb 2017 20:01:26 +0000 (UTC) (envelope-from trafdev@mail.ru) Received: from smtp2.mail.ru (smtp2.mail.ru [94.100.179.91]) by fallback2.mail.ru (mPOP.Fallback_MX) with ESMTP id 8AD1C81A9002 for ; Fri, 3 Feb 2017 03:14:52 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=Content-Type:MIME-Version:Date:Message-ID:Subject:From:To; bh=VjUxg5aqKPPv5ocyAxjuRGoq8rT9B4hAV2OznSjtgak=; b=D3GWLiY6IPsdocksqukJwENGBTkWnKsrE4bYWaNvvn2cbqGOhxJVzDdtZxxk7fttL0onctrrkoI66CngemhcCU0kNJeWJzaeNbvW1kp31pn/CpEqzQ+uOIWKVzoferayIJvAiBP4a7+5h+pE5B64GfK6/VX8R75M2xfUWlf1eB8=; Received: from c-50-131-6-44.hsd1.ca.comcast.net ([50.131.6.44]:23716 helo=[192.168.1.116]) by smtp2.mail.ru with esmtpa (envelope-from ) id 1cZRWV-0003Hg-3t for freebsd-hackers@freebsd.org; Fri, 03 Feb 2017 03:14:43 +0300 To: freebsd-hackers@freebsd.org From: trafdev Subject: Strange hw.pci.enable_msi boot effect Message-ID: <41112505-b0bf-4fec-8e37-8192ca9d8e72@mail.ru> Date: Thu, 2 Feb 2017 16:14:38 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Authentication-Results: smtp2.mail.ru; auth=pass smtp.auth=trafdev@mail.ru smtp.mailfrom=trafdev@mail.ru X-E1FCDC63: 0D19BE9587B94E4CFC249DFBD6503B368472923344694FB0 X-E1FCDC64: 100A53D0D47AB18415603296ED6CA5E25538E8C2FBAFF0BA8C23C411F30400B5 X-Mailru-Sender: 3CBCA9EAC7B55374C185D75874726954ABB5135293815AAB1DAC718FB8BC1A97DA590893EA273EA8 X-Mras: OK Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2017 20:01:27 -0000 Hi. I've noticed that following two settings in a /boot/loader.conf: hw.pci.enable_msi="0" hw.pci.enable_msix="0" cause boot process to crash with: Error: cannot find the pool label for zroot mounting from zfs failed with error 5 How these options might affect zroot mounting phase? Thanks! From owner-freebsd-hackers@freebsd.org Tue Feb 7 20:11:39 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93DE9CD5B80 for ; Tue, 7 Feb 2017 20:11:39 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 3E3E01041 for ; Tue, 7 Feb 2017 20:11:39 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-qt0-x22c.google.com with SMTP id x49so145566079qtc.2 for ; Tue, 07 Feb 2017 12:11:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MkpHxZo7xE1e1r/wV6AZSPKb880xl+/el/MMewYT9BE=; b=ocUH3yJ25iHg0SaxgLjyECZ6ROLI/OS2QScfzlQuUOgdWudtIZFHL51ZPQyk6G61EL FChd+W8cLL+42Scsoi35k/hFg+gM96BqOfB34KDwctFgjGh9gXgXp8QZF+iKOjLvOW6f G3mxjD1c2YEFL18gChja3omdIOec8ExpJGzuWtUMxwFVC9FcLiYm757uJMkD7XR2dQFO IRYK+QSeRNhxBzO/GCgJEqBYtudb2K37sjj7sG20Kb9hZo4N+f9qtgNvKJcMSsDQdSid LC/Mtu4No2ji/n9VVY43dd2YCYQvRsBahyJ3kT6O4LAAjzxRjlEG1zC8X7x/OMfYqoPL iuIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MkpHxZo7xE1e1r/wV6AZSPKb880xl+/el/MMewYT9BE=; b=M6CQ7UyPHHFXpPaPigIo2W6JEJtsvoPKnHQELHtloFneTMHtgCPBloNKYZIPJxepUl LHwRgCB4ISwe9IiQ/9n5l+IeRMtU4WUwv2dNrWe3/U8yS1C9K6BDeFLBxsxFhxhKqDt6 Eh7bGorGYTx+Uc9/yIUVegf9TPmlHL09DEihnMRLUqjUby+c9PD1hZemTRXYas5DWZL0 9vj5K0Qxl58qaLT25619lAB0/2T/HYhBmrLpfA1zm5aLKYoyRmMDb9LdlMKKe4Q4Fsxk iH/jE9mnlyLgBZP5JVttvjbn2+VqFrbl5lYH2gQ28HryvtjPGtcdafh9Ha0P5miqnmGF NSyw== X-Gm-Message-State: AMke39no7XwOnPoGiKB/muSpkh32CoRDuuJqh8GHphfOtq4cbLAL2STZxxlGOgwWCh3+cieNdoVKuffSbUUwrA== X-Received: by 10.200.36.162 with SMTP id s31mr15950984qts.231.1486498298464; Tue, 07 Feb 2017 12:11:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.28.202 with HTTP; Tue, 7 Feb 2017 12:11:37 -0800 (PST) In-Reply-To: <41112505-b0bf-4fec-8e37-8192ca9d8e72@mail.ru> References: <41112505-b0bf-4fec-8e37-8192ca9d8e72@mail.ru> From: Freddie Cash Date: Tue, 7 Feb 2017 12:11:37 -0800 Message-ID: Subject: Re: Strange hw.pci.enable_msi boot effect To: trafdev Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2017 20:11:39 -0000 On Thu, Feb 2, 2017 at 4:14 PM, trafdev via freebsd-hackers < freebsd-hackers@freebsd.org> wrote: > Hi. > > I've noticed that following two settings in a /boot/loader.conf: > > hw.pci.enable_msi=3D"0" > hw.pci.enable_msix=3D"0" > > cause boot process to crash with: > > Error: > cannot find the pool label for zroot > mounting from zfs failed with error 5 > > How these options might affect zroot mounting phase? > Thanks! > =E2=80=8BBest guess would be that the kernel can't configure your storage a= dapter in non-MSI mode, so it can't find any of the disks to mount the pool from. Hit Scroll-Lock, and use the arrow keys to scroll up, and see if there are any messages about the storage adapters.=E2=80=8B --=20 Freddie Cash fjwcash@gmail.com