From owner-freebsd-arm@FreeBSD.ORG Mon Feb 11 06:17:09 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 01FA343C for ; Mon, 11 Feb 2013 06:17:08 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id CB9FD87E for ; Mon, 11 Feb 2013 06:17:08 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r1B6H8hR010849; Mon, 11 Feb 2013 06:17:08 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id 4ammtaytnzfe5bpr453m5jqfmi; Mon, 11 Feb 2013 06:17:07 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: New BeagleBone errors Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: <20130210231709.26f122dc@ivory.local> Date: Sun, 10 Feb 2013 22:17:07 -0800 Content-Transfer-Encoding: 7bit Message-Id: References: <20130210231709.26f122dc@ivory.local> To: Brett Wynkoop X-Mailer: Apple Mail (2.1283) Cc: freebsd-arm@freebsd.org 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: Mon, 11 Feb 2013 06:17:09 -0000 On Feb 10, 2013, at 8:17 PM, Brett Wynkoop wrote: > Greeting- > > I am in the process of transferring man pages from the Bone to the Pi > and I got this on the bone console: > > a ./man1/ls.1.gzcpsw0: watchdog timeout > interrupt storm detected on "intr42:"; throttling interrupt source > > I am transferring by shoving a tar down nc....so > > tar cpvf - . | nc Pi 8080 Can you tell me the SVN revision of your BeagleBone kernel? Also, the output of "sysctl dev.cpsw" might hold useful clues whenever this happens. Interrupt 42 is the RX interrupt for the CPSW ethernet; it sounds like the driver is no longer correctly acknowledging RX interrupts after the watchdog reset. Tim