Date: Fri, 23 Jan 2015 22:38:43 -0700 From: Dan Raymond <draymond@foxvalley.net> To: Hans Petter Selasky <hps@selasky.org>, freebsd-arm@freebsd.org Subject: Re: Raspberry Pi stability improved Message-ID: <54C32FE3.1080807@foxvalley.net> In-Reply-To: <54BFAC6B.50201@selasky.org> References: <DE1783C0-C19F-448D-92EF-A51826D7FE2B@freebsd.org> <54BEFCC6.5040108@foxvalley.net> <54BFAC6B.50201@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54C32FE3.1080807>