Re: 5.2-CURRENT panic (a little outdated I know, but still)

From: Ryan Sommers <ryans_at_gamersimpact.com>
Date: Tue, 19 Oct 2004 06:42:12 -0500
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_at_gamersimpact.com
Received on Tue Oct 19 2004 - 09:41:58 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:18 UTC