Date: Tue, 19 Oct 2004 06:42:12 -0500 From: Ryan Sommers <ryans@gamersimpact.com> To: Mark Cullen <mark.cullen@dsl.pipex.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: 5.2-CURRENT panic (a little outdated I know, but still) Message-ID: <4174FD94.1050407@gamersimpact.com> In-Reply-To: <4174D733.2020201@dsl.pipex.com> References: <4174D733.2020201@dsl.pipex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Cullen wrote: > Me again. Same symptoms and a hard lock up. Different hardware, put my > P1 133MHz machine back. Last thing in /var/log/messages before it > locked up (and I had to hit reset) is the same as before... > > -- /var/log/messages/ -- > Oct 19 08:27:18 bone kernel: arplookup xx.xx.xx.xx failed: could not > allocate llinfo > Oct 19 08:27:18 bone kernel: arpresolve: can't allocate llinfo for > xx.xx.xx.xxrt > -- end -- > > Anyone got any ideas yet? It's been doing this since uhh.. I think I > installed 5.2.1-RELEASE and was having these problems, someone > suggested going -CURRENT and I was still getting them. For what it's > worth I am now going to update to 5.3-whatever-its-at. (RELENG_5) > > Help me out? It's getting a tad annoying :) What are your memory usage statistics like? Amount of memory in box? Swap space? Tried different memory? Dmesg output? -- Ryan Sommers ryans@gamersimpact.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4174FD94.1050407>