named kills raspberry pi

[Tim Kientzle]

On Feb 9, 2013, at 12:36 PM, Tim Kientzle wrote:

> 
> On Feb 9, 2013, at 11:32 AM, Tim Kientzle wrote:
> 
>> 
>> On Feb 9, 2013, at 7:50 AM, George Rosamond wrote:
>> 
>>> On 02/09/13 06:03, Werner Thie wrote:
>>>> 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?
>>>> 
>>> 
>>> My $0.02:
>>> 
>>> 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.
>>> 
>>> The BBone isn't doing much, however, as it just sits on a quiet private network with no ports installed.
>>> 
>>> 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.
> 
> 
> Luckily, I had updated just shortly before and after the breakage,
> so it only took a couple of tries to bisect and find the problem.
> 
> Looks like r246318 broke the stack alignment.
> 
> I think I see the problem; it will take me a few minutes to
> verify a fix.



I believe this is fixed in r246601.

Tim