From owner-freebsd-questions@FreeBSD.ORG Tue Nov 23 16:02:27 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B50516A4D0 for ; Tue, 23 Nov 2004 16:02:27 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A50343D5D for ; Tue, 23 Nov 2004 16:02:27 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iANG2JC5097568; Tue, 23 Nov 2004 10:02:19 -0600 (CST) (envelope-from dan) Date: Tue, 23 Nov 2004 10:02:19 -0600 From: Dan Nelson To: Piotr Gnyp Message-ID: <20041123160219.GG48882@dan.emsphone.com> References: <20041123131807.GA1070@discordia.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041123131807.GA1070@discordia.pl> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: questions@freebsd.org Subject: Re: 5.3-STABLE - system after few hours X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 16:02:27 -0000 In the last episode (Nov 23), Piotr Gnyp said: > after upgrade from 5.2.1 o 5.3-STABLE my system started to reboot on > regular basis. The error message on screen (not always showing): > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id=03 > fault virtual address = 0x1c > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc04ce84b > stack pointer = 0x10:0xea54f9co > frame pointer = 0x10:0xea54f9cc > code segment = base 0x0, limit 0xfffff type 0x1b > = DPL 0, pres 1, def32 1 , gran 1 > procesor eflags = interrupt cenabled, resume, IOPL=0 > current process = 11445 (screen) > trap number = 12 > panic: page fault > cpuid = 0 > boot() called on cpu#0 Enable crashdumps by setting dumpdev="/path/to/swap/slice" in rc.conf, wait for the system to crash again, then use the dump to get a stack trace, and post that. http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING -- Dan Nelson dnelson@allantgroup.com