Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 9 Feb 2013 11:32:14 -0800
From:      Tim Kientzle <tim@kientzle.com>
To:        george@ceetonetechnology.com
Cc:        freebsd-arm@freebsd.org
Subject:   Re: named kills raspberry pi
Message-ID:  <399EC5F6-6820-40A0-A58B-B3ECA1B58E76@kientzle.com>
In-Reply-To: <5116703C.3000904@ceetonetechnology.com>
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> <51162D16.7000206@thieprojects.ch> <5116703C.3000904@ceetonetechnology.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Feb 9, 2013, at 7:50 AM, George Rosamond wrote:

> On 02/09/13 06:03, Werner Thie wrote:
>> Hi all
>>=20
>> may I chime in with my experience, I wrote the 'portsnap killing...' =
post.
>>=20
>> 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.
>>=20
>> 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.
>>=20
>> Tim, it's a long shot, but could this be UDP related?
>>=20
>=20
> My $0.02:
>=20
> Running r246119 of CURRENT, without named running, I can ping and do =
digs with no issue.  And sshd doesn't seem to die either, and it's been =
up for a while.
>=20
> The BBone isn't doing much, however, as it just sits on a quiet =
private network with no ports installed.
>=20
> I'll update to the current build later and test then.

I wasn't seeing this with r246278, but am seeing it now with r246600.

Seems like recent breakage.

Tim




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?399EC5F6-6820-40A0-A58B-B3ECA1B58E76>