From owner-freebsd-stable@freebsd.org Sun Mar 18 16:33:24 2018 Return-Path: Delivered-To: freebsd-stable@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 5F2CAF615C8 for ; Sun, 18 Mar 2018 16:33:24 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BAD9579E08 for ; Sun, 18 Mar 2018 16:33:23 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from [192.168.243.11] ([192.168.243.11]) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTP id w2IGXJeC061230 for ; Sun, 18 Mar 2018 21:33:19 +0500 (YEKT) (envelope-from emz@norma.perm.ru) To: freebsd-stable@freebsd.org From: "Eugene M. Zheganin" Subject: HAST, configuration, this actually looks insane Message-ID: Date: Sun, 18 Mar 2018 21:33:20 +0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Language: ru Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 16:33:24 -0000 Hi, I'm trying to configure a HAST on FreeBSD, and suddenly it appears to be a mind-breaking procedure. I totally don't get it, thus it doesn't work, dumps cores and behaves weirdly. First of all, in an existing configuration files paradigm, used widely in the whole IT industry, the local view is usually described, and then remote mentioned. Here both local and remote views are described and the configuration file (and they aren't named explicitely local and remote since they are both "remote"), like I understand the handbook article, must be _the_same_ on both nodes. So, given that the sections are named arbitrarily, the local hostname isn't mentioned or linked anywhere - how do I configure it considering that I have _different_ GEOM providers of different machines ? So, let's consider I have written this configutaion file: resource hasta {     on gw0 { local /dev/ada2p3 remote 192.168.0.247     }     on gw1 { local /dev/ada0p4 remote 192.168.0.248     } } resource hastb {     on gw0 { local /dev/ada3p3 remote 192.168.0.247     }     on gw1 {              local /dev/ada1p4 remote 192.168.0.248     } } The main question which IP do I mention where ? As far as I understand I should mention "remote" IP in the "local" device block, and vice-versa, but first of all - this doesn't work (dumps cores, complains bout FIFOs, and so on ) - second of all - how the hastd itself finds who's local and who's remote ? Thank god I have a GEOM configuration which cannot be applied on both nodes, so only the correct node wouyld have the GEOM provider mentions - otherwise I suggest this would corrupt my data and make a total mess of it. With thsi configuration file hastd doesn't work. "create" stage goes smoothly, but then on one node (the one with /dev/ada1p4 and /dev/ada0p4) hastd just loops crashing: Mar 18 20:48:47 gw1 hastd[92215]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Mar 18 20:48:47 gw1 hastd[92215]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Mar 18 20:48:47 gw1 kernel: pid 92215 (hastd), uid 0: exited on signal 6 (core dumped) Mar 18 20:48:52 gw1 hastd[92204]: [hasta] (primary) Worker process killed (pid=92215, signal=6). Mar 18 20:48:53 gw1 hastd[92222]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Mar 18 20:48:53 gw1 hastd[92222]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Mar 18 20:48:53 gw1 kernel: pid 92222 (hastd), uid 0: exited on signal 6 (core dumped) Mar 18 20:48:58 gw1 hastd[92204]: [hasta] (primary) Worker process killed (pid=92222, signal=6). Mar 18 20:48:59 gw1 hastd[92223]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Mar 18 20:48:59 gw1 hastd[92223]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Mar 18 20:48:59 gw1 kernel: pid 92223 (hastd), uid 0: exited on signal 6 (core dumped) Mar 18 20:49:01 gw1 hastd[92204]: [hasta] (primary) Worker process killed (pid=92223, signal=6). Mar 18 20:49:02 gw1 hastd[92225]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Mar 18 20:49:02 gw1 hastd[92225]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Mar 18 20:49:02 gw1 hastd[92204]: Unable to receive control header: Socket is not connected. Mar 18 20:49:02 gw1 kernel: pid 92225 (hastd), uid 0: exited on signal 6 (core dumped) Mar 18 20:49:02 gw1 hastd[92204]: Unable to send control response: Broken pipe. Mar 18 20:49:07 gw1 hastd[92204]: [hasta] (primary) Worker process killed (pid=92225, signal=6). Mar 18 20:49:08 gw1 hastd[92230]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Mar 18 20:49:08 gw1 hastd[92230]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Mar 18 20:49:08 gw1 kernel: pid 92230 (hastd), uid 0: exited on signal 6 (core dumped) Thanks. Eugene. From owner-freebsd-stable@freebsd.org Sun Mar 18 22:56:31 2018 Return-Path: Delivered-To: freebsd-stable@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 137ECF5B7EF; Sun, 18 Mar 2018 22:56:31 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (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 845006BCB0; Sun, 18 Mar 2018 22:56:30 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by mail-pf0-x22a.google.com with SMTP id l27so1767300pfk.12; Sun, 18 Mar 2018 15:56:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=R3QymJFMYYCJNVx+1+ozGcEEsLaOB5/dMmH+5mVvIts=; b=NJgUOPcm2YzRYH3H5RoF6v7toWPQl9w3P9tbc4zOeWFKb4ZmpJtrglt1SNbWjoMkRX 5eAiaJDbsWpIuMhF5m4Vqc99RBdy5HtJ16LbWBhSaJjzYNkDx/XYUwihnn2Jv2PLJ28r Lh730dZ7c2M4ESfqyo+7Q+yMVFLas63Jovm+r4xNYJ1UuYYdx8xXmjQ/AXjmunRDiLWy q4kGo7GaIhNmQ+kpmGVbfq2V+1V40bSJTPA7YQa27DKk5huzpE13GHrgJiPCnk4O100+ mM8+NDrHbo9o5c/7at1T/QjQAzsjf58PI+jrviduC5Nb1kkyWUBqr4jZOonTQu+zM91P JdiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=R3QymJFMYYCJNVx+1+ozGcEEsLaOB5/dMmH+5mVvIts=; b=U4/sh5jsvusAPMmAdJnCMCCfOuY5PvCw1aWDgBBoDUOmoHIz8+ooBrzk2S2z1tAhuc 4Vz2FOJZdHsRJaF3NPvr/Perx5NmlnK+QI6Tr1oCOEVfip9+wWTj7JT09FvtHvjnLogt bv3l+31pQFlqQ88pD4pKeCYqnPV0BiaKzfQTuSMyR2PPnu41XnV5zBCBwZBd4Ivk46Z7 mnzf+2X8+aXZ3jcV3WwZyFi/V9X2kmmL+6iEK+VAdj7ida55WfG4Q83DIdax8t2G+Xj0 iltQBgLia97xbClZMhQq2pjg5gJs/4GQ0qnIRaW6Lkk4eQDUwusu4TkdpSTBQ603xZxM au2g== X-Gm-Message-State: AElRT7FKEEwTPDjJqfXV1j/VhSpd1HMmuyeuS/R5+9uCkRY4oWQraZNj S/XBmrCAuLB6DIdFC4YYxrM0j01G X-Google-Smtp-Source: AG47ELvSuhOGiJmhqDBJQgwPo1kz2jYQl6vEYbA4/63RfwWyhbaOhFtLWg3S7KWr3BiDBUScF2FIMw== X-Received: by 10.101.70.203 with SMTP id n11mr7566419pgr.166.1521413789580; Sun, 18 Mar 2018 15:56:29 -0700 (PDT) Received: from ox ([2601:641:c000:b800:d4a0:ba9e:80e:6a83]) by smtp.gmail.com with ESMTPSA id p86sm26952670pfi.55.2018.03.18.15.56.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Mar 2018 15:56:28 -0700 (PDT) Date: Sun, 18 Mar 2018 15:56:19 -0700 From: Navdeep Parhar To: Hans Petter Selasky Cc: Konstantin Belousov , "'freebsd-infiniband@freebsd.org'" , freebsd-drivers , Meny Yossefi , "'FreeBSD-stable@FreeBSD.org'" , freebsd-arch Subject: Re: [HEADS UP] - OFED/RDMA stack update Message-ID: <20180318225619.GA6132@ox> Mail-Followup-To: Hans Petter Selasky , Konstantin Belousov , "'freebsd-infiniband@freebsd.org'" , freebsd-drivers , Meny Yossefi , "'FreeBSD-stable@FreeBSD.org'" , freebsd-arch References: <1519683699.47932.5.camel@FreeBSD.org> <20180226224311.GT94212@kib.kiev.ua> <3027f48e-0ba8-555d-df23-d638303cb125@selasky.org> <20180317195200.GA5223@ox> <6d451a3b-a635-08b1-f8d4-52fdc48083d6@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6d451a3b-a635-08b1-f8d4-52fdc48083d6@selasky.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 22:56:31 -0000 On Sat, Mar 17, 2018 at 09:03:40PM +0100, Hans Petter Selasky wrote: > On 03/17/18 20:52, Navdeep Parhar wrote: > >Hold your horses. Do you have confirmation from the affected party that > >the shims are adequate for them? I have been waiting for that before > >looking at this branch. > > Hi Navdeep, > > Mellanox has received an API list from at least one party, and has taken the > action to support all the required APIs. > > >Is the iw_cxgbe breakage a simple merge conflict as previously discussed > >or do the shims require driver changes? > > It is a merge conflict. The code already compiles in 12-current. Ok that doesn't sound that bad. I'll take a look early this week. Regards, Navdeep > > >If they don't then it should be > >possible to drop the iw_cxgbe from head into this branch and it should > >just work, is that correct? > > Yes, it shouldn't be too hard to do and I would appreciate if Chelsio could > throw some resources at this ASAP. I believe the new code will benefit > everyone using Infiniband/RoCE and iWarp with FreeBSD. > > --HPS > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Mon Mar 19 10:27:49 2018 Return-Path: Delivered-To: freebsd-stable@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 3F585F63397 for ; Mon, 19 Mar 2018 10:27:49 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (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 D1276681ED for ; Mon, 19 Mar 2018 10:27:48 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from cpc73666-dals20-2-0-cust303.20-2.cable.virginm.net ([82.47.237.48] helo=foula.drayhouse.twisted.org.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1exs14-0001Mj-Md for freebsd-stable@freebsd.org; Mon, 19 Mar 2018 10:27:46 +0000 Subject: Re: HAST, configuration, this actually looks insane To: freebsd-stable@freebsd.org References: From: Pete French Message-ID: <2383bbc2-0efe-288a-99b6-cc35c23bcd16@ingresso.co.uk> Date: Mon, 19 Mar 2018 10:27:46 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 10:27:49 -0000 I aalways found hast very easy to configure - I stopped using it a couple of weeks ago, but up until then we had used it heavily in production. Have found some old config files, which do work, as examples: two machines - catbert-active, catbert-passive. catbert-active is 192.168.10.3, passive is 192.168.10.4. on catbert-active: resource cbert0 { replication memsync local /dev/gpt/catbert-active-hast-a on catbert-active { remote tcp4://192.168.10.4 source tcp4://192.168.10.3 } on catbert-passive { remote tcp4://192.168.10.3 source tcp4://192.168.10.4 } } on catbert-passive: resource cbert0 { replication memsync local /dev/gpt/catbert-passive-hast-a on catbert-active { remote tcp4://192.168.10.4 source tcp4://192.168.10.3 } on catbert-passive { remote tcp4://192.168.10.3 source tcp4://192.168.10.4 } } As you can see, its the same config file on both machines, just my gpt name is different. If I were using device names then it would be identical. I always fix both source and remote addresses as I was using a pair of dedicted cards to connect themmachines - they had other Ip addresse and could see each eother over a different LAN too. I always put by 'local' outsid the 'on' definitionse, and had different config files on each machine. I havent tried it with 'local' inside, but your config does look OK to me, assumng that works. try adjusting it to have the soucre addess and local outside of th definition like I do though, as I do know that works. -pete. From owner-freebsd-stable@freebsd.org Mon Mar 19 15:09:28 2018 Return-Path: Delivered-To: freebsd-stable@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 5C06EF5380B for ; Mon, 19 Mar 2018 15:09:28 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) (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 BF496738EF for ; Mon, 19 Mar 2018 15:09:27 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [217.29.44.10]) by gate2.intern.punkt.de with ESMTP id w2JEr3XN019180 for ; Mon, 19 Mar 2018 15:53:03 +0100 (CET) Received: from [217.29.44.49] ([217.29.44.49]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id w2JEr3MQ014176 for ; Mon, 19 Mar 2018 15:53:03 +0100 (CET) (envelope-from hausen@punkt.de) From: "Patrick M. Hausen" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: FreeBSD 11.1 ixl(4) interface does not negotiate at 100 Mbit/s Message-Id: Date: Mon, 19 Mar 2018 15:53:03 +0100 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 15:09:28 -0000 Hi all, any ideas why a current RELENG_11_1 system with ixl(4) onboard interfaces might not negotiate with a switch that has only fast ethernet? status: no carrier on the host line protocol is down (notconnect) on the switch dmesg: https://imgur.com/9ri9is8 Thanks for any hints, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe info@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling From owner-freebsd-stable@freebsd.org Mon Mar 19 15:18:48 2018 Return-Path: Delivered-To: freebsd-stable@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 35F41F54427 for ; Mon, 19 Mar 2018 15:18:48 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::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 C66CE747D0 for ; Mon, 19 Mar 2018 15:18:47 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1exwYj-000BEt-6k; Mon, 19 Mar 2018 16:18:49 +0100 Date: Mon, 19 Mar 2018 16:18:49 +0100 From: Kurt Jaeger To: "Patrick M. Hausen" Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 11.1 ixl(4) interface does not negotiate at 100 Mbit/s Message-ID: <20180319151849.GP21001@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 15:18:48 -0000 Hi! > any ideas why a current RELENG_11_1 system with ixl(4) > onboard interfaces might not negotiate with a switch that > has only fast ethernet? > > status: no carrier on the host > line protocol is down (notconnect) on the switch > > dmesg: > https://imgur.com/9ri9is8 Please install net/intel-ixl-kmod and try again. -- pi@opsec.eu +49 171 3101372 2 years to go ! From owner-freebsd-stable@freebsd.org Mon Mar 19 15:22:57 2018 Return-Path: Delivered-To: freebsd-stable@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 2E1C7F549B9 for ; Mon, 19 Mar 2018 15:22:57 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fmsmga106.fm.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EBDE74C0F for ; Mon, 19 Mar 2018 15:22:55 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Mar 2018 08:21:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,331,1517904000"; d="scan'208";a="36262714" Received: from orsmsx107.amr.corp.intel.com ([10.22.240.5]) by orsmga003.jf.intel.com with ESMTP; 19 Mar 2018 08:21:45 -0700 Received: from orsmsx161.amr.corp.intel.com (10.22.240.84) by ORSMSX107.amr.corp.intel.com (10.22.240.5) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 19 Mar 2018 08:21:45 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.12.160]) by ORSMSX161.amr.corp.intel.com ([169.254.4.212]) with mapi id 14.03.0319.002; Mon, 19 Mar 2018 08:21:45 -0700 From: "Pieper, Jeffrey E" To: "Patrick M. Hausen" , "freebsd-stable@freebsd.org" Subject: Re: FreeBSD 11.1 ixl(4) interface does not negotiate at 100 Mbit/s Thread-Topic: FreeBSD 11.1 ixl(4) interface does not negotiate at 100 Mbit/s Thread-Index: AQHTv5SAPFGgRKBwm0C/2Ge9YsVVvaPXrM+A Date: Mon, 19 Mar 2018 15:21:43 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.c.0.180312 x-originating-ip: [134.134.172.157] Content-Type: text/plain; charset="utf-8" Content-ID: <032C017DD399684F898C5D9029F81449@intel.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 15:22:57 -0000 V2hhdCBpcyB0aGUgZGV2aWNlIGlkIChwY2ljb25mIC1sdik/IEknbSBwcmV0dHkgY2VydGFpbiB0 aGF0IHRoZXJlIGFyZW4ndCBhbnkgZGV2aWNlcyBzdXBwb3J0ZWQgYnkgaXhsIHRoYXQgYXJlIGNh cGFibGUgb2YgMTAwTWIuIEFGQUlLLCB0aGUgWDcxMC9YNzIyIEJBU0UtVCBkZXZpY2VzIGFyZSBh bGwgMTBHLzFHLg0KDQpKZWZmDQoNCu+7v09uIDMvMTkvMTgsIDg6MTEgQU0sICJvd25lci1mcmVl YnNkLXN0YWJsZUBmcmVlYnNkLm9yZyBvbiBiZWhhbGYgb2YgUGF0cmljayBNLiBIYXVzZW4iIDxv d25lci1mcmVlYnNkLXN0YWJsZUBmcmVlYnNkLm9yZyBvbiBiZWhhbGYgb2YgaGF1c2VuQHB1bmt0 LmRlPiB3cm90ZToNCg0KICAgIEhpIGFsbCwNCiAgICANCiAgICBhbnkgaWRlYXMgd2h5IGEgY3Vy cmVudCBSRUxFTkdfMTFfMSBzeXN0ZW0gd2l0aCBpeGwoNCkNCiAgICBvbmJvYXJkIGludGVyZmFj ZXMgbWlnaHQgbm90IG5lZ290aWF0ZSB3aXRoIGEgc3dpdGNoIHRoYXQNCiAgICBoYXMgb25seSBm YXN0IGV0aGVybmV0Pw0KICAgIA0KICAgIHN0YXR1czogbm8gY2FycmllcgkJCQkJb24gdGhlIGhv c3QNCiAgICBsaW5lIHByb3RvY29sIGlzIGRvd24gKG5vdGNvbm5lY3QpCQlvbiB0aGUgc3dpdGNo DQogICAgDQogICAgZG1lc2c6DQogICAgaHR0cHM6Ly9pbWd1ci5jb20vOXJpOWlzOA0KICAgIA0K ICAgIA0KICAgIFRoYW5rcyBmb3IgYW55IGhpbnRzLA0KICAgIFBhdHJpY2sNCiAgICAtLSANCiAg ICBwdW5rdC5kZSBHbWJICQkJSW50ZXJuZXQgLSBEaWVuc3RsZWlzdHVuZ2VuIC0gQmVyYXR1bmcN CiAgICBLYWlzZXJhbGxlZSAxM2EJCQlUZWwuOiAwNzIxIDkxMDktMCBGYXg6IC0xMDANCiAgICA3 NjEzMyBLYXJsc3J1aGUJCQlpbmZvQHB1bmt0LmRlCWh0dHA6Ly9wdW5rdC5kZQ0KICAgIEFHIE1h bm5oZWltIDEwODI4NQkJR2Y6IEp1ZXJnZW4gRWdlbGluZw0KICAgIA0KICAgIF9fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICAgZnJlZWJzZC1zdGFibGVA ZnJlZWJzZC5vcmcgbWFpbGluZyBsaXN0DQogICAgaHR0cHM6Ly9saXN0cy5mcmVlYnNkLm9yZy9t YWlsbWFuL2xpc3RpbmZvL2ZyZWVic2Qtc3RhYmxlDQogICAgVG8gdW5zdWJzY3JpYmUsIHNlbmQg YW55IG1haWwgdG8gImZyZWVic2Qtc3RhYmxlLXVuc3Vic2NyaWJlQGZyZWVic2Qub3JnIg0KICAg IA0KDQo= From owner-freebsd-stable@freebsd.org Mon Mar 19 15:38:57 2018 Return-Path: Delivered-To: freebsd-stable@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 194DEF55B2C for ; Mon, 19 Mar 2018 15:38:57 +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 A60F5757D7 for ; Mon, 19 Mar 2018 15:38:56 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1exws3-000GM5-O5; Mon, 19 Mar 2018 18:38:47 +0300 Date: Mon, 19 Mar 2018 18:38:47 +0300 From: Slawa Olhovchenkov To: "Patrick M. Hausen" Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 11.1 ixl(4) interface does not negotiate at 100 Mbit/s Message-ID: <20180319153847.GA6612@zxy.spb.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 15:38:57 -0000 On Mon, Mar 19, 2018 at 03:53:03PM +0100, Patrick M. Hausen wrote: > Hi all, > > any ideas why a current RELENG_11_1 system with ixl(4) > onboard interfaces might not negotiate with a switch that > has only fast ethernet? > > status: no carrier on the host > line protocol is down (notconnect) on the switch > > dmesg: > https://imgur.com/9ri9is8 "Intel® Ethernet Controller X710/XXV710/XL710 Feature Support Matrix" don't show support 100Mb link for any sw release for X710/XL710. "Intel® Ethernet Connection X722 Feature Support Matrix" don't have string "100" From owner-freebsd-stable@freebsd.org Mon Mar 19 15:55:25 2018 Return-Path: Delivered-To: freebsd-stable@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 E243EF56FBC for ; Mon, 19 Mar 2018 15:55:25 +0000 (UTC) (envelope-from Albert.Shih@obspm.fr) Received: from mx-p1.obspm.fr (mx-p1.obspm.fr [145.238.193.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "*.obspm.fr", Issuer "TERENA SSL CA 3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85DE476881; Mon, 19 Mar 2018 15:55:25 +0000 (UTC) (envelope-from Albert.Shih@obspm.fr) Received: from io.chezmoi.fr (io-p2.obspm.fr [145.238.197.205]) (authenticated bits=0) by mx-p1.obspm.fr (8.14.4/8.14.4/DIO Observatoire de Paris - 15/04/10) with ESMTP id w2JFtHoB345477 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 19 Mar 2018 16:55:18 +0100 Date: Mon, 19 Mar 2018 16:55:21 +0100 From: Albert Shih To: Gary Palmer Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 11.1,11-stable,12-current on Dell H740p raid Message-ID: <20180319155521.GA4310@io.chezmoi.fr> References: <20180313161553.GC8462@io.chezmoi.fr> <20180313165215.GA59700@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180313165215.GA59700@in-addr.com> User-Agent: Mutt/1.9.4 (2018-02-28) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.11 (mx-p1.obspm.fr [145.238.193.20]); Mon, 19 Mar 2018 16:55:18 +0100 (CET) X-Virus-Scanned: clamav-milter 0.99.3 at mx-p1.obspm.fr X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 15:55:26 -0000 Le 13/03/2018 à 16:52:15+0000, Gary Palmer a écrit > On Tue, Mar 13, 2018 at 05:15:53PM +0100, Albert Shih wrote: > > Hi, > > > > > > I got issue with Dell PowerEdge R740/R640 server with H740p and FreeBSD > > 11.1-Release, 11-stable, 12-current > > > > In all version I don't able to find the raid controler, so no disk...so of > > course impossible to install anything. > > > > I don't know if it's the right mailing-list, but if they are someone can > > help.... > > > > In other way, I can do ? any ? test for making thing work and help the > > freebsd team. Because Dell are still a large provider for hardware, and that would > > be very sad if FreeBSD cannot run on Dell. > > > > I still got some time (~ 1 month) before the server go in to production. > > > > For information Debian with Linux kernel prio to 4.14 don't work either. Currently only > > RedHat 7 work out of the box. > > Download the driver from > > https://www.broadcom.com/products/storage/raid-controllers/megaraid-9460-8i#downloads > > and try that. Okay. So yes it's working. I just install the server. But...the documentation inside the archive s*cks..... If you follow the doc with a standard memstick img it's not working because the mrsas driver is include inside the generic kernel. So you either need to build a personnal memstick with the src of the driver from broadcom, or you need to build a personnal memstick without mrsas driver and load the mrsas.so from broadcom. Looking inside the archive it's seem the mrsas driver from broadcom are in src version. Are someone know why they are not include in FreeBSD source ? I didn't see (but I'm not a specialist) anything (licence) against that Thanks for the help -- Albert SHIH DIO bâtiment 15 Observatoire de Paris Heure local/Local time: Mon Mar 19 16:50:55 CET 2018 From owner-freebsd-stable@freebsd.org Mon Mar 19 16:43:50 2018 Return-Path: Delivered-To: freebsd-stable@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 A9B62F5A47E for ; Mon, 19 Mar 2018 16:43:50 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: from mail-it0-f46.google.com (mail-it0-f46.google.com [209.85.214.46]) (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 422E478AE3 for ; Mon, 19 Mar 2018 16:43:50 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: by mail-it0-f46.google.com with SMTP id e98-v6so11107254itd.4 for ; Mon, 19 Mar 2018 09:43:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=09QCmPVDHw2e0aTbzzJCBD0fe0aRDLMfwnoM4crGMG8=; b=EpI3o3MHAJDxVuKRH/FfXs06E7Z0PVqKuyGjeTZbIwFQyz7I8zzs+7q6wZR4GiyTL1 du50uXIKI3iWkBrXFZpGoeAeYoS6rHKOf6hQd2zssd1jBV9ClEduO4aUWqs6PQX0K3nj tMAqQEibjUfJKz2lpfJT5Q61zcB8RC5SFQk/mA8qnWrLyw8Cp5ofTHhyCLPvYfh3oJmV FpwQIzpS77MZJ+cMVBks4NybmoeIYU9MDw1JihP0LLV5NZpGy5MofPcR6IK0RlZzJr3x rLKeBTKkEqU/vUGZHLzKwmpk6YaLi3yzM3GzRXoeRuPal54A55vseHet5uHtFOfkowsy 39Bw== X-Gm-Message-State: AElRT7G1hMw+CmaOVNN6WgAoinlKv6JWmPvfd5WbrY65FAF6PDDJuqFQ 4COj60oWEvbguInH9ZI8Tp3Sn3Kq X-Google-Smtp-Source: AG47ELsRKDg8oX2lkRT4IM8jVUbqY4Hbmu1AOaDQxlM4Pci7E+Z3TN/b8OqkTOeXIt0S+34Ie38i5A== X-Received: by 2002:a24:595:: with SMTP id 143-v6mr12589351itl.138.1521477432647; Mon, 19 Mar 2018 09:37:12 -0700 (PDT) Received: from mail-io0-f177.google.com (mail-io0-f177.google.com. [209.85.223.177]) by smtp.gmail.com with ESMTPSA id u67sm180361ioe.12.2018.03.19.09.37.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Mar 2018 09:37:12 -0700 (PDT) Received: by mail-io0-f177.google.com with SMTP id e7so11063690iof.2 for ; Mon, 19 Mar 2018 09:37:11 -0700 (PDT) X-Received: by 10.107.188.197 with SMTP id m188mr13622244iof.193.1521477431593; Mon, 19 Mar 2018 09:37:11 -0700 (PDT) MIME-Version: 1.0 References: <20180319153847.GA6612@zxy.spb.ru> In-Reply-To: <20180319153847.GA6612@zxy.spb.ru> From: Eric Joyner Date: Mon, 19 Mar 2018 16:37:00 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: FreeBSD 11.1 ixl(4) interface does not negotiate at 100 Mbit/s To: "Patrick M. Hausen" Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 16:43:50 -0000 I'm guessing these are 10G copper LOMs using X722; those don't support 100Mb speeds. - Eric On Mon, Mar 19, 2018 at 8:41 AM Slawa Olhovchenkov wrote: > On Mon, Mar 19, 2018 at 03:53:03PM +0100, Patrick M. Hausen wrote: > > > Hi all, > > > > any ideas why a current RELENG_11_1 system with ixl(4) > > onboard interfaces might not negotiate with a switch that > > has only fast ethernet? > > > > status: no carrier on the host > > line protocol is down (notconnect) on the switch > > > > dmesg: > > https://imgur.com/9ri9is8 > > "Intel=C2=AE Ethernet Controller X710/XXV710/XL710 Feature Support Matrix= " > don't show support 100Mb link for any sw release for X710/XL710. > > "Intel=C2=AE Ethernet Connection X722 Feature Support Matrix" don't have > string "100" > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Mon Mar 19 19:53:06 2018 Return-Path: Delivered-To: freebsd-stable@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 32133F67E12 for ; Mon, 19 Mar 2018 19:53:06 +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 C8EF181CFB; Mon, 19 Mar 2018 19:53:05 +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 2601E10A7DB; Mon, 19 Mar 2018 15:53:05 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Cc: Glen Barber , Mark Saad , wishmaster Subject: Re: Problem with USB <---> UPS management connection Date: Mon, 19 Mar 2018 12:53:01 -0700 Message-ID: <1744138.yp8bGWUsoN@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <20180308011646.GC7399@FreeBSD.org> References: <1520423283.816382083.msco108y@frv52.fwdcdn.com> <548D61D9-2A86-48E4-B077-285298CB64CE@longcount.org> <20180308011646.GC7399@FreeBSD.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 19 Mar 2018 15:53:05 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 19:53:06 -0000 On Thursday, March 08, 2018 01:16:46 AM Glen Barber wrote: > On Wed, Mar 07, 2018 at 08:04:47PM -0500, Mark Saad wrote: > > > On Mar 7, 2018, at 6:55 AM, wishmaster wrote: > > >=20 > > > Hi, colleagues! > > >=20 > > > Something strange happens with a server. I am attempting to conne= ct management interface of UPS with server via USB. > > > In console I see a lot of errors: > > >=20 > > > Mar 7 13:42:04 xxx kernel: ugen2.2: at usbus2 > > > Mar 7 13:42:05 xxx kernel: uhid0 on uhub6 > > > Mar 7 13:42:05 xxx kernel: uhid0: on usbus2 > > > Mar 7 13:42:08 xxx kernel: ugen2.2: at usbus2 (disconnected) > > > Mar 7 13:42:08 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disc= onnected) > > > Mar 7 13:42:08 xxx kernel: uhid0: detached > > > Mar 7 13:42:12 xxx kernel: ugen2.2: at usbus2 > > > Mar 7 13:42:12 xxx kernel: uhid0 on uhub6 > > > Mar 7 13:42:12 xxx kernel: uhid0: on usbus2 > > > Mar 7 13:42:16 xxx kernel: ugen2.2: at usbus2 (disconnected) > > > Mar 7 13:42:16 xxx kernel: uhid0: at uhub6, port 3, addr 2 (disc= onnected) > > > Mar 7 13:42:16 xxx kernel: uhid0: detached > > >=20 > > > I have changed USB-cables, USB port on the server - without succe= ss. > > > On another server this problem is absent. > > >=20 > > > FreeBSD version: FreeBSD 11.1-STABLE #1 r329364M: > > >=20 > > > Any ideas? > > >=20 > > All > > I lost power at home and noticed that nut didn=E2=80=99t work righ= t . I > > had a similar dmesg . My box is running 11.1-stable amd64 built > > from svn 7-8 days ago . When I get power back I=E2=80=99ll post det= ails . > >=20 >=20 > This seems suspiciously similar to an issue I am seeing with a USB mo= use > on both stable/11 a patched build of releng/11.1. In my case, the dm= esg > shows: >=20 > ugen1.3: at usbus1 (disconnected) > ugen1.3: at usbus1 > ugen1.3: at usbus1 (disconnected) > ugen1.3: at usbus1 >=20 > What struck me as "suspiciously similar" is the 'ugen' reference. > Unfortunately, I do not have more information yet, but have been > pounding my head on my desk throughout the day. Then, I saw this > thread. >=20 > Anyone else seeing at least USB mouse-related issues? It could entir= ely > be a red herring. I am definitely seeing issues with an APC USB I have on my desktop. I = have used this desktop + APC combination for at least 5 years now and only a= fter my most recent upgrade to 11.1-STABLE at r326909. I did not have issue= s on the previous 11.1-STABLE kernel at r321399, so it does seem like it cou= ld be a regression. --=20 John Baldwin From owner-freebsd-stable@freebsd.org Mon Mar 19 20:00:55 2018 Return-Path: Delivered-To: freebsd-stable@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 924D9F6859A for ; Mon, 19 Mar 2018 20:00:55 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45F1E821E2; Mon, 19 Mar 2018 20:00:55 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id F13AB1AE2B; Mon, 19 Mar 2018 20:00:54 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Mon, 19 Mar 2018 20:00:53 +0000 From: Glen Barber To: John Baldwin Cc: freebsd-stable@freebsd.org, Mark Saad , wishmaster Subject: Re: Problem with USB <---> UPS management connection Message-ID: <20180319200053.GE14326@FreeBSD.org> References: <1520423283.816382083.msco108y@frv52.fwdcdn.com> <548D61D9-2A86-48E4-B077-285298CB64CE@longcount.org> <20180308011646.GC7399@FreeBSD.org> <1744138.yp8bGWUsoN@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sfyO1m2EN8ZOtJL6" Content-Disposition: inline In-Reply-To: <1744138.yp8bGWUsoN@ralph.baldwin.cx> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 20:00:55 -0000 --sfyO1m2EN8ZOtJL6 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 19, 2018 at 12:53:01PM -0700, John Baldwin wrote: > On Thursday, March 08, 2018 01:16:46 AM Glen Barber wrote: > > On Wed, Mar 07, 2018 at 08:04:47PM -0500, Mark Saad wrote: > > > > On Mar 7, 2018, at 6:55 AM, wishmaster wrote: > > > >=20 > > > > Hi, colleagues! > > > >=20 > > > > Something strange happens with a server. I am attempting to connect= management interface of UPS with server via USB. > > > > In console I see a lot of errors: > > > >=20 > > > > Mar 7 13:42:04 xxx kernel: ugen2.2: at usbus2 > > > > Mar 7 13:42:05 xxx kernel: uhid0 on uhub6 > > > > Mar 7 13:42:05 xxx kernel: uhid0: on usbus2 > > > > Mar 7 13:42:08 xxx kernel: ugen2.2: at usbus2 (disconnected) > > > > Mar 7 13:42:08 xxx kernel: uhid0: at uhub6, port 3, addr 2 (discon= nected) > > > > Mar 7 13:42:08 xxx kernel: uhid0: detached > > > > Mar 7 13:42:12 xxx kernel: ugen2.2: at usbus2 > > > > Mar 7 13:42:12 xxx kernel: uhid0 on uhub6 > > > > Mar 7 13:42:12 xxx kernel: uhid0: on usbus2 > > > > Mar 7 13:42:16 xxx kernel: ugen2.2: at usbus2 (disconnected) > > > > Mar 7 13:42:16 xxx kernel: uhid0: at uhub6, port 3, addr 2 (discon= nected) > > > > Mar 7 13:42:16 xxx kernel: uhid0: detached > > > >=20 > > > > I have changed USB-cables, USB port on the server - without success. > > > > On another server this problem is absent. > > > >=20 > > > > FreeBSD version: FreeBSD 11.1-STABLE #1 r329364M: > > > >=20 > > > > Any ideas? > > > >=20 > > > All > > > I lost power at home and noticed that nut didn=E2=80=99t work right = =2E I > > > had a similar dmesg . My box is running 11.1-stable amd64 built > > > from svn 7-8 days ago . When I get power back I=E2=80=99ll post detai= ls . > > >=20 > >=20 > > This seems suspiciously similar to an issue I am seeing with a USB mouse > > on both stable/11 a patched build of releng/11.1. In my case, the dmesg > > shows: > >=20 > > ugen1.3: at usbus1 (disconnected) > > ugen1.3: at usbus1 > > ugen1.3: at usbus1 (disconnected) > > ugen1.3: at usbus1 > >=20 > > What struck me as "suspiciously similar" is the 'ugen' reference. > > Unfortunately, I do not have more information yet, but have been > > pounding my head on my desk throughout the day. Then, I saw this > > thread. > >=20 > > Anyone else seeing at least USB mouse-related issues? It could entirely > > be a red herring. >=20 > I am definitely seeing issues with an APC USB I have on my desktop. I ha= ve > used this desktop + APC combination for at least 5 years now and only aft= er > my most recent upgrade to 11.1-STABLE at r326909. I did not have issues = on > the previous 11.1-STABLE kernel at r321399, so it does seem like it could > be a regression. >=20 I did figure out what the problem was with my mouse - the ums(4) driver was not properly loading on releng/11.1. It does appear to be fixed in stable/11, so the issue I pointed out in this thread may not be related. Glen --sfyO1m2EN8ZOtJL6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlqwFvUACgkQAxRYpUeP 4pOzIA/8DGiEUURBGsdEpyBZmonOpGqn1fZBVgw/km4X5tHRF2p12m5IxsyOT0ts JUKTsg7TfydIfqLenZIRlIMV6e2zFlAXzeBkIBcCNZIgRc53e502G6uLGDgLA9aK f58pK8p37HGCg3c/U4x8bVC/LtU7wYw8ef5GIa8t4wrd6ygyii5KVYrpPsTotuq9 WPlJ4uc3s+hUvYSbgtmtLQU2QQ3NB4dRdukUepfCx+3DJQvyWe8uFF8cNqmKf6PD MHGHOUP1wSnBkQhO1UlVOxXOSEEFNy4BDJj+1eZrvFwpXl3MEAoq1pojaTQFb5z4 GAxo/n3tNQPPpYi7KR4UcIiEEvMOgc6u1BvlOUn/r8c8dym+Ea3FxW/D4RKZ2QCC 3rn6FIQ3rjkUYmRg5Dpf16IBnfodqXlPjCmaQhBAijca3GvKJbKlhAmmbwSzK8Od AGTGyb2XikkPQ5l1NUPhYsc9f4I+GO106Kidd8JAIWcH1FBPOR8XpTztE8f7MORu QF0RbNyeblEfqJrc3w2wozANEVamRf92dlEL2KqERpwNWWtncFLPRbw92oWhlx88 rq9C/TrCUqXowHRl4gLBs7+9kpoZm3lTtYnRbBd81zwLKUdkSL9dTzdrHgYPZv/t sBlfUOShlc7RJBpqoC7I5D7TU6R94Lz/JuXGueWDgfoFzx5Vmsg= =+U0B -----END PGP SIGNATURE----- --sfyO1m2EN8ZOtJL6-- From owner-freebsd-stable@freebsd.org Mon Mar 19 20:04:56 2018 Return-Path: Delivered-To: freebsd-stable@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 07970F68C4F for ; Mon, 19 Mar 2018 20:04:56 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) (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 7B634827D5; Mon, 19 Mar 2018 20:04:55 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [217.29.44.10]) by gate2.intern.punkt.de with ESMTP id w2JK4r6e022146; Mon, 19 Mar 2018 21:04:53 +0100 (CET) Received: from [217.29.46.112] ([217.29.46.112]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id w2JK4qiN023184; Mon, 19 Mar 2018 21:04:52 +0100 (CET) (envelope-from hausen@punkt.de) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: FreeBSD 11.1 ixl(4) interface does not negotiate at 100 Mbit/s From: "Patrick M. Hausen" In-Reply-To: Date: Mon, 19 Mar 2018 21:04:53 +0100 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <1BBBC80C-13F9-48DE-8256-E8110679C0DC@punkt.de> References: <20180319153847.GA6612@zxy.spb.ru> To: Eric Joyner X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 20:04:56 -0000 Hi all, > Am 19.03.2018 um 17:37 schrieb Eric Joyner : > I'm guessing these are 10G copper LOMs using X722; those don't support = 100Mb speeds. Your guess is probably correct. Going to re-wire tomorrow. Thanks, everyone. Patrick --=20 punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe info@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling From owner-freebsd-stable@freebsd.org Tue Mar 20 01:07:18 2018 Return-Path: Delivered-To: freebsd-stable@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 15D74F5A986 for ; Tue, 20 Mar 2018 01:07:18 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from hermes.heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46284704CD for ; Tue, 20 Mar 2018 01:07:16 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from [10.0.5.3] (noddy.hs [10.0.5.3]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.15.2/8.15.2) with ESMTPSA id w2K15rJl078863 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Tue, 20 Mar 2018 12:05:55 +1100 (AEDT) (envelope-from dewayne.geraghty@heuristicsystems.com.au) X-Authentication-Warning: b3.hs: Host noddy.hs [10.0.5.3] claimed to be [10.0.5.3] To: FreeBSD Stable Mailing List From: Dewayne Geraghty Subject: Stability of 11.1S Message-ID: Date: Tue, 20 Mar 2018 12:05:33 +1100 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-AU X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 01:07:18 -0000 We rebuild 11.1-Stable at least every two weeks.  Our build on the 7th Feb is in use on our development boxes, however the rebuild on 22nd resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE  r329008.  Is anyone actually running a Stable that was built after 22nd Feb?  Could you please share the revision number? Because the churn in https://lists.freebsd.org/pipermail/svn-src-stable-11/2018-March/ is high we haven't been able to sight if a problem was identified and fixed; so we're really looking for a functioning stable that we can resume tracking. PS There was no information in the logs, and we have no instrumentation in the kernel to help. Sorry. -- Influence national support against IP address spoofing (pretending to be someone else), refer: http://www.bcp38.info/index.php/Main_Page From owner-freebsd-stable@freebsd.org Tue Mar 20 01:15:58 2018 Return-Path: Delivered-To: freebsd-stable@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 34A39F5BB88 for ; Tue, 20 Mar 2018 01:15:58 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 31A99710D7 for ; Tue, 20 Mar 2018 01:15:56 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w2K1Fnh7020764; Tue, 20 Mar 2018 01:15:49 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w2K1Fnir020763; Mon, 19 Mar 2018 18:15:49 -0700 (PDT) (envelope-from david) Date: Mon, 19 Mar 2018 18:15:48 -0700 From: David Wolfskill To: Dewayne Geraghty Cc: FreeBSD Stable Mailing List Subject: Re: Stability of 11.1S Message-ID: <20180320011548.GG1233@albert.catwhisker.org> Reply-To: stable@freebsd.org Mail-Followup-To: stable@freebsd.org, Dewayne Geraghty , FreeBSD Stable Mailing List References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3LDjyuwMyYgFmzqN" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 01:15:58 -0000 --3LDjyuwMyYgFmzqN Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 20, 2018 at 12:05:33PM +1100, Dewayne Geraghty wrote: > We rebuild 11.1-Stable at least every two weeks.=A0 Our build on the 7th > Feb is in use on our development boxes, however the rebuild on 22nd > resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE=A0 > r329008.=A0 Is anyone actually running a Stable that was built after 22nd > Feb?=A0 Could you please share the revision number? These are lightly loaded, but the two "production" boxes at home run a stable/11 snapshot, built weekly. Details on the process may be found at ; the page with historical information (including "uname" output for each snapshot run) is . (Each of the two machines runs from the same sources as listed for "albert".) (My laptop & build machine run a daily snapshot of stable/11, as well as building & smoke-testing a daily snapshot of head. The above-cited "weekly snapshot" is actually a "daily snapshot" that is sampled only weekly -- on Sunday morning.) > ...=20 Peace, david --=20 David H. Wolfskill david@catwhisker.org An investigator who doesn't make a perp nervous isn't doing his job. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --3LDjyuwMyYgFmzqN Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlqwYMRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hcoZQf/dsD4o+gzoR1t0TOrk/gfXlDIPGy4CL9PANt8Zfi7H++LhY1W4Elo6ntY 2OBvOIzMz1uXjW4Ofvhn3QJu7hrqw7FJlgAHzoLGOo64LNd+Nk4KyVNqSHiYQP3p HLCVu8DJk3/c1aY3dplqbdjhyurcoKsD65GKfr5cUwjHrt6k+2px3BUjAhZiMGwY ddF7f24PWOag6MwUviUJfJc2NTq2I6WV2wimbMnQbCm2HBS43bq/7Eej9eg/eQq3 Xf77jumKMzWGhlNgEScmMFEK7ba1/xPZIt6y5Px1NQkxo9upJSrNBLQnjcZsTgkH 7LBfRYd+4a+mp2EFw8InoRmjF7Vm+A== =zpKR -----END PGP SIGNATURE----- --3LDjyuwMyYgFmzqN-- From owner-freebsd-stable@freebsd.org Tue Mar 20 03:33:11 2018 Return-Path: Delivered-To: freebsd-stable@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 2AB4A77A for ; Tue, 20 Mar 2018 03:33:11 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (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 B37997A489 for ; Tue, 20 Mar 2018 03:33:10 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x22f.google.com with SMTP id c20so74970ywa.2 for ; Mon, 19 Mar 2018 20:33:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xgtKLAKnBWPM8hKGJOJ0Fn6c9+KBOdruy2drwW3gCQw=; b=FJdKem/m0ZuxBVXnz1hN7fnRMeylfOMsckLf6aiJi7am5dXH6PFUatVIwd2uxqCkTd L/pVjAcY7Q8WTBe+0fEmFcVn/Jq5VxII8bnVw6CcVKyYxommHXMp61hs7xbtt6VhDY0y TXgnLaxP2MpyLKK7FwO31lxiWAKfrxDMa/XNw= 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=xgtKLAKnBWPM8hKGJOJ0Fn6c9+KBOdruy2drwW3gCQw=; b=nzK7HkYkZv1nlEjVrELzK00+1zAmfKubeJr7H77MXsifFopFt/6MySPwRvoapnwK13 xbINmrWRX7fheN0j225KhGt5IJceJ19vgzrEkH7AYtYE0ADrw6kiZtU1x8V1xNpPWJAp 94+gkS4oW7D1cdMX+0m2nKSkwV4tqyIEhHJ10dPR7LiRpIGQXCnccVIyJYirvFI88OMl 8+goUJ9+gwdNEF9jwFj0szKkqq8DK3bSl6+CKH0GBd3bo4zODJ6t/nS0Q3y6//MNKF2r 0LJppsWmWbYr7ohwiwTT0Qng5fMGquNr2assOHrkBzjeccgVXnq9d0XdVnOCANU1MZCT 72fg== X-Gm-Message-State: AElRT7EIrD8hvmHfLhbbEC/fHO27XC1IIu4gtj+aZ518Yf0m12U5hNZR FF1sBVvLKF4xXJH7E1QI+ZtQs0j3FRxUaUsZjMCfbQ== X-Google-Smtp-Source: AG47ELs8sz3+FavjqnKSBfGoiKYtWfeXPs1QpJig6eNxtMII3Ccmb+gkgyt5jg9TAzNOQoDzyAhxaJ+0uUphnobj5Nw= X-Received: by 10.129.62.11 with SMTP id l11mr8355942ywa.387.1521516789847; Mon, 19 Mar 2018 20:33:09 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:23d2:0:0:0:0:0 with HTTP; Mon, 19 Mar 2018 20:32:39 -0700 (PDT) In-Reply-To: References: From: Eitan Adler Date: Mon, 19 Mar 2018 20:32:39 -0700 Message-ID: Subject: Re: Stability of 11.1S To: Dewayne Geraghty Cc: FreeBSD Stable Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 03:33:11 -0000 On 19 March 2018 at 18:05, Dewayne Geraghty wrote: > We rebuild 11.1-Stable at least every two weeks. Our build on the 7th > Feb is in use on our development boxes, however the rebuild on 22nd > resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE > r329008. Is anyone actually running a Stable that was built after 22nd > Feb? Could you please share the revision number? > > Because the churn in > https://lists.freebsd.org/pipermail/svn-src-stable-11/2018-March/ is > high we haven't been able to sight if a problem was identified and > fixed; so we're really looking for a functioning stable that we can > resume tracking. Hi, I can't help identify the problem and if it was fixed without any information. Can you at least let us know what kind of crashes are you seeing? Kernel panics?SIGBUS? Something else? It would be best if you could bisect to the revision causing you problems. Note that despite the name, STABLE is a development branch and users of the branch are expected to be able to provide some help tracking down issues. -- Eitan Adler From owner-freebsd-stable@freebsd.org Tue Mar 20 06:01:03 2018 Return-Path: Delivered-To: freebsd-stable@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 67F47F5566E for ; Tue, 20 Mar 2018 06:01:03 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from hermes.heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 74E0A810E5 for ; Tue, 20 Mar 2018 06:01:01 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from [10.0.5.3] (noddy.hs [10.0.5.3]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.15.2/8.15.2) with ESMTPSA id w2K60HlG031638 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 20 Mar 2018 17:00:17 +1100 (AEDT) (envelope-from dewayne.geraghty@heuristicsystems.com.au) X-Authentication-Warning: b3.hs: Host noddy.hs [10.0.5.3] claimed to be [10.0.5.3] Subject: Re: Stability of 11.1S To: Eitan Adler Cc: FreeBSD Stable Mailing List References: From: Dewayne Geraghty Message-ID: <6b02d324-db1e-5136-e74e-0bf60e38726b@heuristicsystems.com.au> Date: Tue, 20 Mar 2018 16:59:47 +1100 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 In-Reply-To: Content-Language: en-AU MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 06:01:03 -0000 From owner-freebsd-stable@freebsd.org Tue Mar 20 10:50:18 2018 Return-Path: Delivered-To: freebsd-stable@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 4C482F67185 for ; Tue, 20 Mar 2018 10:50:18 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (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 E469A6C8C3 for ; Tue, 20 Mar 2018 10:50:17 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6]) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1eyEqO-000KDd-DS for freebsd-stable@freebsd.org; Tue, 20 Mar 2018 10:50:16 +0000 Subject: Re: Stability of 11.1S To: freebsd-stable@freebsd.org References: From: Pete French Message-ID: <0317c52c-073a-bf53-b278-79f2407daa4b@ingresso.co.uk> Date: Tue, 20 Mar 2018 10:50:16 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 10:50:18 -0000 On 20/03/2018 01:05, Dewayne Geraghty wrote: > We rebuild 11.1-Stable at least every two weeks.  Our build on the 7th > Feb is in use on our development boxes, however the rebuild on 22nd > resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE > r329008.  Is anyone actually running a Stable that was built after 22nd > Feb?  Could you please share the revision number? r330769 works fine for me. I usually upgrade on a Monday, though am holding off this week as am waiting for r330745 to land in STABLE, but it works fine for me always. > Because the churn in > https://lists.freebsd.org/pipermail/svn-src-stable-11/2018-March/ is > high we haven't been able to sight if a problem was identified and > fixed; so we're really looking for a functioning stable that we can > resume tracking. I use this to eyeball whats gone into STABLE, its a daily read for me as I find keeping up with the mailing list tricky too. http://www.freshbsd.org/?branch=RELENG_11&project=freebsd& -pete. From owner-freebsd-stable@freebsd.org Tue Mar 20 14:10:53 2018 Return-Path: Delivered-To: freebsd-stable@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 D14D1F50A28 for ; Tue, 20 Mar 2018 14:10:53 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 55038749A2; Tue, 20 Mar 2018 14:10:52 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w2KEAdn7078731 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 20 Mar 2018 15:10:39 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: freebsd-stable@FreeBSD.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id w2KEAZkF006342; Tue, 20 Mar 2018 21:10:35 +0700 (+07) (envelope-from eugen@grosbein.net) To: FreeBSD Stable Cc: Konstantin Belousov From: Eugene Grosbein Subject: CPUCTL_EVAL_CPU_FEATURES X-Enigmail-Draft-Status: N1110 Message-ID: <5AB1165A.5020800@grosbein.net> Date: Tue, 20 Mar 2018 21:10:34 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=3.5 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, TRACKER_ID autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 1.3 TRACKER_ID BODY: Incorporates a tracking ID number * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: *** X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 14:10:54 -0000 Hi! Please consider bumping __FreeBSD_version after https://svnweb.freebsd.org/base?view=revision&revision=327597 for head and stable/11 to ease port maintainers life, so that port's Makefile could differentiate systems having CPUCTL_EVAL_CPU_FEATURES. From owner-freebsd-stable@freebsd.org Tue Mar 20 14:19:49 2018 Return-Path: Delivered-To: freebsd-stable@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 52471F5148D for ; Tue, 20 Mar 2018 14:19:49 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CC1C774F5F; Tue, 20 Mar 2018 14:19:48 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w2KEJfYR078784 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 20 Mar 2018 15:19:42 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: freebsd-stable@FreeBSD.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id w2KEJbRQ006791; Tue, 20 Mar 2018 21:19:37 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: CPUCTL_EVAL_CPU_FEATURES To: FreeBSD Stable References: <5AB1165A.5020800@grosbein.net> Cc: Konstantin Belousov From: Eugene Grosbein Message-ID: <5AB11879.8050104@grosbein.net> Date: Tue, 20 Mar 2018 21:19:37 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <5AB1165A.5020800@grosbein.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=3.2 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_96_Q, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 1.0 DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: *** X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 14:19:49 -0000 On 20.03.2018 21:10, Eugene Grosbein wrote: > Please consider bumping __FreeBSD_version after > > https://svnweb.freebsd.org/base?view=revision&revision=327597 > > for head and stable/11 to ease port maintainers life, > so that port's Makefile could differentiate systems having CPUCTL_EVAL_CPU_FEATURES. Hmm, I should have checked it twice... __FreeBSD_version was bumped, sorry for noise. From owner-freebsd-stable@freebsd.org Tue Mar 20 18:10:51 2018 Return-Path: Delivered-To: freebsd-stable@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 76C71F623E6 for ; Tue, 20 Mar 2018 18:10:51 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from resqmta-po-08v.sys.comcast.net (resqmta-po-08v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "resqmta-po-01v.sys.comcast.net", Issuer "COMODO RSA Organization Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1736A800AF for ; Tue, 20 Mar 2018 18:10:50 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from resomta-po-08v.sys.comcast.net ([96.114.154.232]) by resqmta-po-08v.sys.comcast.net with ESMTP id yLiZe3rFX3paSyLijeOmGQ; Tue, 20 Mar 2018 18:10:49 +0000 Received: from koitsu.org ([71.198.44.84]) by resomta-po-08v.sys.comcast.net with SMTP id yLihe8HXLQ1ZhyLiie8pr9; Tue, 20 Mar 2018 18:10:48 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 43FB11581F8F; Tue, 20 Mar 2018 11:10:47 -0700 (PDT) Date: Tue, 20 Mar 2018 11:10:47 -0700 From: Jeremy Chadwick To: dewayne.geraghty@heuristicsystems.com.au Cc: freebsd-stable@freebsd.org Subject: Re: Stability of 11.1S Message-ID: <20180320181047.GA55267@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.4 (2018-02-28) X-CMAE-Envelope: MS4wfNNNYsnvbI46M16cGhmYjDIirCX18HpqAWWIwDSTdpyEg/MBd1b2JB7qjkJRjHE+vvVyla8ZlwzGrm9duCU7mAfjl7YQdPMLCtjiarQzqszzopElYg4R 3zwJ4vxCgR1CA6d7yyhGdxDbmj8OOVuasPqeOx2b8Rl/ZxukUbl+jjGjQPEo6ifT5V/jt5ygGnRtQWQC3/gG+vz+f83iosdskGp/5DALCoizI3eN1bKZj5Vp X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 18:10:51 -0000 (Please keep me CC'd as I am not subscribed to -stable) I haven't seen any issues, but that means very little. Details: Two boxes -- one bare metal, one VPS (QEMU): $ uname -a FreeBSD XXXXXXXXXXXXXXX 11.1-STABLE FreeBSD 11.1-STABLE #0 r330529: Tue Mar 6 11:36:04 PST 2018 root@XXXXXXXXXXXXXXX:/usr/obj/usr/src/sys/X7SBA_RELENG_11_amd64 amd64 $ uptime 10:33a.m. up 13 days, 18:10, 2 users, load averages: 0.15, 0.19, 0.16 $ uname -a FreeBSD XXXXXXXXXXXXXXXX 11.1-STABLE FreeBSD 11.1-STABLE #0 r330753: Sat Mar 10 21:34:20 PST 2018 root@XXXXXXXXXXXXXXXX:/usr/obj/usr/src/sys/XXXXXXXX_RELENG_11_amd64 amd64 $ uptime 10:33a.m. up 9 days, 10:46, 1 user, load averages: 0.31, 0.35, 0.31 Systems were updated recently because I wanted to test Meltdown/Spectre mitigation (more on that below). Prior to that, bare metal was running 9.x with 200+ day uptimes, VPS was running 10.x with 80-90 day uptimes (VPS providers' HV crashed, i.e. not FreeBSD issues). Since load averages on FreeBSD 10.x onward cannot be trusted[1][2], I have to explain the general system specs and loads: Bare metal box is an Intel Core 2 Quad Q9550, 8GB RAM, doing very little other than running Apache + lots of cron jobs for systems stuff + ZFS with several disks (but not OS disk; that's a dedicated SSD w/ UFS + SU (not SUJ). The cron jobs tend to stress the network and disk I/O a bit; ZFS gets used every day, but only "heavily" during LAN file copies to/from it (Samba is involved), and during nightly backups with rsync. VPS box is some form of QEMU-based Intel Haswell CPU, 1GB RAM, doing general things like Apache + postfix + SpamAssassin + some other daemons, and a lot of Perl. Swap is used heavily on this machine. Disks are all vtblk, and I use multiple to get capacity for the needed space for /usr/src and /usr/obj. Everything is UFS + SU (not SUJ). Things off the top of my head that might be relevant to you: 1. r329462 added Meltdown/Spectre mitigation[3][4]. Bare metal box has the below in /boot/loader.conf, since this is a machine that does not need either given its environment: # Disable PTI (Meltdown mitigation) and IBRS (Spectre mitigation); these # are not relevant on this bare-metal system given its environment and # use case. Details of these tunables is here: # https://lists.freebsd.org/pipermail/freebsd-stable/2018-March/088526.html # vm.pmap.pti="0" hw.ibrs_disable="1" VPS box has no tunings of this sort, and ends up with the below, because the hosting provider has no done BIOS + QEMU updates to add IBRS support (they're very aware of it + have attempted it twice but apparently it didn't go well): vm.pmap.pti: 1 hw.ibrs_disable: 1 hw.ibrs_active: 0 2. If your CPU is an AMD Ryzen, there is a VERY long discussion on -stable about problems with Ryzen manifesting itself in a very uncomfortable way, leading to system lock-ups[5]. There are unofficial patches you can try. I would recommend chiming in there and not here, if relevant to your systems. And yes, the massive number of MFCs that eadler@ is doing make tracking down exact things more tedious than normal, especially when you have sweeping commits like this one[6][7] (which, AFAIK, was acting as a major blocker for several other MFCs and causing general merge problems). However, I commend his efforts; it's a massive undertaking (I would say full-time job). We stable users must accept that we are running stable/11 for a reason -- not only to get fixes faster, but to act a form of "guinea pig" that don't want the risks of HEAD/CURRENT. The more people using stable/11 the better overall feedback devs can get on bugs/issues before making it into the next -RELEASE. This is exactly why, for those of you who have known me over the years, I actually "track" or "follow" commits as they come across. I do this by using the FreshBSD site[8] alongside manual review of svnlite update output. I generally know what files/bits are relevant to my interests. Hope this gives you some things to think about. Good luck! [1]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173541#c8 [2]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173541#c22 [3]: https://lists.freebsd.org/pipermail/freebsd-stable/2018-February/088396.html [4]: https://lists.freebsd.org/pipermail/freebsd-stable/2018-March/088526.html [5]: https://lists.freebsd.org/pipermail/freebsd-stable/2018-January/thread.html#88174 [6]: http://www.freshbsd.org/commit/freebsd/r330897 [7]: https://svnweb.freebsd.org/base?view=revision&revision=330897 [8]: http://www.freshbsd.org/?branch=RELENG_11&project=freebsd -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@freebsd.org Tue Mar 20 20:07:39 2018 Return-Path: Delivered-To: freebsd-stable@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 0C792F6A19E; Tue, 20 Mar 2018 20:07:39 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (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 74B0A84990; Tue, 20 Mar 2018 20:07:38 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id 139so5905065wmn.2; Tue, 20 Mar 2018 13:07:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=ywvAj3LCHifFGTMLaNs1klcykTEygXtTk9Zy1scKsb0=; b=Nz7I1mM2HGIs4GoDb+B+WJ+nDHlNbj2PZ6Xe9dbwgkgqCqXmFLBjuTFll/sODISpzo mnEaOvcnWIeB2YN5abuSZy3dRGQrXFZYIr1bTWEarzk+sZpzUgkVD8tV0QDub1/CwoKR KxlNppdEpWLQUber2UqKCsPrlwwwdDVvkS5Iqp0bRxZWvtas0iOBsgi/a3qembsOosC9 SXCZBSSiyFuZKGa5OCCGCXLTqF/zl3UrfWtjowC+zicCe3rbFNX/1A6PYQzFmdwwYEQT pSxWG+slg38+tOV+lEDN5kyEbBeYktJXQuFazN23cif/QP3Kzw+5/U0esIp4ejMxlrmo mUew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ywvAj3LCHifFGTMLaNs1klcykTEygXtTk9Zy1scKsb0=; b=lak5ZatNMEGsenUzaj5MyzKeBVl3NKMIouQ/lyBuDD2QuO0PeZbF+9FNqx2QiUXGwB yoXwFK5gqZ03z5qjtP8p32zI4xTV19zYudPY5eRdRGzQTYsmyaUZAqi9GsFPE0oHEWyO OK4H9zXZHw8euAMBlcgisv49xHjUHIOJSocFSN2XqZRy7lxlIHKlCGchs3qTtNrc6RFg UHBkhFhs0LObJVeGZNS3T7njMZO0DFaBgM0DFY4wDVv48XK6O/KBM0FuFmlSCxFhK2SS 7mQh8qV0onzCSgh9CVyHbrsrlJ7QbcOAP82pxsvNiGTKXy9hQfWaGdVfbdRkpilwQP87 HyLw== X-Gm-Message-State: AElRT7FUOFxPTm+zprc7+OhZPbV5lKPJkZF3zA6DL4eBhyV62fKT9Ic0 c8fGaul0eApcZUcicW+4zAPWC4UI X-Google-Smtp-Source: AG47ELttX7eIIsLhiKTgOGfJa47jB6mez5SWLkW2/UYJaKKWMS2ukRubdUA2p21/orkaYhisPSm/zA== X-Received: by 10.28.134.5 with SMTP id i5mr655895wmd.127.1521576456967; Tue, 20 Mar 2018 13:07:36 -0700 (PDT) Received: from [10.192.166.0] (stargate.chelsio.com. [12.32.117.8]) by smtp.googlemail.com with ESMTPSA id m35sm5358804wrm.59.2018.03.20.13.07.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Mar 2018 13:07:36 -0700 (PDT) Sender: Navdeep Parhar Subject: Re: [HEADS UP] - OFED/RDMA stack update To: Hans Petter Selasky , Konstantin Belousov , "'freebsd-infiniband@freebsd.org'" , freebsd-drivers , Meny Yossefi , "'FreeBSD-stable@FreeBSD.org'" , freebsd-arch References: <1519683699.47932.5.camel@FreeBSD.org> <20180226224311.GT94212@kib.kiev.ua> <3027f48e-0ba8-555d-df23-d638303cb125@selasky.org> <20180317195200.GA5223@ox> <6d451a3b-a635-08b1-f8d4-52fdc48083d6@selasky.org> From: Navdeep Parhar Message-ID: <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> Date: Tue, 20 Mar 2018 13:07:31 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <6d451a3b-a635-08b1-f8d4-52fdc48083d6@selasky.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 20:07:39 -0000 On 03/17/2018 13:03, Hans Petter Selasky wrote: > On 03/17/18 20:52, Navdeep Parhar wrote: >> Hold your horses.=C2=A0 Do you have confirmation from the affected par= ty that >> the shims are adequate for them?=C2=A0 I have been waiting for that be= fore >> looking at this branch. >=20 > Hi Navdeep, >=20 > Mellanox has received an API list from at least one party, and has take= n > the action to support all the required APIs. >=20 >> Is the iw_cxgbe breakage a simple merge conflict as previously discuss= ed >> or do the shims require driver changes?=C2=A0=20 >=20 > It is a merge conflict. The code already compiles in 12-current. I tried backing out r329391 and r329017 in a local copy and then was able to merge r320418, r323082, and r326169 in that order without any conflicts. But iw_cxgbe/cm.c still doesn't compile in the projects branch because it has some socket code that relies on some of glebius's changes available only in head (I checked with him and they aren't MFC'able). I'm trying to figure out what to do about those. And what about the cxgb breakage? Is there any simple way to make an old style driver work with the new stack? T3 iw_cxgb in head was retired before the ofed overhaul. Regards, Navdeep From owner-freebsd-stable@freebsd.org Tue Mar 20 20:15:11 2018 Return-Path: Delivered-To: freebsd-stable@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 BDA9BF6AB55; Tue, 20 Mar 2018 20:15:11 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 588C3851AB; Tue, 20 Mar 2018 20:15:11 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id DF0E4260186; Tue, 20 Mar 2018 21:15:09 +0100 (CET) Subject: Re: [HEADS UP] - OFED/RDMA stack update To: Navdeep Parhar , Konstantin Belousov , "'freebsd-infiniband@freebsd.org'" , freebsd-drivers , Meny Yossefi , "'FreeBSD-stable@FreeBSD.org'" , freebsd-arch References: <1519683699.47932.5.camel@FreeBSD.org> <20180226224311.GT94212@kib.kiev.ua> <3027f48e-0ba8-555d-df23-d638303cb125@selasky.org> <20180317195200.GA5223@ox> <6d451a3b-a635-08b1-f8d4-52fdc48083d6@selasky.org> <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> From: Hans Petter Selasky Message-ID: <8aa54a0d-feaa-0c0f-82e2-5d32c873375e@selasky.org> Date: Tue, 20 Mar 2018 21:15:03 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 20:15:11 -0000 On 03/20/18 21:07, Navdeep Parhar wrote: > And what about the cxgb breakage? Is there any simple way to make an > old style driver work with the new stack? T3 iw_cxgb in head was > retired before the ofed overhaul. Hi, The most simple way is to pull this driver from Linux 4.9, including libcxgb for user-space, if possible, though I'm not sure about the FreeBSD specific areas of iWarp and socket handling. I think you know that part better than I do. After pulling from Linux 4.9 you need to extend this change to cover the iw_cxgb: https://svnweb.freebsd.org/changeset/base/330508 Or can you retire iw_cxgb? --HPS From owner-freebsd-stable@freebsd.org Tue Mar 20 21:11:52 2018 Return-Path: Delivered-To: freebsd-stable@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 6F31FF4A843 for ; Tue, 20 Mar 2018 21:11:52 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 F06FD6824A for ; Tue, 20 Mar 2018 21:11:51 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 29330a18-2c83-11e8-b951-f99fef315fd9 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 29330a18-2c83-11e8-b951-f99fef315fd9; Tue, 20 Mar 2018 21:10:48 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w2KLBmOa040960; Tue, 20 Mar 2018 15:11:48 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1521580308.54965.34.camel@freebsd.org> Subject: Re: Stability of 11.1S From: Ian Lepore To: Pete French , freebsd-stable@freebsd.org Date: Tue, 20 Mar 2018 15:11:48 -0600 In-Reply-To: <0317c52c-073a-bf53-b278-79f2407daa4b@ingresso.co.uk> References: <0317c52c-073a-bf53-b278-79f2407daa4b@ingresso.co.uk> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 21:11:52 -0000 On Tue, 2018-03-20 at 10:50 +0000, Pete French wrote: > > On 20/03/2018 01:05, Dewayne Geraghty wrote: > > > > We rebuild 11.1-Stable at least every two weeks.  Our build on the 7th > > Feb is in use on our development boxes, however the rebuild on 22nd > > resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE > > r329008.  Is anyone actually running a Stable that was built after 22nd > > Feb?  Could you please share the revision number? > r330769 works fine for me. I usually upgrade on a Monday, though > am holding off this week as am waiting for r330745 to land in STABLE, > but it works fine for me always. > > > > > > Because the churn in > > https://lists.freebsd.org/pipermail/svn-src-stable-11/2018-March/ is > > high we haven't been able to sight if a problem was identified and > > fixed; so we're really looking for a functioning stable that we can > > resume tracking. > I use this to eyeball whats gone into STABLE, its a daily read for me as  > I find keeping up with the mailing list tricky too. > > > http://www.freshbsd.org/?branch=RELENG_11&project=freebsd&; > > -pete. I meant to get that done over the weekend but didn't actually get to it until today.  I've MFC'd it to 11 as r331262, and I'm checking to see whether it should go back to 10-stable as well. -- Ian From owner-freebsd-stable@freebsd.org Tue Mar 20 22:17:21 2018 Return-Path: Delivered-To: freebsd-stable@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 984E1F4FBA5 for ; Tue, 20 Mar 2018 22:17:21 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [89.188.221.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "plan-b.pwste.edu.pl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EF29A6B57E for ; Tue, 20 Mar 2018 22:17:20 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (zarychtam@localhost [127.0.0.1]) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPS id w2KM8GnY026004 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 20 Mar 2018 23:08:16 +0100 (CET) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: (from zarychtam@localhost) by plan-b.pwste.edu.pl (8.15.2/8.15.2/Submit) id w2KM8FUw026002; Tue, 20 Mar 2018 23:08:15 +0100 (CET) (envelope-from zarychtam) Date: Tue, 20 Mar 2018 23:08:15 +0100 From: Marek Zarychta To: Jeremy Chadwick Cc: freebsd-stable@freebsd.org Subject: Re: Stability of 11.1S Message-ID: <20180320220815.GA14152@plan-b.pwste.edu.pl> References: <20180320181047.GA55267@icarus.home.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline In-Reply-To: <20180320181047.GA55267@icarus.home.lan> User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 22:17:21 -0000 --KsGdsel6WgEHnImy Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 20, 2018 at 11:10:47AM -0700, Jeremy Chadwick wrote: > (Please keep me CC'd as I am not subscribed to -stable) >=20 > I haven't seen any issues, but that means very little. Details: >=20 > Two boxes -- one bare metal, one VPS (QEMU): >=20 > $ uname -a > FreeBSD XXXXXXXXXXXXXXX 11.1-STABLE FreeBSD 11.1-STABLE #0 r330529: Tue M= ar 6 11:36:04 PST 2018 root@XXXXXXXXXXXXXXX:/usr/obj/usr/src/sys/X7SBA= _RELENG_11_amd64 amd64 > $ uptime > 10:33a.m. up 13 days, 18:10, 2 users, load averages: 0.15, 0.19, 0.16 >=20 > $ uname -a > FreeBSD XXXXXXXXXXXXXXXX 11.1-STABLE FreeBSD 11.1-STABLE #0 r330753: Sat = Mar 10 21:34:20 PST 2018 root@XXXXXXXXXXXXXXXX:/usr/obj/usr/src/sys/XXX= XXXXX_RELENG_11_amd64 amd64 > $ uptime > 10:33a.m. up 9 days, 10:46, 1 user, load averages: 0.31, 0.35, 0.31 >=20 > Systems were updated recently because I wanted to test Meltdown/Spectre > mitigation (more on that below). Prior to that, bare metal was running > 9.x with 200+ day uptimes, VPS was running 10.x with 80-90 day uptimes > (VPS providers' HV crashed, i.e. not FreeBSD issues). >=20 > Since load averages on FreeBSD 10.x onward cannot be trusted[1][2], I > have to explain the general system specs and loads: >=20 > Bare metal box is an Intel Core 2 Quad Q9550, 8GB RAM, doing very little > other than running Apache + lots of cron jobs for systems stuff + ZFS > with several disks (but not OS disk; that's a dedicated SSD w/ UFS + SU > (not SUJ). The cron jobs tend to stress the network and disk I/O a bit; > ZFS gets used every day, but only "heavily" during LAN file copies > to/from it (Samba is involved), and during nightly backups with rsync. >=20 > VPS box is some form of QEMU-based Intel Haswell CPU, 1GB RAM, doing > general things like Apache + postfix + SpamAssassin + some other > daemons, and a lot of Perl. Swap is used heavily on this machine. > Disks are all vtblk, and I use multiple to get capacity for the needed > space for /usr/src and /usr/obj. Everything is UFS + SU (not SUJ). >=20 > Things off the top of my head that might be relevant to you: >=20 > 1. r329462 added Meltdown/Spectre mitigation[3][4]. >=20 > Bare metal box has the below in /boot/loader.conf, since this is a > machine that does not need either given its environment: >=20 > # Disable PTI (Meltdown mitigation) and IBRS (Spectre mitigation); these > # are not relevant on this bare-metal system given its environment and > # use case. Details of these tunables is here: > # https://lists.freebsd.org/pipermail/freebsd-stable/2018-March/088526.ht= ml > # > vm.pmap.pti=3D"0" > hw.ibrs_disable=3D"1" >=20 > VPS box has no tunings of this sort, and ends up with the below, because > the hosting provider has no done BIOS + QEMU updates to add IBRS > support (they're very aware of it + have attempted it twice but > apparently it didn't go well): >=20 > vm.pmap.pti: 1 > hw.ibrs_disable: 1 > hw.ibrs_active: 0 >=20 > 2. If your CPU is an AMD Ryzen, there is a VERY long discussion on > -stable about problems with Ryzen manifesting itself in a very > uncomfortable way, leading to system lock-ups[5]. There are unofficial > patches you can try. I would recommend chiming in there and not here, > if relevant to your systems. >=20 > And yes, the massive number of MFCs that eadler@ is doing make tracking > down exact things more tedious than normal, especially when you have > sweeping commits like this one[6][7] (which, AFAIK, was acting as a > major blocker for several other MFCs and causing general merge > problems). >=20 > However, I commend his efforts; it's a massive undertaking (I would say > full-time job). We stable users must accept that we are running > stable/11 for a reason -- not only to get fixes faster, but to act a > form of "guinea pig" that don't want the risks of HEAD/CURRENT. The > more people using stable/11 the better overall feedback devs can get on > bugs/issues before making it into the next -RELEASE. This is exactly > why, for those of you who have known me over the years, I actually > "track" or "follow" commits as they come across. I do this by using the > FreshBSD site[8] alongside manual review of svnlite update output. I > generally know what files/bits are relevant to my interests. >=20 > Hope this gives you some things to think about. Good luck! >=20 > [1]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173541#c8 > [2]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D173541#c22 > [3]: https://lists.freebsd.org/pipermail/freebsd-stable/2018-February/088= 396.html > [4]: https://lists.freebsd.org/pipermail/freebsd-stable/2018-March/088526= =2Ehtml > [5]: https://lists.freebsd.org/pipermail/freebsd-stable/2018-January/thre= ad.html#88174 > [6]: http://www.freshbsd.org/commit/freebsd/r330897 > [7]: https://svnweb.freebsd.org/base?view=3Drevision&revision=3D330897 > [8]: http://www.freshbsd.org/?branch=3DRELENG_11&project=3Dfreebsd >=20 I follow STABLE uprgrading regularly bunch of servers, routers, PCs, laptop and even sometimes Raspberry Pi, always using builds made with meta mode without any serious issue in last months.=20 If I may put my two cents in, the term "guinea pigs" seems to be adequate definition here, but the old school of STABLE users although dying, as the whole BSD is, is still alive, despite a few premature MFCs, imprudent CoCs etc. STABLE seems to be all the same stable. I guess we should rather appreciate the efforts of commiters merging not only bug fixes but also new features than criticize every unattended MFC. --=20 Marek Zarychta --KsGdsel6WgEHnImy Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlqxhksACgkQdZ/s//1S jSziogf/dnkx8v5vtdnQ3613fmmgy3kKQv/7h1YSegXfXJp7niQbKbuKhCE8ccKk 5Q+zheDj1plkyrcorRuTPRzBFzXID/jnDm7fuWMPYNpQpaxXjCl4kcsO3S+S3f5p OBNznbHljm22X2gk8Ae46V9sr2R8UF1Ua2DPFrr0Elg0YIRH3g+XSnsT00mr3pMq hp+u6EbOiX+O038Vx8qNXnfU8WSuOVpUGAQtcVl7t8uwxOHvQx86Kmz+VZj61Ey9 vYLHu5QtVBx02EDCLz8I25OUcRfz3OKw76VfOAJAlJF+PUpIhAOyrjaOamKUczRn KVBgRWx0viIO5bCC51UwqfsxLlf1wA== =Czju -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- From owner-freebsd-stable@freebsd.org Wed Mar 21 08:52:16 2018 Return-Path: Delivered-To: freebsd-stable@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 098C1F54F37 for ; Wed, 21 Mar 2018 08:52:16 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 A04A483CE1 for ; Wed, 21 Mar 2018 08:52:15 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x22e.google.com with SMTP id x20so433274ywg.5 for ; Wed, 21 Mar 2018 01:52:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9b6Ckdo1NtBWCsCYPTfIqvt7hXmxrMjaK1kR7kBApbM=; b=GOXEGqhBR0LQUpseWm+rPoEAUSfkgmBUc9mp4H8m62Rb7LKUrjHXyP9UXJGA7s8ZCN +UStw3Lfgsj9cqFpAO76nbEP8Vb+AY2+G4LLIgpCoNgbWzO6WsYWgL1V6xz240/W4fhG owL+xkqqQmm+GA6MiNsmDi7WpHmmeB/DtTEQU= 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=9b6Ckdo1NtBWCsCYPTfIqvt7hXmxrMjaK1kR7kBApbM=; b=gAXrQVlkjbG+l/Qy1JdTs0IyEIrSSiZIczPp1ADRPoAizLa7TTrMDfJyQ+akL5wzt8 UQHCsf/HzF4Jg3QkcS2qOebOfmw07bsnaBj8vw07iLBqHcPQP/s9NG5Ek57rf9GoXBf8 OggdupVRpPSgMwa457tVsss1CdPYK941r26yMv8+wn1MzojfL0KAAdFQ6Cp1wOVEAihk Id9ZKMJ4YRtYY9mBrlhl/r8j2sFec5NgvSADhM6LjsdUEn+FQWmsLaMz4Zut7ZyccVAy XSV+SozyVL/H02EMo0EM3srgyiR6rSKlDXR1gm6OOJ+FlbFsKgcwiiW0WXMtqAMcs1+y uLug== X-Gm-Message-State: AElRT7FdpYRmKIBFr+zP41i40m0Fg4EP8jZGNfiBh+vNiH9EqWv4ZLhx zVFnq67wZ755QuEiNScRSaPJy/euI5JMiQ9RTDbkuA== X-Google-Smtp-Source: AG47ELvipc0ON1FYdPLqgTzBarUhPlqkoyVPH0OHrc+9KdiO9kPj65KY33Rt/KrQpgfc0c6s+11JCP5BOozKnb43p64= X-Received: by 10.129.114.6 with SMTP id n6mr7586406ywc.113.1521622334691; Wed, 21 Mar 2018 01:52:14 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:23d2:0:0:0:0:0 with HTTP; Wed, 21 Mar 2018 01:51:44 -0700 (PDT) In-Reply-To: <6b02d324-db1e-5136-e74e-0bf60e38726b@heuristicsystems.com.au> References: <6b02d324-db1e-5136-e74e-0bf60e38726b@heuristicsystems.com.au> From: Eitan Adler Date: Wed, 21 Mar 2018 01:51:44 -0700 Message-ID: Subject: Re: Stability of 11.1S To: Dewayne Geraghty Cc: FreeBSD Stable Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 08:52:16 -0000 On 19 March 2018 at 22:59, Dewayne Geraghty wrote: > Hi Eitan, > Agreed. Unfortunately all I have is that it abruptly shuts down. Both > under load (10,8,?) - during a full package rebuild (~1200 ports); and > during periods of idleness between 1am-2am. From our console.log there are > approximately 6 MARK entries in the logs, so it can be idle for that period > of time (2 hours) before halting, abruptly. There has been some additional conversation but just wanted to pick something to reply to: I will take full ownership if something I've MFCed caused breakage. That said I'm somewhat stuck unless I am able to reproduce the issue, or at least guess as to the cause. > PS Normally I would bisect, but we're converting 2 large PROLOG applications > to erlang... (prayers welcome) Both fun languages. -- Eitan Adler From owner-freebsd-stable@freebsd.org Wed Mar 21 10:19:37 2018 Return-Path: Delivered-To: freebsd-stable@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 C93E5F5A919 for ; Wed, 21 Mar 2018 10:19:37 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) (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 44BE0879E9 for ; Wed, 21 Mar 2018 10:19:36 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [217.29.44.10]) by gate2.intern.punkt.de with ESMTP id w2LAJTDL065984 for ; Wed, 21 Mar 2018 11:19:29 +0100 (CET) Received: from [217.29.44.49] ([217.29.44.49]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id w2LAJSn4024992 for ; Wed, 21 Mar 2018 11:19:28 +0100 (CET) (envelope-from hausen@punkt.de) From: "Patrick M. Hausen" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: IPv6 connectivity lost when combining if_bridge with a VLAN ... Message-Id: <55A61118-8BCC-4A09-9996-9EE06CB474DA@punkt.de> Date: Wed, 21 Mar 2018 11:19:28 +0100 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 10:19:38 -0000 Hi all, a follow-up to my discovery that certain chipsets don't support = 100baseTX any more. ;-) We use these servers as jail hosts and use if_bridge with VIMAGE and = iocage a lot. Our tried and true setup used to be like this: ------------- sysctl net.link.bridge.inherit_mac=3D1 ------------- ifconfig_ixl0=3D"up" ifconfig_ixl1=3D"up" cloned_interfaces=3D"bridge0 bridge1" ifconfig_bridge0_name=3D"inet0" ifconfig_bridge1_name=3D"mgmt0" ifconfig_inet0=3D"up addm ixl0" ifconfig_inet0_alias0=3D"inet
/24" ifconfig_inet0_ipv6=3D"inet6
/64 auto_linklocal" ifconfig_mgmt0=3D"up addm ixl1" ifconfig_mgmt0_alias0=3D"inet
/16" ifconfig_mgmt0_ipv6=3D"inet6 auto_linklocal" defaultrouter=3D"
" ipv6_defaultrouter=3D"fe80::11%inet0" ------------- So we use link-local v6 addresses for the default gateways in every = VLAN. The last octet in the GW address is simply the VLAN number ... Now, because I had to run improvised wires to a different switch before we get to upgrading the entire rack to Gbit connectivity we tried to use a single cable and a trunk port: ------------- sysctl net.link.bridge.inherit_mac=3D1 ------------- ifconfig_ixl0=3D"up" cloned_interfaces=3D"vlan7 vlan11 bridge0 bridge1" ifconfig_vlan7=3D"up vlan 7 vlandev ixl0" ifconfig_vlan11=3D"up vlan 11 vlandev ixl0" ifconfig_bridge0_name=3D"inet0" ifconfig_bridge1_name=3D"mgmt0" ifconfig_inet0=3D"up addm vlan7" ifconfig_inet0_alias0=3D"inet
/24" ifconfig_inet0_ipv6=3D"inet6
/64 auto_linklocal" ifconfig_mgmt0=3D"up addm vlan11" ifconfig_mgmt0_alias0=3D"inet
/16" ifconfig_mgmt0_ipv6=3D"inet6 auto_linklocal" defaultrouter=3D"
" ipv6_defaultrouter=3D"fe80::11%inet0" ------------- Nothing overly fancy in my opinion, just an orthogonal combination of technologies. In principle this seems to work, but ... - IPv4 connectivity comes up reliably and stays up - external IPv6 connectivity does not come up at reboot - I can ping6 the default GW from the machine (link-local address) - I can ping6 other machines in the same VLAN (global unicast) - route -6 delete default; route -6 add default fe80::11%inet0 restores = external connectivity - external connectivity get's lost again after a couple of hours Only IPv6 seems to be affected, not IPv4. Any ideas? ;-) Thanks, Patrick --=20 punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe info@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling From owner-freebsd-stable@freebsd.org Wed Mar 21 13:39:59 2018 Return-Path: Delivered-To: freebsd-stable@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 7A282F68DA9 for ; Wed, 21 Mar 2018 13:39:59 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [74.104.188.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 035956FCD7 for ; Wed, 21 Mar 2018 13:39:58 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) (authenticated bits=0) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPSA id w2LDWHCC032908 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 21 Mar 2018 09:32:28 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Subject: Re: Stability of 11.1S To: freebsd-stable@freebsd.org References: <6b02d324-db1e-5136-e74e-0bf60e38726b@heuristicsystems.com.au> From: George Mitchell Message-ID: Date: Wed, 21 Mar 2018 09:32:10 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gPXKm7CTCVupUu3e5ecReJ9T3XVbpIB02" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Wed, 21 Mar 2018 09:32:29 -0400 (EDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 13:39:59 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gPXKm7CTCVupUu3e5ecReJ9T3XVbpIB02 Content-Type: multipart/mixed; boundary="zLkoxq6B6KBmikGUkNTBNpKNB1nOuCXSw"; protected-headers="v1" From: George Mitchell To: freebsd-stable@freebsd.org Message-ID: Subject: Re: Stability of 11.1S References: <6b02d324-db1e-5136-e74e-0bf60e38726b@heuristicsystems.com.au> In-Reply-To: --zLkoxq6B6KBmikGUkNTBNpKNB1nOuCXSw Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 03/21/18 04:51, Eitan Adler wrote: > On 19 March 2018 at 22:59, Dewayne Geraghty > wrote: >> [...] >> PS Normally I would bisect, but we're converting 2 large PROLOG applic= ations >> to erlang... (prayers welcome) > [...] What next, converting a FORTH application to LISP? (Sorry, couldn't resist ...) -- George --zLkoxq6B6KBmikGUkNTBNpKNB1nOuCXSw-- --gPXKm7CTCVupUu3e5ecReJ9T3XVbpIB02 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlqyXuEACgkQwRES3m+p 4fmx/hAAjPAKe+Bf9lc/IODrTrRpUjHaz7vXJ9wE84Bs9eYJTlOwILHwY/QnqmLg zGxilMmLlph0zms8koXGsrAGEEdSKjY6ZjzYS/Z7/F5yfQ6Fcw/bf1Mo/3YiszZS h+d2bfJIJH2E/biHYKjVk6dECwVqU3TZ34drgsNW3nXMREcLAyUrTjRJaB9gmUyw eDR2nsGsFXyO1a7siHC97hYnw5snrOKpR9qECG9SQGP/404EO1LDfHOVtUApzMBI rinrZjjrSMxLvZxg4snotLeN7onwOGjjIpoabOsx44XyAkprE8VVu0e+1k1nCRIV BhFt/s8QUhoEoNUPFQVJwOwLQuC+yKawInaVLkTPoy4zpV3hyi9rGp7fIfsTUpPS VMvnHT5uqJb+JObOpW8/Cs4DX5sd2f1PjGtkm583/xjmX26HYRC5OlyshJosmJAJ JdX2W3KCWnqYP0ucNv4y5rAF+oBl8d4ND/vOaH8XKrF+ZHE5umLDkyXO9gJWXL1R Sd7MJIb7IYBFbt0CJMdFtCmWp6y6uX/28yXY2Gw9R6gdD56v6j1/EN7p+f6WpxRX HzUZX0CfG78JWbIxILhZ1wblRnX8PAluOsy0PO6nWs8V1gjZzJz/oR0FUrWVVB6Q c/l6xkro8smmSUWweusXjpSlvP6rdPl1TntvyAqefoJoPowRBqU= =NJXT -----END PGP SIGNATURE----- --gPXKm7CTCVupUu3e5ecReJ9T3XVbpIB02-- From owner-freebsd-stable@freebsd.org Wed Mar 21 14:59:26 2018 Return-Path: Delivered-To: freebsd-stable@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 859B6F4A910 for ; Wed, 21 Mar 2018 14:59:26 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (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 184CD73A9F for ; Wed, 21 Mar 2018 14:59:26 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x234.google.com with SMTP id y128so7003101iod.4 for ; Wed, 21 Mar 2018 07:59:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=6q6pKKXgfhg9rIV2aYg4+c6BdbFpHPXQFVV0ulJJHHc=; b=T1cJliOTFajMt19BdruG4MZMo+ntCQSbdqfTw3Sotg5pxFhPUUrswRzDCYc0C3XoYb UJeSHHSJhl+E8nJ/MvVWid0MHh6Mo0jgMjJxOMw4wCntV8FAPWx/B6KS2+qHu94GlOAJ 2X6JQiEcdSDBz55hbUBcWi1Cx/yMG3tSlkcwUg5BZUlxKanEiWhFCzvWqbseNfzRPKdq EpvHlq+Bf3of1mAVJCIoea0q4pV81sMcRWF3jqkV8yHiH7BFo80kwN9GX51HSZe03aab wJ9kESo6qRF+pMbneGl2w2R2DlV5muvaRytJ78/tD8WGS++OIQFMyB0zngqGfE81Geou RxNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=6q6pKKXgfhg9rIV2aYg4+c6BdbFpHPXQFVV0ulJJHHc=; b=ZWLVv++i8ybA6Z8sKb5IdIsqWNALTB6EbqipqcIUq8EDnVJC9PLZa5yfA5D0k1bgWF 3HrnSfUrxsBctrXoY6SUK9yOpwun+4ff2XhaL/LqyAQfUCnm1vBo/SFsJSiXQBVl6hOS RDc/4dD3o59Xk48rP6VU1n9QLF99cp/8Tlig4mu0Xv/7IOe9RHtEaJ4kxVUyx0eOTzL6 lQp0QDoZulhqDGf6DhrWiRVtAO6ZPFBJhSkd9miSnIMjhRf3tgyQhMTsfw5A/54l9XJa 9LCnxBL4GuWVAQiaXJ8iy41c6HI9oIcblxztAn+qvDjW3eBmj/g/92N2jdHtgoxZKhKj 7vCQ== X-Gm-Message-State: AElRT7FQPV8VWK4owEIfe9Fjw8uli7U2/HldJrtmIq1B1CUI3bhgB8oe e1DSll1xsh6NasnNhvPV/t0+VZ/3/PdeY6z6gbeWYQ== X-Google-Smtp-Source: AG47ELuORgSZjGE5FTSBqoIRu6x0UHDywLy56KyFn2hfuIvt9RMI/14Gyex0yijW4AiD6HATBG0CJJQoxV/6IW+vPvA= X-Received: by 10.107.12.230 with SMTP id 99mr20644360iom.117.1521644365348; Wed, 21 Mar 2018 07:59:25 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Wed, 21 Mar 2018 07:59:24 -0700 (PDT) X-Originating-IP: [50.227.106.226] In-Reply-To: References: <6b02d324-db1e-5136-e74e-0bf60e38726b@heuristicsystems.com.au> From: Warner Losh Date: Wed, 21 Mar 2018 08:59:24 -0600 X-Google-Sender-Auth: 4PvA8k7Zb733DxSS4rzU7NsVvU0 Message-ID: Subject: Re: Stability of 11.1S To: George Mitchell Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 14:59:26 -0000 On Wed, Mar 21, 2018 at 7:32 AM, George Mitchell wrote: > On 03/21/18 04:51, Eitan Adler wrote: > > On 19 March 2018 at 22:59, Dewayne Geraghty > > wrote: > >> [...] > >> PS Normally I would bisect, but we're converting 2 large PROLOG > applications > >> to erlang... (prayers welcome) > > [...] > > What next, converting a FORTH application to LISP? (Sorry, couldn't > resist ...) Back in college we had a gentleman who was working on his FORTH LISP interpreter.... But I can't recall if it was a FORTH interpreter written in LISP or a LISP interpreter written in FORTH. Warner From owner-freebsd-stable@freebsd.org Wed Mar 21 15:18:41 2018 Return-Path: Delivered-To: freebsd-stable@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 82233F4C80D for ; Wed, 21 Mar 2018 15:18:41 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 DA7BE75263 for ; Wed, 21 Mar 2018 15:18:40 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id g203-v6so8416427lfg.11 for ; Wed, 21 Mar 2018 08:18:40 -0700 (PDT) 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; bh=XjUiRpU4xt74VfciotGzdBH7/Hm/DrvucOsiozkbpO4=; b=dMsSHkYYOxR3rsHNWt2oMtvNq6fg4H3YgMOKNI5lyxNi2M8U+Lv+Hcq34wmsDQQn9T 5wRy3l+D23sULK9Zib8eWToMHkezO7AelOTLGw1fk1Srwm/5LQ3ZjyBnL5HKWfqQ37+8 0TKCQ93/hdXlqz4yDPoWhjJSROCvoTrkobOvYYR6VRnRWzgxWjLn04axJ2qesEyT9wIy xyImFY6jF4VACPUzt3mHk9DzKvn40lGZg4ILzwAzjJGyr+2hsIIlwcEJ5z7jRvzbiTuB te2WySiGQD0DitIudGJUzJJByNmOb/avNFuilvqAoAadIuM3aytSENGUSyhJboh2Z8Hl iBwg== 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; bh=XjUiRpU4xt74VfciotGzdBH7/Hm/DrvucOsiozkbpO4=; b=rGGn2Z8OLZ27tKyA7gikfdvuEKP496LxIl8cIrZdec15aRVtZYQRGC1SJiNfAjLV3z oz86ZQaX2p0bLcgGUV6Tk1KjCOspnVHks8ghdXDBpf4wAboJby7UT4Xo36RqxtMQ4+9r Nm7oJTuA2U5hxtD6Za0WsgOne2y5Zh3RYsR/BNtBLZE03nlE4IDrmsjCG5x0pCMUFsUk f+MSiD2Qx95NyyHqkGW19hgRrlCmrQBK2H9nn5bsHFXM0XYglh8pBfoPABH8QsUvznkq NQXx34u0uco/0QxMatkbXSel31wMsXTmzWNfAUoQsdSCtq0mSrx9YI8RE3onfvo78gBl QLUQ== X-Gm-Message-State: AElRT7EhV5or8tyU5Dr0jaKqnFyz31x2M//Nvm0WoXL/0tOdGwU3NWj6 Rpe8frR79VpykfyMyaysHOaqlQJ5rUoq6JUWsogV5Q== X-Google-Smtp-Source: AG47ELtg4kh8dyKt2HmkPoX19PN2rcjlcA8EjUjkAaEU387KWEcZLFpU93z4GLYl9+GcOZtXQBic4ZUjnSQqixqS+4E= X-Received: by 2002:a19:385e:: with SMTP id d30-v6mr13703232lfj.16.1521645518906; Wed, 21 Mar 2018 08:18:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.82.137 with HTTP; Wed, 21 Mar 2018 08:18:38 -0700 (PDT) In-Reply-To: References: <6b02d324-db1e-5136-e74e-0bf60e38726b@heuristicsystems.com.au> From: Freddie Cash Date: Wed, 21 Mar 2018 08:18:38 -0700 Message-ID: Subject: Re: Stability of 11.1S To: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 15:18:41 -0000 On Wed, Mar 21, 2018 at 7:59 AM, Warner Losh wrote: > On Wed, Mar 21, 2018 at 7:32 AM, George Mitchell > wrote: > > > On 03/21/18 04:51, Eitan Adler wrote: > > > On 19 March 2018 at 22:59, Dewayne Geraghty > > > wrote: > > >> [...] > > >> PS Normally I would bisect, but we're converting 2 large PROLOG > > applications > > >> to erlang... (prayers welcome) > > > [...] > > > > What next, converting a FORTH application to LISP? (Sorry, couldn't > > resist ...) > > > Back in college we had a gentleman who was working on his FORTH LISP > interpreter.... But I can't recall if it was a FORTH interpreter written = in > LISP or a LISP interpreter written in FORTH. > =E2=80=8BWhat happened to his first three LISP interpreters? ;) If at fir= st you don't succeed, try try try try again? Sorry, that one was just too easy, could not resist.=E2=80=8B :D =E2=80=8B I'll see myself out now. :)=E2=80=8B --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@freebsd.org Thu Mar 22 11:36:35 2018 Return-Path: Delivered-To: freebsd-stable@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 96CC6F5D0A7; Thu, 22 Mar 2018 11:36:35 +0000 (UTC) (envelope-from menyy@mellanox.com) Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0081.outbound.protection.outlook.com [104.47.2.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7BBC6F16B; Thu, 22 Mar 2018 11:36:34 +0000 (UTC) (envelope-from menyy@mellanox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=xSqSEk7bQzCSO9GCZEE7YUFP0SSSwMuhX1mjP0xuiXM=; b=BEgR3vl9wk6tvkwDcocXQXyEttaE82ERoVJAIBmTCpJpWP4aek61k1GBnqj2vouVj/txeGlWHToDiQD4VYpuIrvOAgJJ1CPrZZxQ76zzq1ERjur+DduNPjtoe0SH8o+k26KEsaTrQqlxDo8M8IGfBPbgB8Be58ixlffDLQsC0RI= Received: from VI1PR0501MB2863.eurprd05.prod.outlook.com (10.172.12.8) by VI1PR0501MB1949.eurprd05.prod.outlook.com (10.166.44.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.609.10; Thu, 22 Mar 2018 11:36:30 +0000 Received: from VI1PR0501MB2863.eurprd05.prod.outlook.com ([fe80::89b0:b1d8:fec6:c6ec]) by VI1PR0501MB2863.eurprd05.prod.outlook.com ([fe80::89b0:b1d8:fec6:c6ec%17]) with mapi id 15.20.0588.017; Thu, 22 Mar 2018 11:36:30 +0000 From: Meny Yossefi To: Navdeep Parhar , Hans Petter Selasky , Konstantin Belousov , "'freebsd-infiniband@freebsd.org'" , freebsd-drivers , "'FreeBSD-stable@FreeBSD.org'" , freebsd-arch Subject: RE: [HEADS UP] - OFED/RDMA stack update Thread-Topic: [HEADS UP] - OFED/RDMA stack update Thread-Index: AdNZQQ/RuIbNiZgtQumqRm3gP9gf8RVzyJuwAA/+YIAAAMCGgAN8uZ6AADjXuwAAAGXsAACXAjyAAFI51uA= Date: Thu, 22 Mar 2018 11:36:30 +0000 Message-ID: References: <1519683699.47932.5.camel@FreeBSD.org> <20180226224311.GT94212@kib.kiev.ua> <3027f48e-0ba8-555d-df23-d638303cb125@selasky.org> <20180317195200.GA5223@ox> <6d451a3b-a635-08b1-f8d4-52fdc48083d6@selasky.org> <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> In-Reply-To: <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=menyy@mellanox.com; x-originating-ip: [193.47.165.251] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; VI1PR0501MB1949; 7:Kgqx+KeBdP0T4GTiGJCDAJnI7Dm5jtmt9ltX29McXrKx/ipvJbcuiVwV5ayXaPAuNPm1qbLMsXuinxvndpvNZ7d7PckI1vDd06CEaj//AFp9RtnCtKtWahfS7u1jnYwl6MdiH+Bau3Sumhk/IvnC7qX8n7xzobU0175RukBfvb4T9VzgAG22NU+OCpDGgUiZL3tiI8h+5SzYFO3t4LGzAN617bvRevWR6VpK5vSQ0RFIze6wrHUlL9BjPRkXMfTo x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: 6afe4e1a-28cd-472c-9552-08d58fe927fe x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR0501MB1949; x-ms-traffictypediagnostic: VI1PR0501MB1949: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(85827821059158)(5213294742642); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231221)(944501327)(52105095)(6055026)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011); SRVR:VI1PR0501MB1949; BCL:0; PCL:0; RULEID:; SRVR:VI1PR0501MB1949; x-forefront-prvs: 0619D53754 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(39380400002)(396003)(366004)(39860400002)(13464003)(189003)(199004)(97736004)(305945005)(2950100002)(25786009)(74316002)(7736002)(5660300001)(76176011)(2906002)(2900100001)(3846002)(6116002)(7696005)(6436002)(55016002)(5250100002)(3280700002)(8936002)(3660700001)(8676002)(15650500001)(81166006)(81156014)(9686003)(33656002)(6246003)(99286004)(68736007)(105586002)(53936002)(110136005)(66066001)(229853002)(86362001)(106356001)(478600001)(26005)(93886005)(6506007)(102836004)(53546011)(59450400001)(446003)(316002)(186003)(14454004)(96633001)(491001); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0501MB1949; H:VI1PR0501MB2863.eurprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: mellanox.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: h7hNxaHtGPsV81roG0+iMi+ZiMWHtanS5K3xLt5phxKkSuD4gcxv2iZRocXcBZD6OVQ9p7j5Pl/alaMHCWzWrqGMPObRbArdDpPJqoBeHieMyPkgL/j6bEbWNa8OteexQ8sipQVgpPDUaYquJoKQ7rBMmRPK3T8AygqHf2Sk9oEq/sxAA0WkYAtNiq7hjXFqEgMZemMVg28nPv1gM5xZLxXq+/1BuCuoj55lFF7SxClHUVit9SsHOYhO+Qx4++V9mJgVQjHbhG1YlE5eRxI4kNdSgW7y8h6zkBhHxgtFhRO6wzE5189Sck3iHQCJIv9rqMKUrBFnyLsmdCwnrXdVIw== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: Mellanox.com X-MS-Exchange-CrossTenant-Network-Message-Id: 6afe4e1a-28cd-472c-9552-08d58fe927fe X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Mar 2018 11:36:30.2222 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0501MB1949 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 11:36:35 -0000 SGkgTmF2ZGVlcCwgDQoNCldoYXQncyB0aGUgY3VycmVudCBpV0FSUCBzdGF0dXMgb24gdGhlIHBy b2plY3QgYnJhbmNoPyANCklmIGl0J3MgcmVhZHkgd2UnZCBsaWtlIHRvIG1lcmdlIGl0IHRvIEZy ZWVCU0QxMS1TVEFCTEUgaW1tZWRpYXRlbHkuIA0KDQotTWVueQ0KDQoNCi0tLS0tT3JpZ2luYWwg TWVzc2FnZS0tLS0tDQpGcm9tOiBOYXZkZWVwIFBhcmhhciBbbWFpbHRvOm5wYXJoYXJAZ21haWwu Y29tXSBPbiBCZWhhbGYgT2YgTmF2ZGVlcCBQYXJoYXINClNlbnQ6IFR1ZXNkYXksIE1hcmNoIDIw LCAyMDE4IDEwOjA4IFBNDQpUbzogSGFucyBQZXR0ZXIgU2VsYXNreSA8aHBzQHNlbGFza3kub3Jn PjsgS29uc3RhbnRpbiBCZWxvdXNvdiA8a2liQGZyZWVic2Qub3JnPjsgJ2ZyZWVic2QtaW5maW5p YmFuZEBmcmVlYnNkLm9yZycgPGZyZWVic2QtaW5maW5pYmFuZEBmcmVlYnNkLm9yZz47IGZyZWVi c2QtZHJpdmVycyA8ZnJlZWJzZC1kcml2ZXJzQG1lbGxhbm94LmNvbT47IE1lbnkgWW9zc2VmaSA8 bWVueXlAbWVsbGFub3guY29tPjsgJ0ZyZWVCU0Qtc3RhYmxlQEZyZWVCU0Qub3JnJyA8RnJlZUJT RC1zdGFibGVARnJlZUJTRC5vcmc+OyBmcmVlYnNkLWFyY2ggPGZyZWVic2QtYXJjaEBmcmVlYnNk Lm9yZz4NClN1YmplY3Q6IFJlOiBbSEVBRFMgVVBdIC0gT0ZFRC9SRE1BIHN0YWNrIHVwZGF0ZQ0K DQpPbiAwMy8xNy8yMDE4IDEzOjAzLCBIYW5zIFBldHRlciBTZWxhc2t5IHdyb3RlOg0KPiBPbiAw My8xNy8xOCAyMDo1MiwgTmF2ZGVlcCBQYXJoYXIgd3JvdGU6DQo+PiBIb2xkIHlvdXIgaG9yc2Vz LsKgIERvIHlvdSBoYXZlIGNvbmZpcm1hdGlvbiBmcm9tIHRoZSBhZmZlY3RlZCBwYXJ0eSANCj4+ IHRoYXQgdGhlIHNoaW1zIGFyZSBhZGVxdWF0ZSBmb3IgdGhlbT/CoCBJIGhhdmUgYmVlbiB3YWl0 aW5nIGZvciB0aGF0IA0KPj4gYmVmb3JlIGxvb2tpbmcgYXQgdGhpcyBicmFuY2guDQo+IA0KPiBI aSBOYXZkZWVwLA0KPiANCj4gTWVsbGFub3ggaGFzIHJlY2VpdmVkIGFuIEFQSSBsaXN0IGZyb20g YXQgbGVhc3Qgb25lIHBhcnR5LCBhbmQgaGFzIA0KPiB0YWtlbiB0aGUgYWN0aW9uIHRvIHN1cHBv cnQgYWxsIHRoZSByZXF1aXJlZCBBUElzLg0KPiANCj4+IElzIHRoZSBpd19jeGdiZSBicmVha2Fn ZSBhIHNpbXBsZSBtZXJnZSBjb25mbGljdCBhcyBwcmV2aW91c2x5IA0KPj4gZGlzY3Vzc2VkIG9y IGRvIHRoZSBzaGltcyByZXF1aXJlIGRyaXZlciBjaGFuZ2VzPw0KPiANCj4gSXQgaXMgYSBtZXJn ZSBjb25mbGljdC4gVGhlIGNvZGUgYWxyZWFkeSBjb21waWxlcyBpbiAxMi1jdXJyZW50Lg0KDQpJ IHRyaWVkIGJhY2tpbmcgb3V0IHIzMjkzOTEgYW5kIHIzMjkwMTcgaW4gYSBsb2NhbCBjb3B5IGFu ZCB0aGVuIHdhcyBhYmxlIHRvIG1lcmdlIHIzMjA0MTgsIHIzMjMwODIsIGFuZCByMzI2MTY5IGlu IHRoYXQgb3JkZXIgd2l0aG91dCBhbnkgY29uZmxpY3RzLiAgQnV0IGl3X2N4Z2JlL2NtLmMgc3Rp bGwgZG9lc24ndCBjb21waWxlIGluIHRoZSBwcm9qZWN0cyBicmFuY2ggYmVjYXVzZSBpdCBoYXMg c29tZSBzb2NrZXQgY29kZSB0aGF0IHJlbGllcyBvbiBzb21lIG9mIGdsZWJpdXMncyBjaGFuZ2Vz IGF2YWlsYWJsZSBvbmx5IGluIGhlYWQgKEkgY2hlY2tlZCB3aXRoIGhpbSBhbmQgdGhleSBhcmVu J3QgTUZDJ2FibGUpLiAgSSdtIHRyeWluZyB0byBmaWd1cmUgb3V0IHdoYXQgdG8gZG8gYWJvdXQg dGhvc2UuDQoNCkFuZCB3aGF0IGFib3V0IHRoZSBjeGdiIGJyZWFrYWdlPyAgSXMgdGhlcmUgYW55 IHNpbXBsZSB3YXkgdG8gbWFrZSBhbiBvbGQgc3R5bGUgZHJpdmVyIHdvcmsgd2l0aCB0aGUgbmV3 IHN0YWNrPyAgVDMgaXdfY3hnYiBpbiBoZWFkIHdhcyByZXRpcmVkIGJlZm9yZSB0aGUgb2ZlZCBv dmVyaGF1bC4NCg0KUmVnYXJkcywNCk5hdmRlZXANCg0K From owner-freebsd-stable@freebsd.org Thu Mar 22 13:05:51 2018 Return-Path: Delivered-To: freebsd-stable@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 58807F65329 for ; Thu, 22 Mar 2018 13:05:51 +0000 (UTC) (envelope-from eugene@zhegan.in) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B9FF57389B for ; Thu, 22 Mar 2018 13:05:49 +0000 (UTC) (envelope-from eugene@zhegan.in) Received: from bsdrookie.norma.com. (asterisk.enaza.ru [91.237.76.254]) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id w2MD5jZa055710 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 22 Mar 2018 18:05:45 +0500 (YEKT) (envelope-from eugene@zhegan.in) To: "'FreeBSD-stable@FreeBSD.org'" From: "Eugene M. Zheganin" Subject: panic: vdrop: holdcnt 0 Message-ID: <64c1f57a-c461-cc48-8dfa-1b18ef3865e0@zhegan.in> Date: Thu, 22 Mar 2018 18:05:45 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spamd-Result: default: False [-998.10 / 25.00] WHITELISTED_IPS(-999.00)[91.237.76.254] AUTH_NA(1.00)[] RCVD_COUNT_TWO(0.00)[2] MID_RHS_MATCH_FROM(0.00)[] DMARC_NA(0.00)[zhegan.in] FROM_EQ_ENVFROM(0.00)[] ARC_NA(0.00)[] ASN(0.00)[asn:57973, ipnet:91.237.76.0/24, country:RU] FROM_HAS_DN(0.00)[] R_SPF_NA(0.00)[] TO_MATCH_ENVRCPT_ALL(0.00)[] TO_DN_ALL(0.00)[] MIME_GOOD(-0.10)[text/plain] RCPT_COUNT_ONE(0.00)[1] RCVD_TLS_ALL(0.00)[] R_DKIM_NA(0.00)[] IP_SCORE(0.00)[ip: (-9.88), ipnet: 91.237.76.0/24(-7.79), asn: 57973(-4.87), country: RU(0.11)] X-Rspamd-Server: localhost X-Rspamd-Scan-Time: 0.77 X-Rspamd-Queue-ID: w2MD5jZa055710 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 13:05:51 -0000 Hi, today I eventyally got "panic: vdrop: holdcnt 0" on an iSCSI host, on an 11.1. Since I don't see any decent information on this - I just wanted to ask - what this kind of panic generally mean ? And where do I go with this. The only PR I see is about 9.[, and the author there got multiple reproducing crashes, not just one. Thanks. From owner-freebsd-stable@freebsd.org Thu Mar 22 13:37:13 2018 Return-Path: Delivered-To: freebsd-stable@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 68217F67E0F for ; Thu, 22 Mar 2018 13:37:13 +0000 (UTC) (envelope-from eugene@zhegan.in) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B25BF74D23 for ; Thu, 22 Mar 2018 13:37:12 +0000 (UTC) (envelope-from eugene@zhegan.in) Received: from bsdrookie.norma.com. (asterisk.enaza.ru [91.237.76.254]) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id w2MDbASN056565 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 22 Mar 2018 18:37:10 +0500 (YEKT) (envelope-from eugene@zhegan.in) Subject: Re: panic: vdrop: holdcnt 0 To: freebsd-stable@freebsd.org References: <64c1f57a-c461-cc48-8dfa-1b18ef3865e0@zhegan.in> From: "Eugene M. Zheganin" Message-ID: <8addac2d-4b04-1a87-8f5f-492f53fb783e@zhegan.in> Date: Thu, 22 Mar 2018 18:37:10 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <64c1f57a-c461-cc48-8dfa-1b18ef3865e0@zhegan.in> Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spamd-Result: default: False [-998.10 / 25.00] WHITELISTED_IPS(-999.00)[91.237.76.254] AUTH_NA(1.00)[] RCVD_COUNT_TWO(0.00)[2] MID_RHS_MATCH_FROM(0.00)[] DMARC_NA(0.00)[zhegan.in] FROM_EQ_ENVFROM(0.00)[] ARC_NA(0.00)[] ASN(0.00)[asn:57973, ipnet:91.237.76.0/24, country:RU] FROM_HAS_DN(0.00)[] R_SPF_NA(0.00)[] TO_MATCH_ENVRCPT_ALL(0.00)[] TO_DN_NONE(0.00)[] MIME_GOOD(-0.10)[text/plain] RCPT_COUNT_ONE(0.00)[1] RCVD_TLS_ALL(0.00)[] R_DKIM_NA(0.00)[] IP_SCORE(0.00)[ip: (-9.88), ipnet: 91.237.76.0/24(-7.79), asn: 57973(-4.87), country: RU(0.11)] X-Rspamd-Server: localhost X-Rspamd-Scan-Time: 0.57 X-Rspamd-Queue-ID: w2MDbASN056565 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 13:37:13 -0000 Hello, On 22.03.2018 18:05, Eugene M. Zheganin wrote: > today I eventyally got "panic: vdrop: holdcnt 0" on an iSCSI host, on > an 11.1. Since I don't see any decent information on this - I just > wanted to ask - what this kind of panic generally mean ? And where do > I go with this. The only PR I see is about 9.[, and the author there > got multiple reproducing crashes, not just one. To be more specific - here's a backtrace: Unread portion of the kernel message buffer: panic: vdrop: holdcnt 0 cpuid = 11 KDB: stack backtrace: #0 0xffffffff80aadac7 at kdb_backtrace+0x67 #1 0xffffffff80a6bba6 at vpanic+0x186 #2 0xffffffff80a6ba13 at panic+0x43 #3 0xffffffff80b28739 at _vdrop+0x3e9 #4 0xffffffff80b295d8 at vputx+0x2f8 #5 0xffffffff80b38342 at vn_close1+0x182 #6 0xffffffff82639d1a at ctl_be_block_ioctl+0x86a #7 0xffffffff82632bdc at ctl_ioctl+0x48c #8 0xffffffff8093ae38 at devfs_ioctl_f+0x128 #9 0xffffffff80ac9415 at kern_ioctl+0x255 #10 0xffffffff80ac914f at sys_ioctl+0x16f #11 0xffffffff80ee0394 at amd64_syscall+0x6c4 #12 0xffffffff80ec39bb at Xfast_syscall+0xfb Uptime: 1d17h36m25s I also have the full crashdump and stuff, in case someone will show an interest. This is currently the only panic I got, but this happened on a production system, which is, by the way 11.1-RELEASE-p6 r329259M, an iSCSI host and M stands for iscsi holdoff patch which was recently MFC'd, but appeared later than the 11.1 was released. Eugene. From owner-freebsd-stable@freebsd.org Thu Mar 22 15:10:20 2018 Return-Path: Delivered-To: freebsd-stable@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 A865CF4C5B1 for ; Thu, 22 Mar 2018 15:10:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::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 3AFA779833 for ; Thu, 22 Mar 2018 15:10:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22c.google.com with SMTP id h23so11359216iob.11 for ; Thu, 22 Mar 2018 08:10:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=BSIJCfDLCtALJgJxgLUI3bO1lNezrh3WVOBS0afg8oE=; b=UHR6VlM+Wn4by7r+7H1vczTmu2ZXsIyX8Y66hOq0I77urzR2wtILkl+Rk1+89Ff9om p9oxe+xv64DxGOh5y1J9KmUA2BJUB/2tbN3z+RM31097zkTMUsrI+O115IKgGCR8W44i MZLojuDgDghDv1mNE4HGm/AVloa2Nm/09+CllOLm468NHTT9iV7EqZcLm/xEjZOrAxFB Xc31XcM6rsowlFrsNdaqGub9lmnJhoL/058qrgxW6egCILtZxQzpB1SeBHg6089aJK9b eSNauN7dkVuJcSrTctbOTJm0MxhNqnvAZqZcxNLOc/1HK/UAFE6wsrKGf9URaukAXJhn CYOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=BSIJCfDLCtALJgJxgLUI3bO1lNezrh3WVOBS0afg8oE=; b=JrMdPVUbvVVxyAVfxpvuV/eVcbdWQgB5ZqGFluPgRIFysJcXFhkQZioQblq5PQei0m LXFztqOBHIrOCUf8ARgOgwp93yYRpSRnyC2cRQ1fpJUZ/oXqT8/So9ignoFtcdX15P1d 6rBkOPx956IkaRY6JDC/nvvlup0gUmEu9yD47jNZy6ScZr/LRDm0aODi0Dr/DlKsMEbu gD6XkxdFHgaPTHJjqnbe3vk3yVZpA2S1f+IZZ1dVLCAq/EMiCSM9WhqxkxlO4bbefCED Pp2aIkZnmO4u/CuJ2RIyPtxBTUWjXCPmJsDshkvRm/0Blx6SMpUjGaOgyTCtVPIZAFNH pVhw== X-Gm-Message-State: AElRT7G7lebt2eHPZ/ZZ6TpRUshMy3hAOrKAknu/YLdSHax57pbyN5nv OONgdPF6bQOhLBHjXin4oNgdBrp/4lj5Pd9KalYdmQ== X-Google-Smtp-Source: AG47ELvK+Icy1h5C1PW/jHXM4W12F8e/xyWSfchcoHgyqFz8HW6+bEUKj57VMi5TXMXShv723qGyXiwHTVjZdnu7tmI= X-Received: by 10.107.162.146 with SMTP id l140mr21834598ioe.39.1521731419515; Thu, 22 Mar 2018 08:10:19 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Thu, 22 Mar 2018 08:10:18 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:18a2:a4f7:170:8dd9] In-Reply-To: <8addac2d-4b04-1a87-8f5f-492f53fb783e@zhegan.in> References: <64c1f57a-c461-cc48-8dfa-1b18ef3865e0@zhegan.in> <8addac2d-4b04-1a87-8f5f-492f53fb783e@zhegan.in> From: Warner Losh Date: Thu, 22 Mar 2018 09:10:18 -0600 X-Google-Sender-Auth: RSJQi2s3JkN8fUQ4civdUS-LDgc Message-ID: Subject: Re: panic: vdrop: holdcnt 0 To: "Eugene M. Zheganin" Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 15:10:21 -0000 On Thu, Mar 22, 2018 at 7:37 AM, Eugene M. Zheganin wrote: > Hello, > > On 22.03.2018 18:05, Eugene M. Zheganin wrote: > >> today I eventyally got "panic: vdrop: holdcnt 0" on an iSCSI host, on an >> 11.1. Since I don't see any decent information on this - I just wanted to >> ask - what this kind of panic generally mean ? And where do I go with this. >> The only PR I see is about 9.[, and the author there got multiple >> reproducing crashes, not just one. >> > To be more specific - here's a backtrace: > > Unread portion of the kernel message buffer: > panic: vdrop: holdcnt 0 > cpuid = 11 > KDB: stack backtrace: > #0 0xffffffff80aadac7 at kdb_backtrace+0x67 > #1 0xffffffff80a6bba6 at vpanic+0x186 > #2 0xffffffff80a6ba13 at panic+0x43 > #3 0xffffffff80b28739 at _vdrop+0x3e9 > #4 0xffffffff80b295d8 at vputx+0x2f8 > #5 0xffffffff80b38342 at vn_close1+0x182 > #6 0xffffffff82639d1a at ctl_be_block_ioctl+0x86a > #7 0xffffffff82632bdc at ctl_ioctl+0x48c > #8 0xffffffff8093ae38 at devfs_ioctl_f+0x128 > #9 0xffffffff80ac9415 at kern_ioctl+0x255 > #10 0xffffffff80ac914f at sys_ioctl+0x16f > #11 0xffffffff80ee0394 at amd64_syscall+0x6c4 > #12 0xffffffff80ec39bb at Xfast_syscall+0xfb > Uptime: 1d17h36m25s > > I also have the full crashdump and stuff, in case someone will show an > interest. This is currently the only panic I got, but this > happened on a production system, which is, by the way 11.1-RELEASE-p6 > r329259M, an iSCSI host and M stands for iscsi holdoff patch > which was recently MFC'd, but appeared later than the 11.1 was released. Can you try the latest -current with https://reviews.freebsd.org/D14792? Warner From owner-freebsd-stable@freebsd.org Thu Mar 22 20:37:34 2018 Return-Path: Delivered-To: freebsd-stable@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 3A13AF696EC; Thu, 22 Mar 2018 20:37:34 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 B6E3E6A1D5; Thu, 22 Mar 2018 20:37:33 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id f125so18458009wme.4; Thu, 22 Mar 2018 13:37:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=bTTEGC4bxXV9VWskmJ+XUHvUmFSddzsDWEci5AUklFU=; b=AEaONByuIPmX/AFJjohmxxJ88OAyC3nb9E2Gl2VHT59jwzBKsJg7hdKf4C86gg/Z6P faSC35WVTGg7nVOitFbT/nFngKj77O0zA0dYGz1lvOdodPe+BWOh0pHKOWlkV77p1SPl QSqOA0Xi2jDDZmFk8qA+mFr4S6UxJ8BB08k9eu5DXCMGR4BhLWKdv8gbPAIdRdfwn/aN OwSPgS/PjSyfy4Y+OIyrV1PHKmFYnhP+bGJNxmJ+vcjJGnif0SinZvNSXg29tU2VMYHI tc/DJ8QjrmWbhTExGApRGRpmqEEFz+spIXldcWPegBQUu0Pn3G+KDIcjpJUumItnN225 Qe7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bTTEGC4bxXV9VWskmJ+XUHvUmFSddzsDWEci5AUklFU=; b=KOMJiHeUrNK0F+8WJ4yaaKOTGnvmTNuDmfyA92aN9eFa0vDUkBlv4W97GZbeCYQ6Tv 6rcbLFH6HLD0tDcY6BaBe1oDhtQc8B3xkyXUymm/ZfLVKxwE+pndgv1funFpxx7l/PWC 7BpVLOdhQ6KjnGyXnoUsJC9aW3FpFbNacAQ18ToM5QNUUAqCZnWDlhiqgR2vGHaVhYrd NblajIn0mwQ7abHi2hynNRPfIp444nT5wn6Qt+ZdSWlmJi+wy7DqdiQPc78pIJO8FP88 PLfEOnNSl6mAE3jeNTyqYa6bTMAiIRYZWsatvYrkzaEDHf0jEUieCKnZEI5bhqyTCOuf +CHA== X-Gm-Message-State: AElRT7EKZ5T6+Ybipw//TzGctw+9tUINm/4Zahcdr1hjVAQHnhY08NwA 6ncj6K8EgNIPd4VCY4WPdXXHvee3 X-Google-Smtp-Source: AG47ELugfQaH6FygNuBWVfMizFCUilu+vsGhAqxO9h6c7jYLOg1d/lebU2HFJTg68sQHDwuP3T0OtA== X-Received: by 10.28.220.2 with SMTP id t2mr7141293wmg.21.1521751052284; Thu, 22 Mar 2018 13:37:32 -0700 (PDT) Received: from [10.192.166.0] (stargate.chelsio.com. [12.32.117.8]) by smtp.googlemail.com with ESMTPSA id v23sm6815589wmc.22.2018.03.22.13.37.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 13:37:31 -0700 (PDT) Sender: Navdeep Parhar Subject: Re: [HEADS UP] - OFED/RDMA stack update To: Meny Yossefi , Hans Petter Selasky , Konstantin Belousov , "'freebsd-infiniband@freebsd.org'" , freebsd-drivers , "'FreeBSD-stable@FreeBSD.org'" , freebsd-arch References: <1519683699.47932.5.camel@FreeBSD.org> <20180226224311.GT94212@kib.kiev.ua> <3027f48e-0ba8-555d-df23-d638303cb125@selasky.org> <20180317195200.GA5223@ox> <6d451a3b-a635-08b1-f8d4-52fdc48083d6@selasky.org> <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> From: Navdeep Parhar Message-ID: Date: Thu, 22 Mar 2018 13:37:27 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 20:37:34 -0000 iw_cxgbe still doesn't build in the branch because of some socket changes in head that are not in 11. I need to add the 11 equivalent of the dequeue_socket code to iw_cxgbe to get it to compile, and then try it to see if it actually works. Regards, Navdeep On 03/22/2018 04:36, Meny Yossefi wrote: > Hi Navdeep,=20 >=20 > What's the current iWARP status on the project branch?=20 > If it's ready we'd like to merge it to FreeBSD11-STABLE immediately.=20 >=20 > -Meny >=20 >=20 > -----Original Message----- > From: Navdeep Parhar [mailto:nparhar@gmail.com] On Behalf Of Navdeep Pa= rhar > Sent: Tuesday, March 20, 2018 10:08 PM > To: Hans Petter Selasky ; Konstantin Belousov ; 'freebsd-infiniband@freebsd.org' ; freebsd-drivers ; Meny Yossefi ; 'FreeBSD-stable@FreeBSD.org' ;= freebsd-arch > Subject: Re: [HEADS UP] - OFED/RDMA stack update >=20 > On 03/17/2018 13:03, Hans Petter Selasky wrote: >> On 03/17/18 20:52, Navdeep Parhar wrote: >>> Hold your horses.=C2=A0 Do you have confirmation from the affected pa= rty=20 >>> that the shims are adequate for them?=C2=A0 I have been waiting for t= hat=20 >>> before looking at this branch. >> >> Hi Navdeep, >> >> Mellanox has received an API list from at least one party, and has=20 >> taken the action to support all the required APIs. >> >>> Is the iw_cxgbe breakage a simple merge conflict as previously=20 >>> discussed or do the shims require driver changes? >> >> It is a merge conflict. The code already compiles in 12-current. >=20 > I tried backing out r329391 and r329017 in a local copy and then was ab= le to merge r320418, r323082, and r326169 in that order without any confl= icts. But iw_cxgbe/cm.c still doesn't compile in the projects branch bec= ause it has some socket code that relies on some of glebius's changes ava= ilable only in head (I checked with him and they aren't MFC'able). I'm t= rying to figure out what to do about those. >=20 > And what about the cxgb breakage? Is there any simple way to make an o= ld style driver work with the new stack? T3 iw_cxgb in head was retired = before the ofed overhaul. >=20 > Regards, > Navdeep >=20 From owner-freebsd-stable@freebsd.org Fri Mar 23 02:40:15 2018 Return-Path: Delivered-To: freebsd-stable@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 5B2D8F62872 for ; Fri, 23 Mar 2018 02:40:15 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from hermes.heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 805397B2E5 for ; Fri, 23 Mar 2018 02:40:13 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from [10.0.5.3] (noddy.hs [10.0.5.3]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.15.2/8.15.2) with ESMTPSA id w2N2ciAe084090 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 23 Mar 2018 13:38:55 +1100 (AEDT) (envelope-from dewayne.geraghty@heuristicsystems.com.au) X-Authentication-Warning: b3.hs: Host noddy.hs [10.0.5.3] claimed to be [10.0.5.3] Subject: Re: Stability of 11.1S References: <6b02d324-db1e-5136-e74e-0bf60e38726b@heuristicsystems.com.au> Cc: FreeBSD-STABLE Mailing List To: Freddie Cash , Eitan Adler From: Dewayne Geraghty Message-ID: Date: Fri, 23 Mar 2018 13:38:33 +1100 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 In-Reply-To: Content-Language: en-AU MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 02:40:15 -0000 From owner-freebsd-stable@freebsd.org Fri Mar 23 15:01:37 2018 Return-Path: Delivered-To: freebsd-stable@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 3C47DF4F093 for ; Fri, 23 Mar 2018 15:01:37 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (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 9E25F7846D for ; Fri, 23 Mar 2018 15:01:36 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: (qmail 33898 invoked from network); 23 Mar 2018 15:01:34 -0000 Received: from elektropost.org (HELO elektropost.org) (joerg?surmann) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 23 Mar 2018 15:01:34 -0000 To: freebsd-stable@freebsd.org. From: Joerg Surmann Subject: Two NIC's inside a Jail Message-ID: <785ce70f-3f2d-3422-0e95-146b05f7f768@elektropost.org> Date: Fri, 23 Mar 2018 16:01:30 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sqBIekZkZ7zcxGyRub0v1VWwKHHtNEmLJ" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 15:01:37 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --sqBIekZkZ7zcxGyRub0v1VWwKHHtNEmLJ Content-Type: multipart/mixed; boundary="h7IyF2OY3LAHI0zaLVdIU8LDVer66a1qh"; protected-headers="v1" From: Joerg Surmann To: freebsd-stable@freebsd.org. Message-ID: <785ce70f-3f2d-3422-0e95-146b05f7f768@elektropost.org> Subject: Two NIC's inside a Jail --h7IyF2OY3LAHI0zaLVdIU8LDVer66a1qh Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: de-DE Hi all, I have a Problem to understund how to manage 2 Networks inside a Jail. i have create a jail (using ezjail) with a alias IP. in rc.conf (on Host): ifconfig_vmx0=3D"inet 192.168.100.1 netmask 255.255.255.0" ifconfig_vmx0_alias0=3D"inet 192.168.100.2 netmask 255.255.255.0"=C2=A0 <= - this is the jail ip Inside the jail running apachhe24. Now i add a new NIC to the System. in rc.conf (on Host): ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" in /usr/local/etc/ezjail/myjail.conf: i add the new ip export jail_myjail_ip=3D"192.168.100.2,213.70.80.92" Restart the jail and ifconfig looks fine. vmx0 -> inet 192.168.100.2 em0=C2=A0 -> inet 213.70.80.92 Apache Listen on all NIC's () But i can see my Website only via 192.168.100.2 from intern Network. The Host is behind a Firewall. The IP=C2=A0 213.70.80.92 is enabled for incomming Traffic. When i give the Hostname in a Browser i become "connection Timeout". What is to do that the Host is accessable from Inet? Thanks Holm --h7IyF2OY3LAHI0zaLVdIU8LDVer66a1qh-- --sqBIekZkZ7zcxGyRub0v1VWwKHHtNEmLJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKgIE1afOeXZNzpBEGHz25TAa4ssFAlq1FsoACgkQGHz25TAa 4ss79BAAsg85bLX26JL2OcuXwLGI9zdtSULoyfeTua5ucXESeN/M682RV1g9mLim SbbUYK0VbesCe752vYRsDFQbVWLNRsE77d+fTH7fWnxR/Jb3bmcOX+PlyN2cSWpu hbgOyuS+YMZ/FcUnVGwgtCXVhtuxVIy0BckkBf+x8px2SkdyAGy2mSwkP0/kTenj g4S+QyCcMBrWrQZodaRoZterMPtqFtA1jgYxBuyv9fvt+3MmdyycYyaNoQAX1HPq QvVoxPlx3SnZwC8+1NTKPvQ7tJXC3qDtukQ4faCrt05nq1+BernJjgPZwPHnMv+X w33UqfjPpL6nl1IA5AlGN1PuEVaS4EFkMEbbuDK+WWAeiSzZSZYkrD6yqfrC21jZ wJBEMIW4+ZC9DC6920EF88I/DW0++D4eV7k4jAKXN8iuOXeThZb8fR0Kw4gU10bn LTUOTx+Sdfq2qY/Y1bcH31eD1wC9oYKnB/oPvgxdSKl2rYqOzsVUoq4R5Ry37HdC 43cqDBp7QykcEqvIA9z6405gc47hiLS+yEVCfnfeL5o01UABDfWf2r6l2i8W4m1U J3KJ6U1cNkiwDRB6oC8GJPdiDHVA/PJKkWIV88auUh7swZeYyqzCAkQ24yMlvYxv LoYu5ZsoXBvaz/dZHg9w0ZJV3rBr+RdOKLl1APOJb5eWXlT7/b8= =5wL+ -----END PGP SIGNATURE----- --sqBIekZkZ7zcxGyRub0v1VWwKHHtNEmLJ-- From owner-freebsd-stable@freebsd.org Fri Mar 23 17:25:09 2018 Return-Path: Delivered-To: freebsd-stable@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 D878BF5C353 for ; Fri, 23 Mar 2018 17:25:08 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (unknown [IPv6:2001:678:618::40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "plan-b.pwste.edu.pl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5CC6A810BA for ; Fri, 23 Mar 2018 17:25:07 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (zarychtam@localhost [127.0.0.1]) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPS id w2NHP4Zf061954 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 23 Mar 2018 18:25:05 +0100 (CET) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: (from zarychtam@localhost) by plan-b.pwste.edu.pl (8.15.2/8.15.2/Submit) id w2NHP4Fa061952; Fri, 23 Mar 2018 18:25:04 +0100 (CET) (envelope-from zarychtam) Date: Fri, 23 Mar 2018 18:25:04 +0100 From: Marek Zarychta To: Joerg Surmann Cc: freebsd-stable@freebsd.org Subject: Re: Two NIC's inside a Jail Message-ID: <20180323172504.GA55971@plan-b.pwste.edu.pl> References: <785ce70f-3f2d-3422-0e95-146b05f7f768@elektropost.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <785ce70f-3f2d-3422-0e95-146b05f7f768@elektropost.org> User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 17:25:09 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 23, 2018 at 04:01:30PM +0100, Joerg Surmann wrote: > Hi all, >=20 > I have a Problem to understund how to manage 2 Networks inside a Jail. >=20 > i have create a jail (using ezjail) with a alias IP. in rc.conf (on > Host): >=20 > ifconfig_vmx0=3D"inet 192.168.100.1 netmask 255.255.255.0" > ifconfig_vmx0_alias0=3D"inet 192.168.100.2 netmask 255.255.255.0"=C2=A0 <- > this is the jail ip >=20 > Inside the jail running apachhe24. >=20 > Now i add a new NIC to the System. in rc.conf (on Host): > ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >=20 > in /usr/local/etc/ezjail/myjail.conf: i add the new ip export > jail_myjail_ip=3D"192.168.100.2,213.70.80.92" >=20 > Restart the jail and ifconfig looks fine. vmx0 -> inet 192.168.100.2 > em0=C2=A0 -> inet 213.70.80.92 >=20 > Apache Listen on all NIC's () But i can see my > Website only via 192.168.100.2 from intern Network. >=20 > The Host is behind a Firewall. The IP=C2=A0 213.70.80.92 is enabled for > incomming Traffic. >=20 > When i give the Hostname in a Browser i become "connection Timeout". >=20 > What is to do that the Host is accessable from Inet? >=20 Hi Joerg,=20 I guess your host has default gw reachable via vmx0 and second interface em0 is connected and was reachable at least from firewall protecting address 213.70.80.92? If it is true then you should add:=20 to /usr/local/etc/ezjail/myjail.conf=20 export jail_myjail_ip=3D"lo1|127.0.1.1,vmx0|192.168.100.2,em0|213.70.80.92" export jail_myjail_fib=3D"1" to /etc/rc.conf static_routes=3D"net_jails" route_net_jails=3D"default 213.70.80.x -fib 1" to /boot/loader.conf net.fibs=3D"2" Eventually take a look at setfib(1) and also consider migrating em adapter to second vmx which shuld be faster and more flexible. IMHO this questions should be asked rather on freebsd-net list than here. --=20 Marek Zarychta --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlq1OG0ACgkQdZ/s//1S jSzW5AgAoHjVX3DhoUa4Ey9EvKYmNATgYmY9HVLfSGufV33YWyty5QoE1YH8idO8 hbk2BWLE+tnKrMo6lhbrb79OgkyusC0H960KAOm8C4AgfM8zyou4/Vbqu3I6pbXB RNH4fG2huX0ZOHepuZvtLUT/YcY++b3eSrjYMhokzgZdK3APzmQhLtyeT5t4H1MD ou2H+z9t+gjp5OE8x39lJCBeGS3jyuPLbPUUr3h2UgYxKZkbG5menfsx12PxcpcZ 0bSL77S1VZI0+RKtEbaZdhuAXt0BLQ3tMk/8ct5CIpoi67lfYt5t7MTmw8DUAUlJ QPC7nglxf/2GLhGuf46Fv2APhfD31w== =Fm9O -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-stable@freebsd.org Fri Mar 23 19:17:30 2018 Return-Path: Delivered-To: freebsd-stable@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 E508AF66265 for ; Fri, 23 Mar 2018 19:17:29 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (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 5F8A0874B1 for ; Fri, 23 Mar 2018 19:17:29 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: (qmail 93349 invoked from network); 23 Mar 2018 19:17:28 -0000 Received: from elektropost.org (HELO elektropost.org) (joerg?surmann) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 23 Mar 2018 19:17:28 -0000 Subject: Re: Two NIC's inside a Jail To: Marek Zarychta Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org References: <785ce70f-3f2d-3422-0e95-146b05f7f768@elektropost.org> <20180323172504.GA55971@plan-b.pwste.edu.pl> From: joerg_surmann Message-ID: Date: Fri, 23 Mar 2018 20:17:27 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180323172504.GA55971@plan-b.pwste.edu.pl> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="QabuUyHbzzRJWlhPrBEMbgUkV38HLlAPv" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 19:17:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --QabuUyHbzzRJWlhPrBEMbgUkV38HLlAPv Content-Type: multipart/mixed; boundary="XLdbuKE7TcH5190G2OxcWomUP464lUdtA"; protected-headers="v1" From: joerg_surmann To: Marek Zarychta Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Message-ID: Subject: Re: Two NIC's inside a Jail References: <785ce70f-3f2d-3422-0e95-146b05f7f768@elektropost.org> <20180323172504.GA55971@plan-b.pwste.edu.pl> In-Reply-To: <20180323172504.GA55971@plan-b.pwste.edu.pl> --XLdbuKE7TcH5190G2OxcWomUP464lUdtA Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: de-DE Hi, thanks for yor help. I can't find a solution. But i have find a starnge ip config. in rc.conf on Host(not jail) ifconfig_vmx0_alias1=3D"inet 192.168.100.2=C2=A0 netmask 255.255.255.0" ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" ifconfig on host say: inet 213.70.80.92 netmask 0xffffffff broadcast 213.70.80.92 inet 192.168.100.2=C2=A0 netmask 0xffffffff broadcast 192.168.100.2 ifconfig say to both ip's /32. Maby that's the reason for unavailable the apache. ifconfig iside the jail say the same. I'm a little bit confused. Am 23.03.2018 um 18:25 schrieb Marek Zarychta: > On Fri, Mar 23, 2018 at 04:01:30PM +0100, Joerg Surmann wrote: >> Hi all, >> >> I have a Problem to understund how to manage 2 Networks inside a Jail.= >> >> i have create a jail (using ezjail) with a alias IP. in rc.conf (on >> Host): >> >> ifconfig_vmx0=3D"inet 192.168.100.1 netmask 255.255.255.0" >> ifconfig_vmx0_alias0=3D"inet 192.168.100.2 netmask 255.255.255.0"=C2=A0= <- >> this is the jail ip >> >> Inside the jail running apachhe24. >> >> Now i add a new NIC to the System. in rc.conf (on Host): >> ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >> >> in /usr/local/etc/ezjail/myjail.conf: i add the new ip export >> jail_myjail_ip=3D"192.168.100.2,213.70.80.92" >> >> Restart the jail and ifconfig looks fine. vmx0 -> inet 192.168.100.2 >> em0=C2=A0 -> inet 213.70.80.92 >> >> Apache Listen on all NIC's () But i can see my >> Website only via 192.168.100.2 from intern Network. >> >> The Host is behind a Firewall. The IP=C2=A0 213.70.80.92 is enabled f= or >> incomming Traffic. >> >> When i give the Hostname in a Browser i become "connection Timeout". >> >> What is to do that the Host is accessable from Inet? >> > Hi Joerg,=20 > > I guess your host has default gw reachable via vmx0 and second interfac= e > em0 is connected and was reachable at least from firewall protecting > address 213.70.80.92? If it is true then you should add:=20 > > to /usr/local/etc/ezjail/myjail.conf=20 > export jail_myjail_ip=3D"lo1|127.0.1.1,vmx0|192.168.100.2,em0|213.70.80= =2E92" > export jail_myjail_fib=3D"1" > > to /etc/rc.conf > static_routes=3D"net_jails" > route_net_jails=3D"default 213.70.80.x -fib 1" > > to /boot/loader.conf > net.fibs=3D"2" > > Eventually take a look at setfib(1) and also consider migrating em > adapter to second vmx which shuld be faster and more flexible. > > IMHO this questions should be asked rather on freebsd-net list than > here. --XLdbuKE7TcH5190G2OxcWomUP464lUdtA-- --QabuUyHbzzRJWlhPrBEMbgUkV38HLlAPv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIzBAEBCgAdFiEEKgIE1afOeXZNzpBEGHz25TAa4ssFAlq1UscACgkQGHz25TAa 4stliw//U8XD9nn0MOnrgTW3nROyAaYIcLn1S8VMMT9iTMILIh8nM4RDpU3wMZ9l TjjFQihgihJzOI2GLGBIpyCV3iwaG1PWjkTRT9ed+weI+8drhFx1IXlbFtWKxIt3 8dYYfH/30RRrudzJSdB+bOgwkPvRM+AXpB4ydIzZPvtG/WKRZqG7J/H4l31udLfh i2oBqjV6jeaq/z8LU0gJ8H0BlZUVnEzRtUojKXmGeyOsffKB5DAU89iCGl5rikuJ /z8ob6o0+OiRkpoDq0wKIwqw4ZWLXNINMn7bYbhtXay3p+ItVagPBO5ih2bX9ZLi Xdv3YK7xx+qmg7qzWLUBMWyivF5MeYKn7PNT+vVpNwNm9A/ANjQ9uuR6sL7XjVM5 a9xC2vpRf/DCHaExUBbRwD1KbkbUtSrkiEriOqJVXUv5D9HHRpSQ2IplV1WevbQg 8cA4+0PfV2+pbDf1sMzKIxYLrZEdRlS0IKu1qpsq5YJvEjV11+NDYgdFfN6F4xbK DnXlxL39sFhTX1d0J4q3iBTt9UZaP9fsx1INDVqwa/WDOblutFcgzdcINi/cWOOW z0iEsb+MPCGHh1Iu6/xLgWw9QqldRdQYOuPay2R3oxzCQMiLDicQRBAGf3HVuG2o fm22wRoEMABnX6+NfznofRY5wPfxGCnWYpSK0KPa0NHCVq5apvY= =yYf7 -----END PGP SIGNATURE----- --QabuUyHbzzRJWlhPrBEMbgUkV38HLlAPv-- From owner-freebsd-stable@freebsd.org Fri Mar 23 20:23:32 2018 Return-Path: Delivered-To: freebsd-stable@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 7D955F6B815; Fri, 23 Mar 2018 20:23:32 +0000 (UTC) (envelope-from chris@tellme3times.com) Received: from mail.tellme3times.com (j90z.x.rootbsd.net [208.86.227.78]) (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 1F5BB8A7DD; Fri, 23 Mar 2018 20:23:31 +0000 (UTC) (envelope-from chris@tellme3times.com) Received: from gatekeeper.tellme3times.com (modemcable074.25-70-69.static.videotron.ca [69.70.25.74]) by mail.tellme3times.com (Postfix) with ESMTP id 947C394104B; Fri, 23 Mar 2018 16:15:17 -0400 (EDT) Received: from [192.168.7.61] (unknown [192.168.7.61]) by gatekeeper.tellme3times.com (Postfix) with ESMTP id 35E8D3727C; Fri, 23 Mar 2018 16:15:17 -0400 (EDT) From: Chris Kiakas Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_4E2C9BD6-B7A9-4D60-96EC-D0A8852A43FC"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Two NIC's inside a Jail Date: Fri, 23 Mar 2018 16:14:27 -0400 In-Reply-To: Cc: Marek Zarychta , freebsd-stable@freebsd.org, freebsd-current@freebsd.org To: joerg_surmann References: <785ce70f-3f2d-3422-0e95-146b05f7f768@elektropost.org> <20180323172504.GA55971@plan-b.pwste.edu.pl> X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 20:23:32 -0000 --Apple-Mail=_4E2C9BD6-B7A9-4D60-96EC-D0A8852A43FC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, Sorry that I am coming to the conversation a little late. I have several = systems Which run with multiple IP connections where the jail responds = to multiple IPs I set /etc/rc.conf to just control the ips of the host. as an example; ifconfig_igb1=3D"inet AAA.AAA.AAA.1 netmask 255.255.255.0" defaultrouter=3D=E2=80=9CAAA.AAA.AAA.1=E2=80=9D ifconfig_igb2=3D"inet 192.168.10.1 netmask 255.255.255.0" ifconfig_igb4=3D"UP" ifconfig_igb5=3D"UP" ifconfig_igb6=3D"UP" ifconfig_igb7=3D"UP" cloned_interfaces=3D"lagg0" ifconfig_lagg0=3D"laggproto lacp laggport igb4 laggport igb5 laggport = igb6 laggport igb7 192.168.12.14/24=E2=80=9D The jail is then set with it=E2=80=99s jail.conf file as such; jailname { host.hostname =3D =E2=80=9Cjailname"; ip4.addr =3D =E2=80=9Cigb1|AAA.AAA.AAA.2/24=E2=80=9D; ip4.addr +=3D =E2=80=9Cigb2|192.168.10.21/24=E2=80=9D; ip4.addr +=3D "lagg0|192.168.12.32/24"; path =3D "/usr/jail/jailname"; exec.start =3D "/bin/sh /etc/rc"; exec.stop =3D "/bin/sh /etc/rc.shutdown"; exec.consolelog =3D "/var/log/jail.jailname.console.log"; mount.devfs; } My interfaces are igb# your's are em0 Apache is set to listen to; Listen :80 If the Apache setup is not complex it should just work on all IP. If you = are running vhosts you will need to specify ServerName and/or = ServerAliases in apache. If the jail requires a different gateway than the defaultrouter then you = will need to setup fibs. Chris > On Mar 23, 2018, at 3:17 PM, joerg_surmann = wrote: >=20 > Hi, >=20 > thanks for yor help. >=20 > I can't find a solution. >=20 > But i have find a starnge ip config. >=20 > in rc.conf on Host(not jail) >=20 > ifconfig_vmx0_alias1=3D"inet 192.168.100.2 netmask 255.255.255.0" > ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >=20 > ifconfig on host say: > inet 213.70.80.92 netmask 0xffffffff broadcast 213.70.80.92 > inet 192.168.100.2 netmask 0xffffffff broadcast 192.168.100.2 >=20 > ifconfig say to both ip's /32. >=20 > Maby that's the reason for unavailable the apache. >=20 > ifconfig iside the jail say the same. >=20 > I'm a little bit confused. >=20 >=20 >=20 > Am 23.03.2018 um 18:25 schrieb Marek Zarychta: >> On Fri, Mar 23, 2018 at 04:01:30PM +0100, Joerg Surmann wrote: >>> Hi all, >>>=20 >>> I have a Problem to understund how to manage 2 Networks inside a = Jail. >>>=20 >>> i have create a jail (using ezjail) with a alias IP. in rc.conf (on >>> Host): >>>=20 >>> ifconfig_vmx0=3D"inet 192.168.100.1 netmask 255.255.255.0" >>> ifconfig_vmx0_alias0=3D"inet 192.168.100.2 netmask 255.255.255.0" = <- >>> this is the jail ip >>>=20 >>> Inside the jail running apachhe24. >>>=20 >>> Now i add a new NIC to the System. in rc.conf (on Host): >>> ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >>>=20 >>> in /usr/local/etc/ezjail/myjail.conf: i add the new ip export >>> jail_myjail_ip=3D"192.168.100.2,213.70.80.92" >>>=20 >>> Restart the jail and ifconfig looks fine. vmx0 -> inet = 192.168.100.2 >>> em0 -> inet 213.70.80.92 >>>=20 >>> Apache Listen on all NIC's () But i can see my >>> Website only via 192.168.100.2 from intern Network. >>>=20 >>> The Host is behind a Firewall. The IP 213.70.80.92 is enabled for >>> incomming Traffic. >>>=20 >>> When i give the Hostname in a Browser i become "connection Timeout". >>>=20 >>> What is to do that the Host is accessable from Inet? >>>=20 >> Hi Joerg, >>=20 >> I guess your host has default gw reachable via vmx0 and second = interface >> em0 is connected and was reachable at least from firewall protecting >> address 213.70.80.92? If it is true then you should add: >>=20 >> to /usr/local/etc/ezjail/myjail.conf >> export = jail_myjail_ip=3D"lo1|127.0.1.1,vmx0|192.168.100.2,em0|213.70.80.92" >> export jail_myjail_fib=3D"1" >>=20 >> to /etc/rc.conf >> static_routes=3D"net_jails" >> route_net_jails=3D"default 213.70.80.x -fib 1" >>=20 >> to /boot/loader.conf >> net.fibs=3D"2" >>=20 >> Eventually take a look at setfib(1) and also consider migrating em >> adapter to second vmx which shuld be faster and more flexible. >>=20 >> IMHO this questions should be asked rather on freebsd-net list than >> here. >=20 >=20 --Apple-Mail=_4E2C9BD6-B7A9-4D60-96EC-D0A8852A43FC Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEi+l+WvjUMve3CBUQ0McJ9XNZ9LEFAlq1YCMACgkQ0McJ9XNZ 9LEplxAAiSrcOP0KVLb1TFuR3NximPUObOk7OPk0ueX4ZW6RaLOMZ/7D1m/tnIl/ TUjLlflzyUeAtXHVj9rYbqXMwpL6ftCtd6U/YAz6kqX5nq3k6vkqE2NjJcFd8Jh0 V0svjA4xMOVai3+M2eBf8CWnYFQT62ekbqK1wTon5vL8us/4VHXIjY81vGugMI6J f3m+94xVE9HHTX79Nrc39cQ/4IAcskdCjF5SgWFSc5GBo/2yh2Sgl3NYUsysPPdV M+/oUqg8ZDKO2PGrHUr02+oPnoRdFoh/1DpT0i0jNjgKlqDiysYy2qI9n+6u9TOL T5OmMmaAoPaVg+0N+2JaH8jvPYv8PCZPcaIhl4YaZlm10liLEXN23riDxv3Wgf6a A52nMJZOjqt+2QLs4eS5i5xhZqLay6SiqRuG9vcvc46WU5x9UyoxjixwYVP0wfyc WmlQEHTsrG6D8is2AphPEYfyc6c+f0ksSFYU7x3VvzoQiAU3QdgOW7DUbAbzpFC/ Du3VTLcy6skYl1qSI02b9V3olP6Ly3GtNVGVfZMEUc/wlmE8IyN4i5JZHj++tY6q amTRisEZQmfLJyyRrtxZKyCPOjmMRD4f9o/K2UUd+F1wmZqp0lklOlQFAu8hDch6 ew6LZgLIILE/MOFsG6b7swq+42AzFVsC9UzZt9su/b9VirbHZ6I= =vV0a -----END PGP SIGNATURE----- --Apple-Mail=_4E2C9BD6-B7A9-4D60-96EC-D0A8852A43FC-- From owner-freebsd-stable@freebsd.org Sat Mar 24 09:19:22 2018 Return-Path: Delivered-To: freebsd-stable@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 3C495F58E61; Sat, 24 Mar 2018 09:19:22 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (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 C775082384; Sat, 24 Mar 2018 09:19:18 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1ezf3i-0005le-In; Sat, 24 Mar 2018 10:01:54 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-ports@freebsd.org, "freebsd-stable@freebsd.org" Date: Sat, 24 Mar 2018 10:02:04 +0100 Subject: portsmon.freebsd.org via freshports? Cc: mcl@freebsd.org, "dan@langille.org" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: a07cf4f22b7e0347d98fbeb4081a69be X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 09:19:22 -0000 Hello, Is portsmon ever coming back? http://portsmon.freebsd.org/portoverview.py?category=net&portname=samba46 -> "The latest Python updated failed. Repairs are in progress 20171025 -- mcl" It is referenced from the freshports.org site. https://www.freshports.org/net/samba46/ I found it a useful tool to see why packages are not available for some version. Regards and thanks for all the work for these services, Ronald. From owner-freebsd-stable@freebsd.org Sat Mar 24 09:50:14 2018 Return-Path: Delivered-To: freebsd-stable@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 E4B22F5BA1F for ; Sat, 24 Mar 2018 09:50:13 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (unknown [IPv6:2001:678:618::40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "plan-b.pwste.edu.pl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 610A0839E2 for ; Sat, 24 Mar 2018 09:50:12 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (zarychtam@localhost [127.0.0.1]) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPS id w2O9o9a3080372 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 24 Mar 2018 10:50:09 +0100 (CET) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: (from zarychtam@localhost) by plan-b.pwste.edu.pl (8.15.2/8.15.2/Submit) id w2O9o9Bm080371 for freebsd-stable@freebsd.org; Sat, 24 Mar 2018 10:50:09 +0100 (CET) (envelope-from zarychtam) Resent-From: Marek Zarychta Resent-Date: Sat, 24 Mar 2018 10:50:09 +0100 Resent-Message-ID: <20180324095009.GA80236@plan-b.pwste.edu.pl> Resent-To: freebsd-stable@freebsd.org Date: Fri, 23 Mar 2018 21:02:14 +0100 From: Marek Zarychta To: joerg_surmann Cc: freebsd-stable@freebsd.net Subject: Re: Two NIC's inside a Jail Message-ID: <20180323200214.GA76829@plan-b.pwste.edu.pl> References: <785ce70f-3f2d-3422-0e95-146b05f7f768@elektropost.org> <20180323172504.GA55971@plan-b.pwste.edu.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 09:50:14 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 23, 2018 at 08:17:27PM +0100, joerg_surmann wrote: > Hi, >=20 > thanks for yor help. >=20 > I can't find a solution. >=20 > But i have find a starnge ip config. >=20 > in rc.conf on Host(not jail) >=20 > ifconfig_vmx0_alias1=3D"inet 192.168.100.2=C2=A0 netmask 255.255.255.0" > ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >=20 > ifconfig on host say: > inet 213.70.80.92 netmask 0xffffffff broadcast 213.70.80.92 > inet 192.168.100.2=C2=A0 netmask 0xffffffff broadcast 192.168.100.2 >=20 > ifconfig say to both ip's /32. >=20 > Maby that's the reason for unavailable the apache. >=20 > ifconfig iside the jail say the same. >=20 > I'm a little bit confused. >=20 Please show also the output of: netstat -rn During startup, ezjail is adding one more IP address with /32 mask for each interface deployed to jail. Consider addressing interfaces on host these in these way: in /etc/rc.conf ifconfig_vmx0_alias1=3D"inet 192.168.100.3 netmask 255.255.255.0" ifconfig_em0=3D"inet 213.70.80.93 netmask 255.255.255.0" then in /usr/local/etc/ezjail/myjail.conf=20 export jail_myjail_ip=3D"vmx0|192.168.100.2,em0|213.70.80.92" If you don't want to waste one more public IP for the host, try to setup jails from jail.conf(5) instead of ezjail management. You can also give a try to more sophisticated setup with vnet(9) jails where multiple fibs for the host will not be required. Best regards, --=20 Marek Zarychta --jI8keyz6grp/JLjh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlq1XUQACgkQdZ/s//1S jSxhxwf/Xyr8MX7YXNlbhffjRutJXZcrg0oQTQzU8+n0RgQ3PWZHcOxFM4mGJEnH aqBtH6b+wUgC9oCIh6oXizW0NC6ACGEVFmIGeiLvMjrPF4vEcZ1hNMXCtMq6L2bE 75Iyt0h+kTQSOC+E0drmE/UhLx/k+6o4UaTYVKkjaA8zWVStVpLC4M83uSXj1Y27 ZuT2E3npP69Ncr/jEFWkIpiALC3e65j1ddm4hDTW/mpMgpL8Byj7GjZXF6TbuJWs e6qLCVRcBivsHqJ6F/SLHgPwJQvwf6jQq0CtcSJnrPryyAoWLMCzQfqp0s47QuTx sfOG/HwdJ62a7am/Z0Rsj6IXfd6S/g== =vjML -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- From owner-freebsd-stable@freebsd.org Sat Mar 24 17:39:57 2018 Return-Path: Delivered-To: freebsd-stable@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 D65F5F5EB01; Sat, 24 Mar 2018 17:39:57 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 78198767C3; Sat, 24 Mar 2018 17:39:57 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 2EB5813C7; Sat, 24 Mar 2018 12:39:50 -0500 (CDT) Date: Sat, 24 Mar 2018 12:39:49 -0500 From: Mark Linimon To: Ronald Klop Cc: freebsd-ports@freebsd.org, "freebsd-stable@freebsd.org" , linimon@freebsd.org, "dan@langille.org" Subject: Re: portsmon.freebsd.org via freshports? Message-ID: <20180324173948.GA23064@lonesome.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 17:39:58 -0000 > Is portsmon ever coming back? Sometime in Q2, yes. mcl From owner-freebsd-stable@freebsd.org Sat Mar 24 19:07:35 2018 Return-Path: Delivered-To: freebsd-stable@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 31385F66C0F; Sat, 24 Mar 2018 19:07:35 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 D46F17A752; Sat, 24 Mar 2018 19:07:34 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id DF46020C1F; Sat, 24 Mar 2018 15:07:32 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Sat, 24 Mar 2018 15:07:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=Zm3cVfpvQABY4+5um+dLiQWNsKWbfuZeEUAGB90mTrs=; b=T0wSgeEV o8VlgHlFdyLf2LzmgTs+D4BPO6mXL6TKx7+URlJXZE/TMRdI3sl6GSZ3G62lwfvR 2sXX/gr25Gj/xnZ5ondGfcduew4+eIW5AkDL7brGbq8pXA4ywif8Ov6slAksZjVz hoa1rOH8dvizOVod2lMBa3fjZqk7NcwYn2hjlv/7e4AHxASNnbqjl/VQvBwoJnVE jKL7t2Kqzac+edtkWFkWiQIeL3VMXq12kPID49pwObv3InKxWlfqigoWebtJEd2B 8YyU5vPnTfe6wNrPfbYI/0M52rarkfGGMRCelxXWq0eUFywHlHXRXbu9UXWvRFT2 F+6+o6Eg8sLxEQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=Zm3cVfpvQABY4+5um+dLiQWNsKWbf uZeEUAGB90mTrs=; b=GCPaDGCnr+E7mSYeCtH1Jkbeop5hP43wDQcVVIVjsp344 lqbpA+SaQqltNFRapXmgYvr50Nfqw1nCwS8rFOUKpTFjBOTvFoN1Y8ELcwSc8GuC 4MC7aJ9SiILc7BCVp2BIc6dU4VFw/T6dJXLzAspv+auLOslsUnIgknbsWiv/A7N7 U7sqQNpWc3wTMuzjNVqVCyVgEInixxth+1uwpY6QJN0hrsqd4Jq6rxhbhQjOGOfr wXfTuxJUkh8vHyYFpcgUGRcZ1/eiX3Orb6C6zvq7E+tMBoTYBQpiatv2IWfZesSJ ldymNUMNPqeIe0n7/eqCYHxGO2W8RBhnGywRKaqqQ== X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 45ADB7E13F; Sat, 24 Mar 2018 15:07:32 -0400 (EDT) To: freebsd-ports@freebsd.org Cc: FreeBSD Stable From: tech-lists Subject: libreoffice fails to build Message-ID: Date: Sat, 24 Mar 2018 19:07:31 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 19:07:35 -0000 Hi, Building libreoffice (libreoffice-en_GB) complains about illegal instruction and dumps core. Full script output is at https://www.zyxst.net/errors/libreofficebuildfail.txt last few lines of make MAKE_JOBS_UNSAFE=yes -DBATCH ################################################################## [HIX] scalc/en-US S=/usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1 && I=$S/instdir && W=$S/workdir && ( rm -rf $W/HelpTarget/scalc/en-US/scalc.idxl && LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}"$I/program:$I/program" $W/LinkTarget/Executable/HelpIndexer -dir $W/HelpTarget/scalc/en-US -lang en-US -mod scalc && touch $W/HelpIndexTarget/scalc/en-US.done ) || ( rm -rf scalc.* ; false ) Illegal instruction (core dumped) gmake[3]: *** [/usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1/solenv/gbuild/HelpTarget.mk:452: /usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1/workdir/HelpIndexTarget/sbasic/en-US.done] Error 1 gmake[3]: *** Waiting for unfinished jobs.... Illegal instruction (core dumped) gmake[3]: *** [/usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1/solenv/gbuild/HelpTarget.mk:452: /usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1/workdir/HelpIndexTarget/scalc/en-US.done] Error 1 gmake[3]: Leaving directory '/usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1' gmake[2]: *** [Makefile:268: build] Error 2 gmake[2]: Leaving directory '/usr/ports/editors/libreoffice/work/libreoffice-6.0.2.1' *** Error code 1 Stop. make[1]: stopped in /usr/ports/editors/libreoffice *** Error code 1 Stop. make: stopped in /usr/ports/editors/libreoffice-en_GB ######################################################## context: no /etc/make.conf root@eggs:/root# uname -KU 1101512 1101512 root@eggs:/root# system: 11.1-STABLE #0 r331421 amd64 ports: root@eggs:/root# svnlite info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: https://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 465452 Node Kind: directory Schedule: normal Last Changed Author: gerald Last Changed Rev: 465452 Last Changed Date: 2018-03-24 14:15:56 +0000 (Sat, 24 Mar 2018) shall I file a bug report? -- J.