From owner-freebsd-arm@FreeBSD.ORG Tue Aug 20 20:21: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]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id ADA75B7B for ; Tue, 20 Aug 2013 20:21:03 +0000 (UTC) (envelope-from mailinglists@martinlaabs.de) Received: from relay03.alfahosting-server.de (relay03.alfahosting-server.de [109.237.142.239]) by mx1.freebsd.org (Postfix) with ESMTP id 6BAAA29EA for ; Tue, 20 Aug 2013 20:21:03 +0000 (UTC) Received: by relay03.alfahosting-server.de (Postfix, from userid 1001) id 41A4532CD80E; Tue, 20 Aug 2013 22:10:05 +0200 (CEST) X-Spam-DCC: : X-Spam-Level: X-Spam-Status: No, score=0.0 required=7.0 tests=BAYES_50 autolearn=disabled version=3.2.5 Received: from alfa3018.alfahosting-server.de (alfa3018.alfahosting-server.de [109.237.140.30]) by relay03.alfahosting-server.de (Postfix) with ESMTPS id 85F5932CD80D for ; Tue, 20 Aug 2013 22:10:03 +0200 (CEST) Received: from [192.168.1.55] (p54B30782.dip0.t-ipconnect.de [84.179.7.130]) by alfa3018.alfahosting-server.de (Postfix) with ESMTPSA id 541D2515D2CF for ; Tue, 20 Aug 2013 22:10:03 +0200 (CEST) Message-ID: <5213CD1A.7000506@martinlaabs.de> Date: Tue, 20 Aug 2013 22:10:02 +0200 From: Martin Laabs User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130809 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-arm@freebsd.org Subject: Debug stalling Raspberry Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Status: No X-Virus-Checker-Version: clamassassin 1.2.4 with ClamAV 0.97.3/17707/Tue Aug 20 18:51:12 2013 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, 20 Aug 2013 20:21:03 -0000 Hi, currently I run r254441 on a raspberry pi b and every time I run portsnap the cpu stopps running. This happens during the snapshot verify while around 25k files are gunziped and sha256ed (file after file of cause). I can reproduce this but the Pi does not hang reproducible at the same file but the last processed file is different from try to try. There is, at least at the video console, no kernel panic. The kernel itself still responds to icmp ping packages and echos the keyboard output. But everything else does not work. (I know this behavior from disconnected harddisks containing the kernel/system) The current consumption also dropps around 100mA. It is very interesting that this behavior is not limited to the internal MMC card but also occurs when the data is stored external on an usb stick. My question is how to debug this bug since I have no idea where to start. >From my experience with bare metal arm systems I would start connecting a jtag debugger but I am afraid getting all the symbols mapped correct to the gdb. And even if this works - what should I monitor and what should I test for? There might be however a more simple solution. So any suggestion is welcome. If you can reproduce this bug I also would be very happy. Best regards, Martin Laabs