From owner-freebsd-arm@FreeBSD.ORG Sat Jan 24 05:38:52 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C09485D7 for ; Sat, 24 Jan 2015 05:38:52 +0000 (UTC) Received: from mail.FoxValley.net (mail.FoxValley.net [64.135.192.34]) by mx1.freebsd.org (Postfix) with SMTP id 5CD8AF0B for ; Sat, 24 Jan 2015 05:38:51 +0000 (UTC) Received: (qmail 17161 invoked from network) for freebsd-arm@freebsd.org; 23 Jan 2015 23:38:41 -0600 Received: from 75-171-144-163.hlrn.qwest.net (HELO ?192.168.1.3?) (draymond@75.171.144.163) by mail.foxvalley.net with SMTP; 23 Jan 2015 23:38:41 -0600 Message-ID: <54C32FE3.1080807@foxvalley.net> Date: Fri, 23 Jan 2015 22:38:43 -0700 From: Dan Raymond User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Hans Petter Selasky , freebsd-arm@freebsd.org Subject: Re: Raspberry Pi stability improved References: <54BEFCC6.5040108@foxvalley.net> <54BFAC6B.50201@selasky.org> In-Reply-To: <54BFAC6B.50201@selasky.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2015 05:38:52 -0000 I created an image using 277212 and tried 'portsnap fetch update'. It ran to completion (twice) without crashing. Then I loaded the 275002 image I created in November and ran 'portsnap fetch update'. It failed (crashed) the first time. It seems that whatever fixed it came between 275002 and 277212 or maybe it was a change in the u-boot files between now and November. On 1/21/2015 6:40 AM, Hans Petter Selasky wrote: > On 01/21/15 02:11, Dan Raymond wrote: >> I've been running a web/email server on my Raspberry Pi B+ since Nov >> 28. I was running 11-CURRENT r275002 and it crashed for the first time >> a few days ago. That was 49 days of up-time before crashing which isn't >> bad. I've since upgraded to r277334 and we'll see how long it stays up >> now. I can also confirm that "portsnap fetch update" caused a crash >> every time for me on r275002 but it ran successfully to completion on >> r277334. >> > > Hi, > > Could you try "portsnap fetch update" before and after r277213 ? > > --HPS >