Date: Fri, 29 Aug 2003 11:52:16 -0700 From: "Andrew Kinney" <andykinney@advantagecom.net> To: Marc Ramirez <marc.ramirez@bluecirclesoft.com> Cc: hackers@freebsd.org Subject: Re: FYI - Just got a kernel panic - RELENG_4 Message-ID: <3F4F3E70.29375.29FAE516@localhost> In-Reply-To: <20030828171635.C73827@www.bluecirclesoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28 Aug 2003, at 17:34, Marc Ramirez wrote: > c0271430 T vm_page_remove > c02714f8 T vm_page_lookup Your fault address is between those two, so it happened sometime after you entered vm_page_remove. This particular failure is often related to running out of KVM/KVA space (or hardware problems as someone else mentioned), but without a backtrace it's tough to tell for sure. We had this problem on one of our machines and recently another fellow had this same problem. If you're able to duplicate the panic reliably, then it's likely a KVM/KVA shortage that you'd fix by rebuilding your kernel with a larger KVA_PAGES value (see LINT). If this fixes it for you, please be sure to respond to the list with news of your success so that others searching for this problem and a solution are able to do so. If the fault address is variable and the panic is not consistently reproduceable, then hardware problems are more likely. In many cases with random panics related to memory allocation or deallocation, bad RAM is the culprit, but sometimes it can be a heat issue or a semi-fried CPU that randomly flips bits. Hope that helps. Sincerely, Andrew Kinney President and Chief Technology Officer Advantagecom Networks, Inc. http://www.advantagecom.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F4F3E70.29375.29FAE516>