Re: FYI - Just got a kernel panic - RELENG_4
On Fri, 29 Aug 2003, Kris Kennaway wrote: > On Thu, Aug 28, 2003 at 05:34:29PM -0400, Marc Ramirez wrote: > > > > supped as of ~ 1:40pm EST today > > > > The panic: > > > > Fatal trap 12: page fault while in kernel mode > > This is probably hardware-related, but it's possible it may be due to > a kernel problem. As a first step, you need to try and get a gdb > traceback with debugging symbols as explained in the developer's > handbook on the website. I forgot to turn off the cvsup cron job; I went to rebuild the kernel with DDB, and found out that my code base had changed... Everything works now. I have been unable to reproduce the crash... Thanks for taking the time, though. Marc. -- Marc Ramirez Blue Circle Software Corporation 513-688-1070 (main) 513-382-1270 (direct) http://www.bluecirclesoft.com http://www.mrami.com (personal) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FYI - Just got a kernel panic - RELENG_4
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FYI - Just got a kernel panic - RELENG_4
On Thu, Aug 28, 2003 at 05:34:29PM -0400, Marc Ramirez wrote: > > supped as of ~ 1:40pm EST today > > The panic: > > Fatal trap 12: page fault while in kernel mode This is probably hardware-related, but it's possible it may be due to a kernel problem. As a first step, you need to try and get a gdb traceback with debugging symbols as explained in the developer's handbook on the website. Kris pgp0.pgp Description: PGP signature
