Date: Fri, 18 Oct 2002 14:07:17 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Ben Stuyts <ben@stuyts.nl> Cc: current@freebsd.org, Jeff Roberson <jroberson@chesapeake.net>, Robert Watson <rwatson@freebsd.org>, jeff@freebsd.org, Alfred Perlstein <alfred@FreeBSD.ORG> Subject: Re: [Ugly PATCH] Again: panic kmem_malloc() Message-ID: <3DB07805.AB4BAA15@mindspring.com> References: <4.3.2.7.2.20021018125313.00bb8990@terminus>
next in thread | previous in thread | raw e-mail | index | archive | help
Ben Stuyts wrote: > Just had another panic, same kmem_malloc(). I did a trace but forgot to > write the traceback down. Wait until the next one, and remember to write it down; preferrably, obtain a system dump image, so you can examine it with the debugger, and make sure that the kernel you are running has a debuggable counterpart already there (i.e. you used "config -g" to create the kernel you are running). > In any case, there was a semop() call in the traceback. Not useful, without the full traceback. > Furthermore, this might be interesting: the last vmstat -m log > before the panic. Maybe someone can check if these values are reasonable? > The system has 64 MB memory and has been up for about 24 hrs with almost no > load. > sem344456 5390K 5390K 344456 16,1024,4096 Almost 5.3M of unswappable physical memory dedicated to semaphores seems like a bit much. But without knowing what software you are running, it's hard to say if the number is unreasonable, or not. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DB07805.AB4BAA15>