Date: Sat, 09 Feb 2013 12:03:50 +0100 From: Werner Thie <werner@thieprojects.ch> To: freebsd-arm@freebsd.org Subject: Re: named kills raspberry pi Message-ID: <51162D16.7000206@thieprojects.ch> In-Reply-To: <1360362075.4545.32.camel@revolution.hippie.lan> References: <20130207223038.ec308967273d6a16c41be97b@sohara.org> <E2B20243-F2AD-4B62-946D-374765CB9E39@kientzle.com> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51162D16.7000206>