From owner-freebsd-current@freebsd.org Tue Sep 15 11:09:21 2015 Return-Path: Delivered-To: freebsd-current@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 06AA4A03EA3 for ; Tue, 15 Sep 2015 11:09:21 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 C0FBF1BD9 for ; Tue, 15 Sep 2015 11:09:20 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (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 C4F181FE023; Tue, 15 Sep 2015 13:09:11 +0200 (CEST) Subject: Re: CURRENT: net/igb broken To: "O. Hartmann" , freebsd-current References: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> From: Hans Petter Selasky Message-ID: <55F7FCB5.5090809@selasky.org> Date: Tue, 15 Sep 2015 13:10:45 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Tue, 15 Sep 2015 11:09:21 -0000 On 09/15/15 12:56, O. Hartmann wrote: > Running CURRENT as of today (r287817), it seems that the network system of > CURRENT is corrupted. The machine in question is a Fujitsu server Primergy RX > 1330 with two Intel "igb" devices (igb0 and igb1). > > the network is now on both devices unreachable. With or without IPFW > (disabling, having first rule to allow everything in/out) doesn't matter. > Nothing get to or from that box on any device. > > With FreeBSD 11.0-CURRENT #4 r287592: Wed Sep 9 09:09:23 CEST 2015 amd64 I > had no problems. > > Any ideas? > > Thanks in advance, > > Oliver Just to rule out r287775, can you disable TSO? --HPS