From owner-freebsd-stable@FreeBSD.ORG Wed Oct 8 00:34:33 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DAB5DEB7; Wed, 8 Oct 2014 00:34:32 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (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 B07A1965; Wed, 8 Oct 2014 00:34:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=oKGaD4bnX6AWf2IeWTMIIbtUu9CmWuPHCo2V532FS0w=; b=WeGbWp08JcbGTZfEN5bnN5dgcM/FQkLz3dsT4rzLTgg61SHy4126RIPo5q4gLQREiDMV0gizgssAGIzalWntuJKt/RdXxihK2CYmVKAXM6B1o54jdNCl/Suz0PlaZoF1ZzfUyejnl0wBWJuP57tVXIEIYX0te14Y+/0PmEuB/FU=; Received: from [182.9.144.112] (port=47866 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1XbfD4-003JJO-K1; Tue, 07 Oct 2014 18:34:31 -0600 Date: Wed, 8 Oct 2014 08:34:24 +0800 From: Erich Dollansky To: Scot Hetzel Subject: Re: FreeBSD 10.1-RC1 Now Available --- lagg disables network inside jails Message-ID: <20141008083424.354b9d7c@X220.alogt.com> In-Reply-To: References: <20141005013247.GH1171@hub.FreeBSD.org> <20141005203401.440afc31@X220.alogt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: Glen Barber , freebsd-jail@freebsd.org, FreeBSD Release Engineering Team , FreeBSD Stable , freebsd-net@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Oct 2014 00:34:33 -0000 Hi, jails work now with lagg0 again on my machine. It seems to me that it was a specific problem of this one machine. I installed the following revisions: 272555 starting point which failed 272400 failed 272000 works 272200 works 272300 works 272400 test again and it works 272400 installing world inside the jail and it works I then went to 272672 and it also works. It might was the sequence, it might was a configuration error on my side, all I know is that it works again. I also cross-compiled a kernel for the Raspberry which also works when using the latest firmware as YAMAMOTO Shigeru suggested. Erich On Sun, 5 Oct 2014 11:38:47 -0500 Scot Hetzel wrote: > On Sun, Oct 5, 2014 at 7:34 AM, Erich Dollansky > wrote: > > Hi, > > > > On Sat, 4 Oct 2014 21:32:47 -0400 > > Glen Barber wrote: > > > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA256 > >> > >> The first RC build of the 10.1-RELEASE release cycle is now > >> available > > > > I installed this shortly after your e-mail came. The result was the > > same as with BETA3. If you remember, I have had the problem that the > > network inside jails stopped working after I installed BETA3. The > > upgrade to RC1 did not change anything. > > > > I took now the time to investigate a bit. The result is simple. All > > works as expected until lagg becomes enabled. > > > > If I remember right, BETA1 was my last working version. > > > > I have an em and an iwn interface in the machine. I can use both of > > them without any problems. > > > > As I can reproduce this problem 100%, it might be a good idea if I > > help you to find the source of the problem. My problem would be: > > how. > > > > If somebody could tell me where to start looking for the error, we > > might find it soon. > > > You'll need to identify where in the src caused the issue for you. To > do this, you will need to identify where it was working (BETA1?). > You would then have to step thru the sources until you find the point > where it breaks. > > The easiest way would be to take the svn revision that is half way > between BETA1 and BETA3, compile and install it and see if it works. > You keep halving the result until you identify the commit that broke > it. > > Once the offending commit is identified, email the list. >