From owner-freebsd-arm@FreeBSD.ORG Wed Jan 21 13:40:13 2015 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B43D2ADF for ; Wed, 21 Jan 2015 13:40:13 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 73F67156 for ; Wed, 21 Jan 2015 13:40:12 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 9677B1FE023; Wed, 21 Jan 2015 14:40:09 +0100 (CET) Message-ID: <54BFAC6B.50201@selasky.org> Date: Wed, 21 Jan 2015 14:40:59 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Dan Raymond , freebsd-arm@freebsd.org Subject: Re: Raspberry Pi stability improved References: <54BEFCC6.5040108@foxvalley.net> In-Reply-To: <54BEFCC6.5040108@foxvalley.net> 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: Wed, 21 Jan 2015 13:40:13 -0000 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