From owner-freebsd-current@freebsd.org Mon Jun 20 18:37:43 2016 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 2D004AC41E1; Mon, 20 Jun 2016 18:37:43 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 076A0172F; Mon, 20 Jun 2016 18:37:42 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from [172.27.2.35] (unknown [172.27.2.35]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 273C2541; Mon, 20 Jun 2016 14:31:40 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: BBB (cpsw(4)) seems to be broken in the latest 11-current From: Paul Mather In-Reply-To: Date: Mon, 20 Jun 2016 14:31:39 -0400 Cc: FreeBSD Current , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <71DC2BCB-C486-4772-AE32-CC0816B4E93F@gromit.dlib.vt.edu> References: To: Maxim Sobolev X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Mon, 20 Jun 2016 18:37:43 -0000 On Jun 18, 2016, at 2:50 AM, Maxim Sobolev wrote: > Updated my BBB to the latest -current, immediately got this while = trying to > make world over ssh console: >=20 > 06:02:17 CPSW watchdog cpswss0: watchdog timeout > cpswss0: Unable to cleanly shutdown transmitter >=20 > Interface seems to be locked after that, no traffic comes in or out. >=20 > This is: >=20 > FreeBSD 11.0-ALPHA3 #1 ba7edef(tps65217x)-dirty: Fri Jun 17 16:22:07 = PDT > 2016, svn revision 301898 >=20 > The previous version that was rock-solid was: >=20 > FreeBSD 11.0-CURRENT #0 9d390ee(tps65217x)-dirty: Mon Jul 6 19:31:30 = PDT > 2015, svn revision 284878 >=20 > I've been running buildworlds for literally days on that board, = because > it's how long it takes to build on that hardware. :) >=20 > I'll run it again and see if the issue re-appears. >=20 > If anyone seen this or if it's known issue please let me know. I have experienced this problem recently, too, after updating to = 11.0-ALPHA3. I get the watchdog timeout messages you give above when = trying to buildworld with /usr/src and /usr/obj mounted via NFS. My last successful build that did not have this problem is this one: = FreeBSD beaglebone 11.0-ALPHA2 FreeBSD 11.0-ALPHA2 #0 r301779: Mon Jun = 13 01:30:05 EDT 2016 = pmather@beaglebone:/usr/obj/usr/src/sys/BEAGLEBONE-NO_WITNESS arm The build where this started happening for me is this one: FreeBSD = 11.0-ALPHA3 #0 r301876: Wed Jun 15 14:23:28 EDT 2016 That's just two days apart. Maybe that might help track down the = potential revision that caused the problem. I've not been able to = buildworld via NFS since the problem began, so I've reverted back to the = r301779 kernel for now. Cheers, Paul.