From owner-freebsd-current@FreeBSD.ORG Thu Aug 5 17:35:40 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 DF3DE16A4CE for ; Thu, 5 Aug 2004 17:35:39 +0000 (GMT) Received: from pengo.systems.pipex.net (pengo.systems.pipex.net [62.241.160.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id E30AF43D58 for ; Thu, 5 Aug 2004 17:35:36 +0000 (GMT) (envelope-from mark.cullen@dsl.pipex.com) Received: from laptop (81-178-89-169.dsl.pipex.com [81.178.89.169]) by pengo.systems.pipex.net (Postfix) with SMTP id 328C24C0007A for ; Thu, 5 Aug 2004 18:35:31 +0100 (BST) Message-ID: <00e601c47b12$7b469eb0$f800000a@laptop> From: "Markie" To: "FreeBSD Current" References: <00f401c47653$fc8cb720$f800000a@laptop> Date: Thu, 5 Aug 2004 18:34:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: 5.2.1-R panic still occurs on a recent -CURRENT 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: Thu, 05 Aug 2004 17:35:40 -0000 ----- Original Message ----- From: "Markie" To: "FreeBSD Current" Sent: Friday, July 30, 2004 5:40 PM Subject: Re: 5.2.1-R panic still occurs on a recent -CURRENT | Here's the vmstat logs tar'd then gzipped. The filenames indicate the time of | the 'snapshot' in the format of: | | vmstat.day.month.year.hour (year was probably very unnecessary but oh well :-) | | ----- Original Message ----- | From: "Markie" | To: "FreeBSD Current" | Sent: Friday, July 30, 2004 1:46 AM | Subject: 5.2.1-R panic still occurs on a recent -CURRENT | | | | Hi all. | | | | You may or may not remember I was having trouble with 5.2.1-R giving me random | | panics along the lines of panic: kmem_malloc(4096): kmem_map too small: xxxx | | total allocated. It was suggested that I updated to CURRENT to see if the | issue | | had been fixed. | | | | Well, my server just rebooted. The strange thing is though I didn't get a | | crashdump this time... and it did a background fsck on / aswell, which was | | really nice because it booted up so quickly. Is it safe though? I thought | bgfsck | | wasn't allowed on / yet? | | | | I can't remember who replied last time but I was told to log vmstat -mz every | | hour incase of memory leaks, so I have alot of vmstat hourly files if that | might | | determine the cause of my panic. I also logged netstat -m but if that isn't | any | | help then I can just get rid of all those. | | | | I also noticed something in the logs not long (or right before) it paniced | this | | time: | | | | Jul 30 01:19:57 bone kernel: arpresolve: can't allocate llinfo for | | xxx.xxx.xxx.xxxrt | | Jul 30 01:19:58 bone kernel: arplookup xxx.xxx.xxx.xxx failed: could not | | allocate llinfo | | Jul 30 01:19:58 bone kernel: arpresolve: can't allocate llinfo for | | xxx.xxx.xxx.xxxrt | | Jul 30 01:19:58 bone kernel: arplookup xxx.xxx.xxx.xxx failed: could not | | allocate llinfo | | Jul 30 01:19:58 bone kernel: arpresolve: can't allocate llinfo for | | xxx.xxx.xxx.xxxrt | | Jul 30 01:19:59 bone kernel: arplookup xxx.xxx.xxx.xxx failed: could not | | allocate llinfo | | Jul 30 01:19:59 bone kernel: arpresolve: can't allocate llinfo for | | xxx.xxx.xxx.xxxrt | | Jul 30 01:20:00 bone kernel: arplookup xxx.xxx.xxx.xxx failed: could not | | allocate llinfo | | | | Alot of those. Not sure what it means exactly but could it be related in any | | way? | | | | What do you suggest I do? Would you like to take a look at these vmstat files? | | | | Thanks in advance. | | | | P.S Any ideas why it might not have saved a core dump this time? All I got was | | "Jul 30 01:21:39 bone savecore: no dumps found" I have dumpdev set in rc.conf | | too. Maybe it didn't panic but spontaneously rebooted, perhaps because of a | | change in -CURRENT? Or is spontaneous rebooting hardware problems? | | | -------------------------------------------------------------------------------- | _______________________________________________ | freebsd-current@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-current | To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" | Any ideas? No one else seems to have a problem with this panic randomly appearing but me... :-S Need some more info?