From owner-freebsd-current@FreeBSD.ORG Tue Oct 19 15:06:23 2004 Return-Path: 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 F110616A4E8 for ; Tue, 19 Oct 2004 15:06:22 +0000 (GMT) Received: from galaxy.systems.pipex.net (galaxy.systems.pipex.net [62.241.162.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9EC943D39 for ; Tue, 19 Oct 2004 15:06:21 +0000 (GMT) (envelope-from mark.cullen@dsl.pipex.com) Received: from [10.0.0.247] (81-178-107-130.dsl.pipex.com [81.178.107.130]) by galaxy.systems.pipex.net (Postfix) with ESMTP id A9375E00025F; Tue, 19 Oct 2004 16:06:19 +0100 (BST) Message-ID: <41752E60.4070603@dsl.pipex.com> Date: Tue, 19 Oct 2004 16:10:24 +0100 From: Mark Cullen User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ryan Sommers References: <4174D733.2020201@dsl.pipex.com> <4174FD94.1050407@gamersimpact.com> In-Reply-To: <4174FD94.1050407@gamersimpact.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD Current 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 15:06:23 -0000 Ryan Sommers wrote: > 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? > Well uhm, I can't really answer the memory usage stats I don't think? Someone suggested keeping a log of some vmstat stuff which... I could probably find (posted it all to the list before). The 133 has 64MB and the 350 (went 133->350->back to 133) has 96MB. They both lasted around 20 days before locking up/panicing. Swap space... Device 1K-blocks Used Avail Capacity /dev/ad0s1b 208780 74248 134532 36% I've tried a whole different machine :) Sorry if there's a lack of info. I really don't know what to post. I'll mention I don't ever remember getting this problem when running 4.x Here's dmesg.boot: -- Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-CURRENT #6: Sat Sep 4 19:02:02 BST 2004 mrboo@bone.bone.servebeer.com:/usr/obj/usr/src/sys/BONE Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium/P54C (132.96-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 67108864 (64 MB) avail memory = 60239872 (57 MB) Intel Pentium detected, installing workaround for F00F bug npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 fxp0: port 0xfe80-0xfebf mem 0xffd00000-0xffdfffff,0xfffbe000-0xfffbefff irq 9 at device 13.0 on pci0 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:04:ac:23:02:77 fxp0: [GIANT-LOCKED] fxp1: port 0xff00-0xff3f mem 0xffe00000-0xffefffff,0xfffbf000-0xfffbffff irq 10 at device 14.0 on pci0 miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:90:27:d0:88:d1 fxp1: [GIANT-LOCKED] pci0: at device 15.0 (no driver attached) cpu0 on motherboard orm0: