From owner-freebsd-arm@FreeBSD.ORG Tue Feb 26 17:10:03 2013 Return-Path: Delivered-To: freebsd-arm@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 338DE382 for ; Tue, 26 Feb 2013 17:10:03 +0000 (UTC) (envelope-from wynkoop@wynn.com) Received: from mail.wynn.com (wa3yre.wynn.com [199.89.147.3]) by mx1.freebsd.org (Postfix) with ESMTP id ECF9010BE for ; Tue, 26 Feb 2013 17:10:00 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by mail.wynn.com (8.14.3/8.12.6) with ESMTP id r1QH3ZH1094143 for ; Tue, 26 Feb 2013 12:03:35 -0500 (EST) (envelope-from wynkoop@wynn.com) Date: Tue, 26 Feb 2013 12:03:35 -0500 From: Brett Wynkoop To: freebsd-arm@freebsd.org Subject: Raspberry Pi Network Data Message-ID: <20130226120335.6928b473@ivory.wynn.com> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-apple-darwin10.8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2013 17:10:03 -0000 Greeting- For a couple of days I have been building software from ports. Mostly these builds are for things I just want to try on the Pi, or Bone, but the secondary reason is to put some pre-compiled packages up for those that do not have the patience to build them. While my Pi has been stable for a couple of weeks I have noted that sometimes it stops talking on the network. At those times if I get on the console and ifconfig down and back up the interface it starts talking on the net just fine again. Last night I believe I found a link between disk i/o and network non-responsiveness. During a period of high disk i/o to the USB connected flash drive I lost network. The console had messages about retrys to the disk and the console was slow to respond. It took me for ever to get logged in because the console kept dropping characters while I typed. I am using usb-keyboard and composite video for the console. When I got logged in I still had trouble typing ifconfig ue0 down ; ifconfig ue0 up, but once I did everything went back to normal. Keyboard response was fine, disk i/o no longer seemed to be reporting errors and of course the network came back on line. I went to sleep with zoneminder building. Now 6 hours later I find the machine in the same state. Since the disk, keyboard, and ethernet are all usb devices could we have a bug in the usb sub-system? As soon as the ifconfig ue0 down happens the console keyboard becomes properly responsive again. Could we have some sort of interrupt problem going on here? This is food for thought for you kernel hackers. If there is anything you want me to specifically try or do the next time I have this problem, probably in the next 24 hours, please let me know. Your fellow ARM hacker, -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 718-717-5435 April 19, 1775 An English attempt to confiscate guns from Americans triggered a successful revolution...... Dear Congress, that's a hint.