Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Oct 2017 22:02:13 -0400
From:      Stephen Hurd <shurd@sasktel.net>
To:        Eric van Gyzen <vangyzen@FreeBSD.org>, shurd@FreeBSD.org, sbruno@FreeBSD.org, freebsd-net@freebsd.org
Subject:   Re: LOR in iflib_timer
Message-ID:  <a46362a5-62f7-17af-a653-10cfa9ef4558@sasktel.net>
In-Reply-To: <32cdf984-fa30-331c-f7b0-2bec1f13a6cf@FreeBSD.org>
References:  <32cdf984-fa30-331c-f7b0-2bec1f13a6cf@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Eric van Gyzen wrote:
> 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

I would guess it to be one of the biggest ones.  Review here: 
https://reviews.freebsd.org/D12101



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a46362a5-62f7-17af-a653-10cfa9ef4558>