From owner-freebsd-stable@FreeBSD.ORG Thu Jan 13 09:46:33 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78EA316A4CE for ; Thu, 13 Jan 2005 09:46:33 +0000 (GMT) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DFC643D48 for ; Thu, 13 Jan 2005 09:46:32 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0D9kPHJ021321 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 13 Jan 2005 20:46:30 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0D9kOxP053805; Thu, 13 Jan 2005 20:46:24 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j0D9kOvJ053804; Thu, 13 Jan 2005 20:46:24 +1100 (EST) (envelope-from pjeremy) Date: Thu, 13 Jan 2005 20:46:24 +1100 From: Peter Jeremy To: Rick Updegrove Message-ID: <20050113094624.GD79646@cirb503493.alcatel.com.au> References: <41E36760.2090609@updegrove.net> <44fz18m5k4.fsf@be-well.ilk.org> <41E59844.6000805@updegrove.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E59844.6000805@updegrove.net> User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org Subject: Re: 5.3-RELEASE crashes during make buildworld (and other problems) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2005 09:46:33 -0000 On Wed, 2005-Jan-12 13:36:04 -0800, Rick Updegrove wrote: >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x4d >fault code = supervisor read, page not present >instruction pointer = 0x8:0xc061c642 That's a NULL pointer dereference. It's not necessarily hardware. >rickup@nothing$ nm -n /boot/kernel | grep c061c642 >nm: Warning: '/boot/kernel' is not an ordinary file Two problems: 1) The kernel is /boot/kernel/kernel (sysctl kern.bootfile) 2) You're extremely unlikely to find a symbol at that address. What you need to do is $ nm -n `sysctl kern.bootfile` | less and search for the symbol closest to but no greater than 0xc061c642 This still isn't enough information to reveal anything useful. As a minimum, you need to enable DDB ("options DDB" and "options KDB") and get a backtrace after the panic. If you don't already have one, a serial console will make things much easier. A crashdump or gdb session would be much better. >> Hardware problems would be my first suspicion here. > >Me too... if it were not for the fact 5.3-RELEASE is the only OS that >has problems on this hardware. That doesn't totally rule out hardware. Pattern-sensitive memory problems may not show up on different operating systems (or even different kernels). That said, based on the trap information, I'd look at a software cause first. -- Peter Jeremy