From owner-freebsd-current@FreeBSD.ORG  Tue Oct 19 11:41:58 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7E23E16A4CE
	for <freebsd-current@freebsd.org>;
	Tue, 19 Oct 2004 11:41:58 +0000 (GMT)
Received: from node15.coopprint.com (node15.cooperativeprinting.com
	[208.4.77.15])	by mx1.FreeBSD.org (Postfix) with SMTP id C659343D55
	for <freebsd-current@freebsd.org>;
	Tue, 19 Oct 2004 11:41:57 +0000 (GMT)
	(envelope-from ryans@gamersimpact.com)
Received: (qmail 114 invoked by uid 0); 19 Oct 2004 11:40:51 -0000
Received: from unknown (HELO ?192.168.0.5?) (63.231.165.205)
  by node15.coopprint.com with SMTP; 19 Oct 2004 11:40:51 -0000
Message-ID: <4174FD94.1050407@gamersimpact.com>
Date: Tue, 19 Oct 2004 06:42:12 -0500
From: Ryan Sommers <ryans@gamersimpact.com>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mark Cullen <mark.cullen@dsl.pipex.com>
References: <4174D733.2020201@dsl.pipex.com>
In-Reply-To: <4174D733.2020201@dsl.pipex.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: 5.2-CURRENT panic (a little outdated I know, but still)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2004 11:41:58 -0000

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