From owner-freebsd-arm@FreeBSD.ORG Fri Feb 8 10:36:39 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AD21089E for ; Fri, 8 Feb 2013 10:36:39 +0000 (UTC) (envelope-from werner@thieprojects.ch) Received: from newton.metanet.ch (newton.metanet.ch [80.74.158.130]) by mx1.freebsd.org (Postfix) with ESMTP id 0E75DAA5 for ; Fri, 8 Feb 2013 10:36:38 +0000 (UTC) Received: (qmail 14528 invoked from network); 8 Feb 2013 11:29:55 +0100 Received: from 217-071-083-008.ip-tech.ch (HELO ?192.168.11.88?) (217.71.83.8) by newton.metanet.ch with (DHE-RSA-AES256-SHA encrypted) SMTP; 8 Feb 2013 11:29:55 +0100 Message-ID: <5114D3A4.9030105@thieprojects.ch> Date: Fri, 08 Feb 2013 11:29:56 +0100 From: Werner Thie User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-arm@freebsd.org Subject: portsnap fetch killing Beaglebone Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Fri, 08 Feb 2013 10:36:39 -0000 Hi all back in the game I built a most recent image, up per today, booting much more quiet than the images some weeks ago and did a portsnap fetch which kills the OS instantly. Comfirmed this with running a continuous ping to the IP of the Bone, the moment a portsnap is issued, the Bone does not respond anymore. Any clues? No traces of the crash found after reboot? TIA, Werner