Date: Fri, 8 Feb 2013 04:58:27 -0700 From: Warner Losh <imp@bsdimp.com> To: Steve O'Hara-Smith <steve@sohara.org> Cc: Tim Kientzle <tim@kientzle.com>, freebsd-arm@freebsd.org Subject: Re: named kills raspberry pi Message-ID: <0B9B84F3-D627-497F-B1DA-BE4D0F9BC5DA@bsdimp.com> In-Reply-To: <20130208075702.a755649a60d10dabf10a058b@sohara.org> References: <20130207223038.ec308967273d6a16c41be97b@sohara.org> <E2B20243-F2AD-4B62-946D-374765CB9E39@kientzle.com> <20130208075702.a755649a60d10dabf10a058b@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 8, 2013, at 12:57 AM, Steve O'Hara-Smith wrote: > On Thu, 7 Feb 2013 22:32:40 -0800 > Tim Kientzle <tim@kientzle.com> wrote: >=20 >>=20 >> On Feb 7, 2013, at 2:30 PM, Steve O'Hara-Smith wrote: >>=20 >>> Hi, >>>=20 >>> As soon as I start named either by rc.d script or directly, >>> whether in an ssh session or directly on the video console, with or >>> without chroot, my early model 256MB model B pi locks up solid, no >>> response on console, all ssh sessions freeze, no response to ping, >>> nothing until power cycle. I can build ports all day long, but if I >>> start named everything stops dead. >>=20 >> $ truss named -f >=20 > Yep, nice idea, that or ktrace. Sadly there's no truss built > for the rpi, as for ktrace there was no sign of the output file after > reboot. >=20 >> If you're lucky, you might catch some of the last system calls >> before it hangs, which might give a clue. >=20 > I think Warner has pointed me in the right direction, apart from > anything else it looks like there's a three year old fix for the = ras_start > address that's never been committed - I'll be trying that today. I thought that fix had been committed... But the issue isn't that fix, = but rather the difference between armv6 atomics and armv[45] atomics. We = shouldn't be using ras* anything at all on armv6. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0B9B84F3-D627-497F-B1DA-BE4D0F9BC5DA>