From owner-freebsd-net@freebsd.org  Mon Oct 30 14:09:17 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id F126FE5DD1C
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon, 30 Oct 2017 14:09:17 +0000 (UTC)
 (envelope-from vangyzen@FreeBSD.org)
Received: from smtp.vangyzen.net (hotblack.vangyzen.net
 [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f])
 by mx1.freebsd.org (Postfix) with ESMTP id D24BD638BF;
 Mon, 30 Oct 2017 14:09:17 +0000 (UTC)
 (envelope-from vangyzen@FreeBSD.org)
Received: from blue.vangyzen.net (50-81-65-191.client.mchsi.com [50.81.65.191])
 by smtp.vangyzen.net (Postfix) with ESMTPSA id 2149E5646B;
 Mon, 30 Oct 2017 09:09:17 -0500 (CDT)
To: shurd@FreeBSD.org, sbruno@FreeBSD.org, freebsd-net@freebsd.org
From: Eric van Gyzen <vangyzen@FreeBSD.org>
Subject: LOR in iflib_timer
Message-ID: <32cdf984-fa30-331c-f7b0-2bec1f13a6cf@FreeBSD.org>
Date: Mon, 30 Oct 2017 09:09:13 -0500
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 14:09:18 -0000

Twice a day, my router hits an LOR in iflib_timer when it jumps to the 
"hung" label.  It's running r325049 (head 3 days ago).

lock order reversal:
  1st 0xfffffe0000f36068 igb1:tx(0):call (igb1:tx(0):call) @ 
/usr/src/sys/kern/kern_mutex.c:182
  2nd 0xfffff80003b0c150 igb1 (iflib ctx lock) @ 
/usr/src/sys/net/iflib.c:2139

This looks like it was fixed by the big rollup.  If it was fixed by a 
smallish commit, can that commit alone be merged to head?  If someone 
can point me to the commit, I'd be happy to test it.

Eric