From owner-freebsd-arm@FreeBSD.ORG Sat Feb 9 11:04:00 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 266E0CD4 for ; Sat, 9 Feb 2013 11:04:00 +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 63CE430C for ; Sat, 9 Feb 2013 11:03:58 +0000 (UTC) Received: (qmail 30418 invoked from network); 9 Feb 2013 12:03:51 +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; 9 Feb 2013 12:03:46 +0100 Message-ID: <51162D16.7000206@thieprojects.ch> Date: Sat, 09 Feb 2013 12:03:50 +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: Re: named kills raspberry pi References: <20130207223038.ec308967273d6a16c41be97b@sohara.org> <20130208075702.a755649a60d10dabf10a058b@sohara.org> <0B9B84F3-D627-497F-B1DA-BE4D0F9BC5DA@bsdimp.com> <20130208121803.e6b57c3822271cce6e56b4b2@sohara.org> <20130208152351.GB19514@FreeBSD.org> <20130208162814.346c605ce15a229e878dee27@sohara.org> <20130209102413.5c5d8fe6@bender> <1360362075.4545.32.camel@revolution.hippie.lan> In-Reply-To: <1360362075.4545.32.camel@revolution.hippie.lan> 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: Sat, 09 Feb 2013 11:04:00 -0000 Hi all may I chime in with my experience, I wrote the 'portsnap killing...' post. I'm running on FreeHEAD HEAD Rev 246459 as per yesterday and now think that my previous post and the named problem is related after all, because everything DNS lookup related kills the Bone silently, be it nslookup, named and the likes. Switching the cpsw driver to Tims latest version doesn't change the situation a bit. I didn't try the proposed patch for the atomicity yet, but will over this weekend. Tim, it's a long shot, but could this be UDP related? Cheers, Werner