From owner-freebsd-mips@FreeBSD.ORG Thu May 23 05:55:45 2013 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 41302ED0; Thu, 23 May 2013 05:55:45 +0000 (UTC) (envelope-from freebsd-mips@dino.sk) Received: from mailhost.netlab.sk (mailhost.netlab.sk [84.245.65.10]) by mx1.freebsd.org (Postfix) with ESMTP id 51C6537F; Thu, 23 May 2013 05:55:44 +0000 (UTC) Received: from zeta.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: LOGIN milan, TLS: TLSv1/SSLv3,128bits,AES128-SHA) by mailhost.netlab.sk with ESMTPSA; Thu, 23 May 2013 07:55:50 +0200 id 004EB835.519DAF66.000115CA Date: Thu, 23 May 2013 07:55:37 +0200 From: Milan Obuch To: Joe Holden Subject: Re: Ubiquiti EdgeRouter Lite works multi-user with -CURRENT. Message-ID: <20130523075537.37e4bcba@zeta.dino.sk> In-Reply-To: <519DA801.2090205@rewt.org.uk> References: <20130516111059.38543d57@wind.dino.sk> <20130516131642.adfae355aa3bf7767e9b56e5@ddteam.net> <20130516124248.33ae4e05@wind.dino.sk> <51952112.9010607@rewt.org.uk> <20130517192206.5db0533f@zeta.dino.sk> <51966CB6.2040701@rewt.org.uk> <20130520110659.1d1d2165@zeta.dino.sk> <20130520164001.5f7d99b8@zeta.dino.sk> <20130520172508.087daf7b@zeta.dino.sk> <20130523070225.4d9a3a59@zeta.dino.sk> <519DA801.2090205@rewt.org.uk> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.17; amd64-portbld-freebsd9.1) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEX+/v7++v6YOTrq8PCcuIX989UvOSj++v0BNCbpAAAAB3RJTUUHsQwfFzs7RBhzUQAAAhJJREFUOI1dU8GOqzAMNKIoV1bvwD1i0ysqrHplIdBrVSX7ATSbd03VVvn9tQNtQy0hjAdn7LED4AAcPtWm9RV+MPSfxhBLx9ajd6X/ngB6/mTwnRSZua7i7Ca+0ctZKo4Qmz+JY13X6I3nFZBxIYW1PbgfQ5RP8g0XlltEWGf3cV03joYpRnFbvYDKbXjZlXyyhEZA4lI+cN3NaVXE4VKjSwTExO10eTEkkJVqIAD5z0nUBQJluQDRSQjcrBiHAJxZlAH5CUMBMC7OcJ4LMQNnxhZ1HYPscMc6J4UlWRMNwzOpCcAHKSICd1EDn83abdREIbXsHkD1OinP1aCUCOEVRaa1lMcvywUWdYgk13JQUpYNKmvXQ8Kw5ML9YI5h8SakctBc7E/IYuLhYd/zZIk+1gM1vNweQBvHE0j+oYah3sMqAytQYlZk6+ANaaawJdu3OFzYGMZ3iGpa3qMlq9ZH0VZTgrCtw/ngdYkEIIpSbP1bWQAdFdX9vocBdkH2qVjVmuMu3gI5rjs814EUdrCZgWlPaxZZ3RiLFUtr+ud0PXwp2dnQSNXgePt6AZpBj6UMJ7VQkzN4utVeaSW1Dhn/kblGrKeMvNGnzwX4zuEDarYz1KdPtR60Gul0Gued+515SJXhCsl+Tx/3kY/UDvicPll9mfu50t3tvQ/thZpJYgeuwdSKNJ6tCD98MCgoxLDaPxbwqqwPWaWiAAAAAElFTkSuQmCC X-Face: ak5rwz4-aUa>hPFZlcg,bXxn.(TN}e9DGFrKU\.i_'B[&5=pAd9o"j)5VSUYW:BRQG#^42Ev$Il|; Ztn=,C X-Operating-System: FreeBSD/amd64 8.2-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Aleksandr Rybalko , freebsd-mips@freebsd.org X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 05:55:45 -0000 On Thu, 23 May 2013 06:24:17 +0100, Joe Holden wrote: > Milan Obuch wrote: > > On Mon, 20 May 2013 08:27:40 -0700, Juli Mallett > > wrote: > > > >> On Mon, May 20, 2013 at 8:25 AM, Milan Obuch > >> wrote: > >>> Yes, output is from 'gpioctl -f /dev/gpioc0 -lv' command > >>> execution. Actually, I wrote all 16 pins (0 to 15) in > >>> sys/mips/cavium/octeon_gpio.c so I can see quickly which GPIO pin > >>> is connected to reset switch. Pin 11 changed when pressing the > >>> switch. > >> Could you try commenting out everything but pin 11 in octeon_gpio.c > >> and rebuilding? I'm wondering if one of those pins may have been > >> in-use to talk to some Ethernet hardware or something like that, > >> and that its operation was disrupted by the GPIO driver. > > > > Hi, > > > > it took me some time to build new kernel, howerver, even with only > > pin 11 defined in octeon_gpio.c it behaves the same way. If > > connected to gigabit card it works, connecting to 100 megabit > > switch meens no network activity. Later today I will test it > > against other device if something changes. > > > > Regards, > > Milan > > FWIW I upgraded one of them to latest snapshot and I'm seeing the > same... however: > > I checked an older build on a hunch and it's no the link speed that > seems to be the problem, if I change the switch port to only > advertise 100M, the link comes up but nothing makes it onto the wire > or is received by the kernel. If I reboot with the port still > advertising 100M all is well when it comes back up, and vice versa > with 1000M so it seems to be a problem with the link speed changing > or going up/down... I'd normally expect to see octe0 up/down logged > but that doesn't happen, even thuogh ifconfig shows the correct speed > Yes, you are right - now I checked with octe0 connected to 100 megabit switch and it initializes correctly when booting. When I plug gigabit card now instead, it does not work - no communication on interface. Even if I do ifconfig octe down/ifconfig octe up, it does not transmit/receive packets. So I think problem is phy link speed change on live system. Reboot in this case is a big hackish 'workaround' for now - good for tests, not yet fully for real work (but if you know there will be no link speed change it is OK). Regards, Milan