From owner-freebsd-current@freebsd.org Fri Jul 6 13:26:23 2018 Return-Path: Delivered-To: freebsd-current@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 5B9901027100 for ; Fri, 6 Jul 2018 13:26:23 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 0428380E8D for ; Fri, 6 Jul 2018 13:26:22 +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 5BDA921D37; Fri, 6 Jul 2018 09:26:22 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 06 Jul 2018 09:26:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=WtpQXtxVaTW+XgAMKBx1/aPvqYqeC zPLG6pVY3iWSUI=; b=kpYelRXwJjM2v7fIUIqF3BE+x8uwTCIfA1LFNTBg/N0CN TS8IEvkzi0vsbhSqUeghVvgdMoIP/LFKZX8YW7MxwkNdDnKZ5g9eKbVxx15ZYiSH NxQaKkNkW6JXT0GGZP+P2sQUIDPjRDHhvj1aVH26qwIb6MT5SURabUM9q4OAQueG feOWM0cvVxF7rRe/GN+oULpGI5qnlpAvrOx4reqFjCGOlOXmuHiH+jWxZ5Ajzyyo N6bdkBcABoDUFC63YA+nKWWvxF5f/8UqWJSXXaSj3i15Ylyz+KKFDSzrWwqvoC3f xkftySvlMiBWWHsp8SjwRJIjONdGfQFqGfOfioAgQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=WtpQXt xVaTW+XgAMKBx1/aPvqYqeCzPLG6pVY3iWSUI=; b=EtwWltl4mz+X9J6C87OA0i ROVZYcqJqxB7/xAZjMsipo6r1KAyit4VCVheFM7bNvjFIJQPTw1fMmYAeDcn7jDw KieW4AysLElfZrfehhcA6b4o9dre71Mr8/J/1gxb3qCCzyB+OLaCWnDTkEpAmyuQ V5FXxC9v0gOmxG0bQK+N+5wwN+GmYxEZ6wo4CyGRcwtQVm9rEt9edRoOjU2oNeay k8qxgApQyOUYYQTbG5AktDgXaDuxIaYOztDTlAC8HvsXIBfR+tv1Q8nwbnb6fSla 2zo+rFU7eOhZBVE5C87yUt4bbPNGBrbe0o0fzsDO38zTniO1inS0AFHzgEkSu5eg == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 48C6C102B6; Fri, 6 Jul 2018 09:26:21 -0400 (EDT) Subject: Re: em0 link fail To: Michael Butler , freebsd-current References: <739ef71a-f29f-68ea-955a-fb53c57960a6@protected-networks.net> From: tech-lists Organization: none Message-ID: <10e5354f-44e1-ba6f-4f50-552b2cec5680@zyxst.net> Date: Fri, 6 Jul 2018 14:26:19 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 In-Reply-To: <739ef71a-f29f-68ea-955a-fb53c57960a6@protected-networks.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2018 13:26:23 -0000 On 03/07/2018 18:47, Michael Butler wrote: > On June 1st, I was able to do my monthly laptop ZFS snap-shot/back-up > (using "zfs snapshot -r zroot@backup; zfs send -R >nfs-filesys"). Now I > can't without the em0 interface stalling :-( > > On a guess, I tried reverting SVN r335303 but that didn't help. > > em0: port 0xf080-0xf09f mem > 0xf7e00000-0xf7e1ffff,0xf7e39000-0xf7e39fff irq 20 at device 25.0 on pci0 > em0: attach_pre capping queues at 1 > em0: using 1024 tx descriptors and 1024 rx descriptors > em0: msix_init qsets capped at 1 > em0: PCIY_MSIX capability not found; or rid 0 == 0. > em0: Using an MSI interrupt > em0: allocated for 1 tx_queues > em0: allocated for 1 rx_queues > em0: Ethernet address: f0:1f:af:66:95:7e > em0: netmap queues/slots: TX 1/1024, RX 1/1024 > em0: link state changed to UP > > [ initiate "zfs send" ] > > em0: TX(0) desc avail = 41, pidx = 172 > em0: link state changed to DOWN > em0: TX(0) desc avail = 1024, pidx = 0 > em0: TX(0) desc avail = 1024, pidx = 0 > > .. ad nauseum .. > > "ifconfig em0 down; ifconfig em0 up" doesn't help. > > Any hints? Hi, I'm not seeing any problems using em0/saturating upstream using 12.0-CURRENT #0 r335979 -- J.